diff --git a/en/access-working-group-awg/index.html b/en/access-working-group-awg/index.html index c8c4121df..e02facc44 100644 --- a/en/access-working-group-awg/index.html +++ b/en/access-working-group-awg/index.html @@ -1,4 +1,4 @@ -Access Working Group (AWG) - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Access Working Group (AWG)

The Access Working Group (AWG) was established by the Treasury Board Internet Advisory Committee (parent committee) on August 1, 1997 to engage in collaborative activities between government, private sector and community organizations that have a stake in ensuring equitable access to information and services, especially for, but not limited to persons with disabilities, for the purpose of providing input to Government of Canada (GoC) policy making.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

AWG Next Meeting

When:
1st Tuesday of every month
Time:
1:30 PM to 3:00 PM
Location:
10 Wellington, Gatineau, Quebec, Boardoom #2134, 2nd floor

Mandate

The mandate of the AWG is to provide feedback and proposed solutions to common Government of Canada Web accessibility issues for the Treasury Board Secretariat, Web Managers Council (WMC) and other web, accessibility, procurement and policy groups. The AWG will focus on inclusion by design and full accessibility, meaning that the AWG is not just looking for technically accessible solutions, but ones that are also fully usable for persons with disabilities. (Updated 2016-07-05)

Roles

The Access Working Group has two essential roles: as an advisory body and as a working group providing expertise and independent review for the TBS, the Web Manager’s Council and Web Renewal Initiative.

  1. In its role as an advisory body, the AWG would improve the accessibility of GC-Wide Web Based information and services by:
    • Assisting TBS and the WMC identify Web Accessibility Issues and priorities for persons with disabilities and identify unresolved Web Accessibility Issues.
    • Providing input and expertise on the development of Web standards and guidelines adopted by the GC.
    • Providing advice on GC-wide initiatives and policies affecting persons with disabilities.
  2. In its role as a working group providing expertise and independent review the AWG would be responsible to:
    • Leverage the expertise of AWG members and Adaptive Computer Technology facilities for review and/or user testing on priority projects. Results and recommendations would be compiled by the AWG.
    • Collaborate with the other working groups to ensure that accessibility requirements are incorporated in their advice, recommendation, etc.
    • Report regularly on the work plans of the AWG and to report on the status of deliverables.
Added:
2010-02-19
Updated:
2016-07-05

Work Plan

The Work plan for the AWG will be developed by the members taking into consideration the work plans of other core working groups and will be driven by the priorities set by TBS. This plan will be reviewed on a quarterly basis. The AWG will report on work plans and the status of deliverables.

Added:
2010-02-19
Updated:
2016-07-04

Membership Criteria

Membership on the Access Working Group is intended to reflect its role as a voice for the needs of Web accessibility community & persons with disabilities.

Membership will be comprised as follows:

Membership on the Access Working Group is open to all federal civil servants. Each member must be appointed by a manager at their organization, who is at the EX minus 1 level or higher.

To ensure continuity and stability of involvement, discussion, and information flow, substitutions are discouraged; however, each member may appoint an alternate who will be empowered to fully participate in the Access Working Group’s work in place of the regular member.

The AWG with the prior approval of the Chair(s) of the parent committee, may invite membership above and beyond the membership criteria and retain such assistance and direct such work as may be necessary to facilitate its work. Membership in the AWG could change, as work items are completed and new ones are undertaken.

Members are expected to:

Updated:
2010-02-24

Current Priorities

Added:
2010-02-24
Updated:
2016-07-04

AWG Projects

Updated:
2010-02-24

Keeping informed

People to follow on Twitter

Hashtags to follow

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Access Working Group (AWG)

The Access Working Group (AWG) was established by the Treasury Board Internet Advisory Committee (parent committee) on August 1, 1997 to engage in collaborative activities between government, private sector and community organizations that have a stake in ensuring equitable access to information and services, especially for, but not limited to persons with disabilities, for the purpose of providing input to Government of Canada (GoC) policy making.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

AWG Next Meeting

When:
1st Tuesday of every month
Time:
1:30 PM to 3:00 PM
Location:
10 Wellington, Gatineau, Quebec, Boardoom #2134, 2nd floor

Mandate

The mandate of the AWG is to provide feedback and proposed solutions to common Government of Canada Web accessibility issues for the Treasury Board Secretariat, Web Managers Council (WMC) and other web, accessibility, procurement and policy groups. The AWG will focus on inclusion by design and full accessibility, meaning that the AWG is not just looking for technically accessible solutions, but ones that are also fully usable for persons with disabilities. (Updated 2016-07-05)

Roles

The Access Working Group has two essential roles: as an advisory body and as a working group providing expertise and independent review for the TBS, the Web Manager’s Council and Web Renewal Initiative.

  1. In its role as an advisory body, the AWG would improve the accessibility of GC-Wide Web Based information and services by:
    • Assisting TBS and the WMC identify Web Accessibility Issues and priorities for persons with disabilities and identify unresolved Web Accessibility Issues.
    • Providing input and expertise on the development of Web standards and guidelines adopted by the GC.
    • Providing advice on GC-wide initiatives and policies affecting persons with disabilities.
  2. In its role as a working group providing expertise and independent review the AWG would be responsible to:
    • Leverage the expertise of AWG members and Adaptive Computer Technology facilities for review and/or user testing on priority projects. Results and recommendations would be compiled by the AWG.
    • Collaborate with the other working groups to ensure that accessibility requirements are incorporated in their advice, recommendation, etc.
    • Report regularly on the work plans of the AWG and to report on the status of deliverables.
Added:
2010-02-19
Updated:
2016-07-05

Work Plan

The Work plan for the AWG will be developed by the members taking into consideration the work plans of other core working groups and will be driven by the priorities set by TBS. This plan will be reviewed on a quarterly basis. The AWG will report on work plans and the status of deliverables.

Added:
2010-02-19
Updated:
2016-07-04

Membership Criteria

Membership on the Access Working Group is intended to reflect its role as a voice for the needs of Web accessibility community & persons with disabilities.

Membership will be comprised as follows:

Membership on the Access Working Group is open to all federal civil servants. Each member must be appointed by a manager at their organization, who is at the EX minus 1 level or higher.

To ensure continuity and stability of involvement, discussion, and information flow, substitutions are discouraged; however, each member may appoint an alternate who will be empowered to fully participate in the Access Working Group’s work in place of the regular member.

The AWG with the prior approval of the Chair(s) of the parent committee, may invite membership above and beyond the membership criteria and retain such assistance and direct such work as may be necessary to facilitate its work. Membership in the AWG could change, as work items are completed and new ones are undertaken.

Members are expected to:

Updated:
2010-02-24

Current Priorities

Added:
2010-02-24
Updated:
2016-07-04

AWG Projects

Updated:
2010-02-24

Keeping informed

People to follow on Twitter

Hashtags to follow

Page details

Date modified:
\ No newline at end of file diff --git a/en/accessibility-testing-101/index.html b/en/accessibility-testing-101/index.html index 43c9e40f0..cce099a1f 100644 --- a/en/accessibility-testing-101/index.html +++ b/en/accessibility-testing-101/index.html @@ -1,4 +1,4 @@ -Accessibility Testing 101 - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Accessibility Testing 101

For anyone wanting to create accessible content, we encourage you to use automated accessibility testing tools. These testing tools will help content creators as they build their content by finding errors and offering suggestions to improve the accessibility of their product, application or web site. On this page a list of recommended accessibility testing tools has been made available

On this page

Please note that some of the accessibility testing tools listed will require administrative permissions to install on your device.

Building your toolset

Tool: WAVE Browser Extensions

WAVE for Chrome, Firefox, and Edge extensions allows you to evaluate web content for accessibility issues directly within your browser. Because the extension runs entirely within your web browser, no information is sent to the WAVE server.

While WAVE is most effective when used by someone knowledgeable about web accessibility, people who are not web accessibility experts can also benefit from WAVE.

If you are new to WAVE, take advantage of the Introduction to WAVE video.

Browser Compatibility:

Additional WAVE Documentation:

WAVE Tips and Tricks:

The WAVE sidebar indicates if WAVE has detected any errors or not. The absence of errors DOES NOT mean your page is accessible or compliant. RED icons indicate accessibility errors that need to be fixed. GREEN icons indicate accessibility features—things that improve accessibility (though these should be verified). The other icons and indicators, particularly the yellow alert icons, highlight other elements that you should look at. WAVE brings the underlying accessibility information of a page to the forefront so it can be easily evaluated in context.

Styles and Code:

WAVE provides functionality for disabling page CSS (Cascading Style Sheets) styles. Complex, CSS-powered layouts may become difficult to read, especially after the WAVE icons have been embedded, so disabling styles can simplify the page presentation. Disabling styles also allow you to view the underlying reading and navigation order, the order in which keyboard-only and screen reader users will access the page. To view the relevant code for a particular WAVE icon, you can select the Code tab at the bottom of the page to view the underlying markup/DOM of your page.

Tool: Accessibility Insights for Web

Accessibility Insights for Web is an extension for Chrome and Microsoft Edge that helps developers find and fix accessibility issues in web apps and sites.

The tool supports two primary scenarios:

This is a tool for all levels, you do not need to know accessibility to use it, it will guide you through each step.

Browser Compatibility:

Accessibility Insights Documentation:

Tips and Tricks:

Keyboard Shortcuts:

Tool: LightHouse

Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, public or requiring authentication. It has audits for performance, accessibility, progressive web apps, SEO, and more. A very useful tool for Multimedia Developers and Web Accessibility Testers.

Browsers:

LightHouse Extension Documentation:

Additional Help:

Additional Help and Resources

Keyboard and Manual testing of your site

Automated tools and validators to identify accessibility issues:

Keyboard testing basics

Review or test your site periodically to ensure there are no new errors and the site remains accessible.

Additional Resources

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Accessibility Testing 101

For anyone wanting to create accessible content, we encourage you to use automated accessibility testing tools. These testing tools will help content creators as they build their content by finding errors and offering suggestions to improve the accessibility of their product, application or web site. On this page a list of recommended accessibility testing tools has been made available

On this page

Please note that some of the accessibility testing tools listed will require administrative permissions to install on your device.

Building your toolset

Tool: WAVE Browser Extensions

WAVE for Chrome, Firefox, and Edge extensions allows you to evaluate web content for accessibility issues directly within your browser. Because the extension runs entirely within your web browser, no information is sent to the WAVE server.

While WAVE is most effective when used by someone knowledgeable about web accessibility, people who are not web accessibility experts can also benefit from WAVE.

If you are new to WAVE, take advantage of the Introduction to WAVE video.

Browser Compatibility:

Additional WAVE Documentation:

WAVE Tips and Tricks:

The WAVE sidebar indicates if WAVE has detected any errors or not. The absence of errors DOES NOT mean your page is accessible or compliant. RED icons indicate accessibility errors that need to be fixed. GREEN icons indicate accessibility features—things that improve accessibility (though these should be verified). The other icons and indicators, particularly the yellow alert icons, highlight other elements that you should look at. WAVE brings the underlying accessibility information of a page to the forefront so it can be easily evaluated in context.

Styles and Code:

WAVE provides functionality for disabling page CSS (Cascading Style Sheets) styles. Complex, CSS-powered layouts may become difficult to read, especially after the WAVE icons have been embedded, so disabling styles can simplify the page presentation. Disabling styles also allow you to view the underlying reading and navigation order, the order in which keyboard-only and screen reader users will access the page. To view the relevant code for a particular WAVE icon, you can select the Code tab at the bottom of the page to view the underlying markup/DOM of your page.

Tool: Accessibility Insights for Web

Accessibility Insights for Web is an extension for Chrome and Microsoft Edge that helps developers find and fix accessibility issues in web apps and sites.

The tool supports two primary scenarios:

This is a tool for all levels, you do not need to know accessibility to use it, it will guide you through each step.

Browser Compatibility:

Accessibility Insights Documentation:

Tips and Tricks:

Keyboard Shortcuts:

Tool: LightHouse

Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, public or requiring authentication. It has audits for performance, accessibility, progressive web apps, SEO, and more. A very useful tool for Multimedia Developers and Web Accessibility Testers.

Browsers:

LightHouse Extension Documentation:

Additional Help:

Additional Help and Resources

Keyboard and Manual testing of your site

Automated tools and validators to identify accessibility issues:

Keyboard testing basics

Review or test your site periodically to ensure there are no new errors and the site remains accessible.

Additional Resources

Page details

Date modified:
\ No newline at end of file diff --git a/en/accessible-virtual-events/index.html b/en/accessible-virtual-events/index.html index 231b70e54..c80ef6f9c 100644 --- a/en/accessible-virtual-events/index.html +++ b/en/accessible-virtual-events/index.html @@ -9,4 +9,4 @@ w.gtag('js', new Date()); w.gtag('config', 'G-SM9MSHWDVN'); } - })(window);

Language selection

Government of Canada / Government of Canada

Search

Accessible virtual events

Learn how to host accessible virtual meetings such as a training session, a meeting, or an open-door event.

Best practices for accessible virtual events

This guide is all about planning events, covering a broad range of activities like conferences, meetings, and presentations. It includes common barriers faced by people with disabilities during events and a suggested timeline for organizing your event. The goal is to work together to create more inclusive and accessible experiences.

CART Services and Sign Language Interpreters

The most common accommodations for meetings or events are computer-assisted real-time translation (CART) and sign language interpretation services (SLI).

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Accessible virtual events

Learn how to host accessible virtual meetings such as a training session, a meeting, or an open-door event.

Best practices for accessible virtual events

This guide is all about planning events, covering a broad range of activities like conferences, meetings, and presentations. It includes common barriers faced by people with disabilities during events and a suggested timeline for organizing your event. The goal is to work together to create more inclusive and accessible experiences.

CART Services and Sign Language Interpreters

The most common accommodations for meetings or events are computer-assisted real-time translation (CART) and sign language interpretation services (SLI).

Page details

Date modified:
\ No newline at end of file diff --git a/en/additional-resources/index.html b/en/additional-resources/index.html index 2c8efcd9a..26dce449c 100644 --- a/en/additional-resources/index.html +++ b/en/additional-resources/index.html @@ -1,4 +1,4 @@ -Additional Resources - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Additional Resources

Resources and useful tools for web accessibility for employees of the Government of Canada.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

On this page

Accessible meetings and events

Virtual meetings and events come in various formats and sizes – from small workshops with participants who know each other to large public meetings you are planning. It is critical to ensure meetings and events are fully accessible, from accessing them, to the presentations. By planning ahead, you can build accessibility into all aspects of the meeting. This will allow everyone to participate fully, including people with disabilities.

In order to assist you in offering a fully accessible virtual meeting/event, whether it is a training session, a meeting, a kiosk or an open-door event, the IT Accessibility Office (ITAO) has gathered the most relevant information on the subject.

Accessible meeting/event guidelines

Proper planning of meetings and events is essential for the inclusion of all. There are several things to consider in the to-do list before and during meetings/events.

Accessibility overview of Microsoft Teams

Microsoft Teams is a messaging and collaboration app that lets everyone in your organization join the conversation and work together. This page contains an overview of the many accessibility features that make sure all users can have the best possible experience.

Best practices for setting up and running a Teams meeting or Live event for the deaf and hard of hearing (microsoft.com)

This page contains an overview of the many accessibility features that make sure all users can have the best possible experience, including accessibility features for a better meeting or live event experience, and best practices for setting up and running a Teams meeting or Live event for the deaf and hard of hearing.

CART services and Sign Language Interpreters (SLI)

The most common accommodations for meetings or events are Communication Access Realtime Translation (CART) and interpretation services.

Official Languages (OL) recommendations

Best practices to follow for unilingual and bilingual meetings or events for both official languages (English and French).

Job aid on planning Accessible Virtual Events from the Canada School of Public Service

This job aid provides best practices on how to plan accessible and inclusive virtual events.

Office for Disability Issues (ODI) is proud to present this handbook to colleagues across the Government of Canada to provide guidance on planning inclusive and accessible events.

Proposed meeting types with accessibility features

Our recommendations for choosing virtual meeting platforms based on the type of meeting or event, number of people, and content shared.

GCwiki Microsoft 365/Teams

A collection of MS Teams training products to support public servants.

Take advantage of the accessibility features in Microsoft Teams for a better meeting or live event experience - Office Support

For a better Microsoft Teams meeting or live event experience, check out the following accessibility features in Microsoft Teams.

The Association of Translators and Interpreters of Ontario (ATIO) Directory

Find a translator, interpreter or terminologist for meetings and events.

Best practices for your conference and sign language interpretation requests

Virtual meeting platforms and accessibility features

Microsoft Teams and Zoom virtual meeting platforms offer a variety of accessibility features that meet different needs for participating in meetings and chats.

Development

Accessibility Support

Check if your code will work with assistive technologies.

Centrally Deployed Templates Solution (CDTS)

The purpose of the CDTS is essentially to deliver the presentation layer of the Canada.ca theme or Intranet.canada.ca theme to web assets.

How to Meet WCAG (Quickref Reference) (w3.org)

A customizable quick reference to Web Content Accessibility Guidelines (WCAG) 2 requirements (success criteria) and techniques.

Web Accessibility Assessment Methodology (Level AA)

Assist with measuring conformance to the Web Content Accessibility Guidelines (WCAG) 2.1 Level A and Level AA Success Criteria

Web Experience Toolkit (WET)

An award-winning front-end framework for building websites that are accessible, usable, interoperable, mobile friendly and multilingual

Web Accessibility Checklist

Accessibility checklist developed by ESDC.

Canada.ca Design System

Use this design system to provide a more usable, consistent and trustworthy online experience for people who access Government of Canada digital services.

Design system content includes:

Canada.ca blog

Evidence and insights on improving information and services on Canada.ca

Canada.ca Content and Information Architecture Specification

Who has to use the Canada.ca design system, mandatory elements, how to organize content and design principles

Canada.ca Content Style guide

Writing principles and techniques to make content clear and accessible to all

Continuous improvement of web content

Choosing what to improve, organizing and preparing your team, research and prototyping, designing content, monitoring and measuring success

Latest changes to the Canada.ca design system

Latest changes to the design system, templates and patterns, style guide and other tools

Template and design pattern library

User-tested templates, page layouts, design patterns, guidelines, and code samples

Learning

A way with words and images

Suggestions for the portrayal of people with disabilities. People with disabilities are asking Canadians, and the media in particular, to use respectful terms when writing and speaking about them or about issues that affect their lives. They are also asking that images chosen to portray them be respectful and not reinforce outdated stereotypes.

Accessibility Courses

GitHub recommended courses, webinars, educational videos, and more, offered in web accessibility.

ESDC Accessible Documents

The core steps needed for accessibility are the same regardless of whether your document is in HTML, Microsoft Word, Adobe PDF, or another document format. We have gathered resources to assist you and ensure that everyone, including persons with disabilities, can read and understand your documents.

Apple Accessibility - YouTube

From using your iPhone without seeing the screen, to adapting gestures to your physical needs, discover how the accessibility features built into your Apple devices can help you do more.

ESDC Self-paced Web Accessibility Course - IT Accessibility office

This course is designed for designers, developers, testers, trainers, content authors, project managers and anyone who's interested in learning more about web accessibility.

Introduction to Web Accessibility

Introduction to web accessibility and additional resources provided by the W3C | Web Accessibility Initiative.

International Association of Accessibility Professionals

Accessibility professionals from around the world come together to define, promote and improve the accessibility profession through networking, education and certification.

Microsoft Windows 11 Accessibility Features

Useful resources on Microsoft Windows 11 accessibility features.

Screen reader considerations when choosing between Google at IU My Drive and Microsoft OneDrive at IU

The choice between Google at IU My Drive and Microsoft OneDrive at IU is not simple when considering screen reader accessibility. There are pros and cons to both, which can differ depending on the screen reader and browser combination used.

The structure of Web Content Accessibility Guidelines (WCAG) 2.1

ESDC developed resource of the WCAG 2.1 guidelines structure.

Policy

Accessibility Strategy for the Public Service of Canada

Improving accessibility, accommodations, ergonomics, data, and internships. Accessibility strategy for the public service

Authoring Tool Accessibility Guidelines (ATAG) Overview from the Web Accessibility Initiative (WAI)

Authoring tools are software and services that “authors” (web developers, designers, writers, etc.) use to produce web content (static web pages, dynamic web applications, etc.).

Directive on Service and Digital- Canada.ca

Articulates how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era.

Directive on the Duty to Accommodate- Canada.ca

Provides direction to managers and heads of HR on their obligations with respect to duty to accommodate, with the objective of developing an inclusive, barrier-free workplace in which all persons have equal access to opportunities in the core public administration.

Directive on the Management of Communications- Canada.ca

Provides rules for managing and coordinating communications, including procedures for advertising, public opinion research, social media and web communications.

EU EN 301 549 (Managing accessibility in the public procurement of ICT)(PDF, 2 MB)

Accessibility requirements suitable for public procurement of ICT products and services in Europe.

Guideline on Making Information Technology Usable by All

This guideline supports the Government of Canada’s direction to ensure that departments, agencies and organizations consider accessibility in the acquisition or development of information technology (IT) solutions and equipment to make IT usable by all.

Web Content Accessibility Guidelines (WCAG) 2.1 (w3.org)

Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will also often make Web content more usable to users in general.

Accessible Canada Act

Online source of the consolidated Acts and regulations of Canada.

Accessible Canada Act in Plain Language | Federal Accessibility Legislation Alliance

This document is meant to help people understand the main points of Bill C-81, an Act to ensure a barrier-free Canada.

Accessibility Glossary

This glossary contains 342 concepts and terminology related to Bill C-81 in the fields of sociology of work and technical aids for persons with disabilities.

Procurement

Accessibility at Public Services and Procurement Canada (PSPC)

As the Government of Canada’s common service provider, PSPC works to provide excellent service to other federal departments. By aiming to improve access to its programs and services for people with disabilities, PSPC helps federal departments provide high-quality programs and services to all Canadians.

Services

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Additional Resources

Resources and useful tools for web accessibility for employees of the Government of Canada.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

On this page

Accessible meetings and events

Virtual meetings and events come in various formats and sizes – from small workshops with participants who know each other to large public meetings you are planning. It is critical to ensure meetings and events are fully accessible, from accessing them, to the presentations. By planning ahead, you can build accessibility into all aspects of the meeting. This will allow everyone to participate fully, including people with disabilities.

In order to assist you in offering a fully accessible virtual meeting/event, whether it is a training session, a meeting, a kiosk or an open-door event, the IT Accessibility Office (ITAO) has gathered the most relevant information on the subject.

Accessible meeting/event guidelines

Proper planning of meetings and events is essential for the inclusion of all. There are several things to consider in the to-do list before and during meetings/events.

Accessibility overview of Microsoft Teams

Microsoft Teams is a messaging and collaboration app that lets everyone in your organization join the conversation and work together. This page contains an overview of the many accessibility features that make sure all users can have the best possible experience.

Best practices for setting up and running a Teams meeting or Live event for the deaf and hard of hearing (microsoft.com)

This page contains an overview of the many accessibility features that make sure all users can have the best possible experience, including accessibility features for a better meeting or live event experience, and best practices for setting up and running a Teams meeting or Live event for the deaf and hard of hearing.

CART services and Sign Language Interpreters (SLI)

The most common accommodations for meetings or events are Communication Access Realtime Translation (CART) and interpretation services.

Official Languages (OL) recommendations

Best practices to follow for unilingual and bilingual meetings or events for both official languages (English and French).

Job aid on planning Accessible Virtual Events from the Canada School of Public Service

This job aid provides best practices on how to plan accessible and inclusive virtual events.

Office for Disability Issues (ODI) is proud to present this handbook to colleagues across the Government of Canada to provide guidance on planning inclusive and accessible events.

Proposed meeting types with accessibility features

Our recommendations for choosing virtual meeting platforms based on the type of meeting or event, number of people, and content shared.

GCwiki Microsoft 365/Teams

A collection of MS Teams training products to support public servants.

Take advantage of the accessibility features in Microsoft Teams for a better meeting or live event experience - Office Support

For a better Microsoft Teams meeting or live event experience, check out the following accessibility features in Microsoft Teams.

The Association of Translators and Interpreters of Ontario (ATIO) Directory

Find a translator, interpreter or terminologist for meetings and events.

Best practices for your conference and sign language interpretation requests

Virtual meeting platforms and accessibility features

Microsoft Teams and Zoom virtual meeting platforms offer a variety of accessibility features that meet different needs for participating in meetings and chats.

Development

Accessibility Support

Check if your code will work with assistive technologies.

Centrally Deployed Templates Solution (CDTS)

The purpose of the Centrally Deployed Templates Solution (CDTS is essentially to deliver the presentation layer of the Canada.ca theme or Intranet.canada.ca theme to web assets.

How to Meet WCAG (Quickref Reference) (w3.org)

A customizable quick reference to Web Content Accessibility Guidelines (WCAG) 2 requirements (success criteria) and techniques.

Web Accessibility Assessment Methodology (Level AA)

Assist with measuring conformance to the Web Content Accessibility Guidelines (WCAG) 2.1 Level A and Level AA Success Criteria

Web Experience Toolkit (WET)

An award-winning front-end framework for building websites that are accessible, usable, interoperable, mobile friendly and multilingual

Web Accessibility Checklist

Accessibility checklist developed by ESDC.

Canada.ca Design System

Use this design system to provide a more usable, consistent and trustworthy online experience for people who access Government of Canada digital services.

Design system content includes:

Canada.ca blog

Evidence and insights on improving information and services on Canada.ca

Canada.ca Content and Information Architecture Specification

Who has to use the Canada.ca design system, mandatory elements, how to organize content and design principles

Canada.ca Content Style guide

Writing principles and techniques to make content clear and accessible to all

Continuous improvement of web content

Choosing what to improve, organizing and preparing your team, research and prototyping, designing content, monitoring and measuring success

Latest changes to the Canada.ca design system

Latest changes to the design system, templates and patterns, style guide and other tools

Template and design pattern library

User-tested templates, page layouts, design patterns, guidelines, and code samples

Learning

A way with words and images

Suggestions for the portrayal of people with disabilities. People with disabilities are asking Canadians, and the media in particular, to use respectful terms when writing and speaking about them or about issues that affect their lives. They are also asking that images chosen to portray them be respectful and not reinforce outdated stereotypes.

Accessibility Courses

GitHub recommended courses, webinars, educational videos, and more, offered in web accessibility.

ESDC Accessible Documents

The core steps needed for accessibility are the same regardless of whether your document is in HTML, Microsoft Word, Adobe PDF, or another document format. We have gathered resources to assist you and ensure that everyone, including persons with disabilities, can read and understand your documents.

Apple Accessibility - YouTube

From using your iPhone without seeing the screen, to adapting gestures to your physical needs, discover how the accessibility features built into your Apple devices can help you do more.

ESDC Self-paced Web Accessibility Course - IT Accessibility office

This course is designed for designers, developers, testers, trainers, content authors, project managers and anyone who's interested in learning more about web accessibility.

Introduction to Web Accessibility

Introduction to web accessibility and additional resources provided by the W3C | Web Accessibility Initiative.

International Association of Accessibility Professionals

Accessibility professionals from around the world come together to define, promote and improve the accessibility profession through networking, education and certification.

Microsoft Windows 11 Accessibility Features

Useful resources on Microsoft Windows 11 accessibility features.

Screen reader considerations when choosing between Google at IU My Drive and Microsoft OneDrive at IU

The choice between Google at IU My Drive and Microsoft OneDrive at IU is not simple when considering screen reader accessibility. There are pros and cons to both, which can differ depending on the screen reader and browser combination used.

The structure of Web Content Accessibility Guidelines (WCAG) 2.1

ESDC developed resource of the WCAG 2.1 guidelines structure.

Policy

Accessibility Strategy for the Public Service of Canada

Improving accessibility, accommodations, ergonomics, data, and internships. Accessibility strategy for the public service

Authoring Tool Accessibility Guidelines (ATAG) Overview from the Web Accessibility Initiative (WAI)

Authoring tools are software and services that “authors” (web developers, designers, writers, etc.) use to produce web content (static web pages, dynamic web applications, etc.).

Directive on Service and Digital- Canada.ca

Articulates how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era.

Directive on the Duty to Accommodate- Canada.ca

Provides direction to managers and heads of HR on their obligations with respect to duty to accommodate, with the objective of developing an inclusive, barrier-free workplace in which all persons have equal access to opportunities in the core public administration.

Directive on the Management of Communications- Canada.ca

Provides rules for managing and coordinating communications, including procedures for advertising, public opinion research, social media and web communications.

EU EN 301 549 (Managing accessibility in the public procurement of ICT)(PDF, 2 MB)

Accessibility requirements suitable for public procurement of ICT products and services in Europe.

Guideline on Making Information Technology Usable by All

This guideline supports the Government of Canada’s direction to ensure that departments, agencies and organizations consider accessibility in the acquisition or development of information technology (IT) solutions and equipment to make IT usable by all.

Web Content Accessibility Guidelines (WCAG) 2.1 (w3.org)

Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will also often make Web content more usable to users in general.

Accessible Canada Act

Online source of the consolidated Acts and regulations of Canada.

Accessible Canada Act in Plain Language | Federal Accessibility Legislation Alliance

This document is meant to help people understand the main points of Bill C-81, an Act to ensure a barrier-free Canada.

Accessibility Glossary

This glossary contains 342 concepts and terminology related to Bill C-81 in the fields of sociology of work and technical aids for persons with disabilities.

Procurement

Accessibility at Public Services and Procurement Canada (PSPC)

As the Government of Canada’s common service provider, PSPC works to provide excellent service to other federal departments. By aiming to improve access to its programs and services for people with disabilities, PSPC helps federal departments provide high-quality programs and services to all Canadians.

Services

Page details

Date modified:
\ No newline at end of file diff --git a/en/alternative-text-and-long-description-best-practices/index.html b/en/alternative-text-and-long-description-best-practices/index.html index f25e54788..fc1cab5e7 100644 --- a/en/alternative-text-and-long-description-best-practices/index.html +++ b/en/alternative-text-and-long-description-best-practices/index.html @@ -1,4 +1,4 @@ -Alternative text and long description – Best practices - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Alternative text and long description – Best practices

Alternative text (or alt text) is text that describes and conveys the meaning of a visual non-text item like an image, flowchart, graph and so on. This document will guide you to determine the type of alt text needed and provide you with tips on writing an alt text and long descriptions for simple and complex images, like charts, maps and so on.

Description

Alternative text, also known as alt text or alt tags is text that describes and conveys the meaning of a visual non-text item like an image, flowchart, graph or table.

Adding an alt text benefits many users, such as:

Determining the type of alt text

Ask yourself the following questions:

If the image does not convey information or the information is available in the document/page, it’s decorative.

Alt text for decorative images

For Word and PowerPoint, type ‘Decorative’ in the alt text box. Do not check the box ‘Mark it as decorative’ as some people may use an older version of Word/PowerPoint and the checkbox will not apply.

Marking an image as decorative varies between Learning Management Systems (LMSs). When designing a web product in HTML, W3C recommends using a null (or empty) alt text which is an open and closed quotation mark (alt=“”).

Meaningful alt text

For example: The water cycle, a long description follows.

Text as images

Sometimes users will want to customize text to suit their needs, like increase the font size, change the font color and so on. When text is presented as an image, it’s difficult for a user to customize the text. When possible, use text along with CSS to apply styling like the font family, color.

If a logo is being used, provide an alt text of the text in the logo.

Complex images

Charts and Graphs

The alt text should include the following information:

Your long description should provide the same information that’s presented in the chart or graph. It should include information like:

Depending on the graph and the information it’s trying to convey, the long description can be presented as a table, keeping in mind the elements needed to create an accessible table.

Flowcharts and concept maps

When using a flowchart or concept map to show a process or the relationship between concepts, the long description can be written in a list-based outline format. PennState provides some examples of long descriptions for flowcharts and concept maps.

Tables

For Word and PowerPoint

HTML:

Maps

Like other images, when thinking of the alt text for maps, think about the purpose or context of the map. Is it showing a location? Multiple locations? Directions?

A location or landmarks or locations

Include the landmark and address. For example: The House of Commons is located at West Block (111 Wellington Street) on Parliament Hill in Ottawa, Ontario.

Multiple locations or landmarks

Provide context on what the locations or landmarks are of. If the map is showing multiple locations or landmarks, a long description will most likely be needed. For example: Bus stop locations in Downtown Fredericton. Long description follows.

Directions

If the map is showing directions, the alt text should reflect that. The long description would be a simple, text based directions. For example: Directions from Airport Station (stop ID 5844) to the Canada Justice Department. Long description follows.

Tips for writing long descriptions

Useful links about text alternative

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Alternative text and long description – Best practices

Alternative text (or alt text) is text that describes and conveys the meaning of a visual non-text item like an image, flowchart, graph and so on. This document will guide you to determine the type of alt text needed and provide you with tips on writing an alt text and long descriptions for simple and complex images, like charts, maps and so on.

Description

Alternative text, also known as alt text or alt tags is text that describes and conveys the meaning of a visual non-text item like an image, flowchart, graph or table.

Adding an alt text benefits many users, such as:

Determining the type of alt text

Ask yourself the following questions:

If the image does not convey information or the information is available in the document/page, it’s decorative.

Alt text for decorative images

For Word and PowerPoint, type ‘Decorative’ in the alt text box. Do not check the box ‘Mark it as decorative’ as some people may use an older version of Word/PowerPoint and the checkbox will not apply.

Marking an image as decorative varies between Learning Management Systems (LMSs). When designing a web product in HTML, W3C recommends using a null (or empty) alt text which is an open and closed quotation mark (alt=“”).

Meaningful alt text

For example: The water cycle, a long description follows.

Text as images

Sometimes users will want to customize text to suit their needs, like increase the font size, change the font color and so on. When text is presented as an image, it’s difficult for a user to customize the text. When possible, use text along with CSS to apply styling like the font family, color.

If a logo is being used, provide an alt text of the text in the logo.

Complex images

Charts and Graphs

The alt text should include the following information:

Your long description should provide the same information that’s presented in the chart or graph. It should include information like:

Depending on the graph and the information it’s trying to convey, the long description can be presented as a table, keeping in mind the elements needed to create an accessible table.

Flowcharts and concept maps

When using a flowchart or concept map to show a process or the relationship between concepts, the long description can be written in a list-based outline format. PennState provides some examples of long descriptions for flowcharts and concept maps.

Tables

For Word and PowerPoint

HTML:

Maps

Like other images, when thinking of the alt text for maps, think about the purpose or context of the map. Is it showing a location? Multiple locations? Directions?

A location or landmarks or locations

Include the landmark and address. For example: The House of Commons is located at West Block (111 Wellington Street) on Parliament Hill in Ottawa, Ontario.

Multiple locations or landmarks

Provide context on what the locations or landmarks are of. If the map is showing multiple locations or landmarks, a long description will most likely be needed. For example: Bus stop locations in Downtown Fredericton. Long description follows.

Directions

If the map is showing directions, the alt text should reflect that. The long description would be a simple, text based directions. For example: Directions from Airport Station (stop ID 5844) to the Canada Justice Department. Long description follows.

Tips for writing long descriptions

Useful links about text alternative

Page details

Date modified:
\ No newline at end of file diff --git a/en/audio-description-guidelines/index.html b/en/audio-description-guidelines/index.html index ab361f7e1..2e4c83eec 100644 --- a/en/audio-description-guidelines/index.html +++ b/en/audio-description-guidelines/index.html @@ -1,4 +1,4 @@ -Audio Description Guidelines - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Audio Description Guidelines

Audio description allows any user with a visual disability or cognitive disability to receive a very detailed and descriptive experience of what is happening on the screen for every aspect of the video.

Audio description is sometimes known as described video, video description, or visual interpretation.

Audio description allows any user with a visual disability or cognitive disability to receive a very detailed and descriptive experience of what is happening on the screen for every aspect of the video. A number of organizations require Audio description (AD) and Described video (DV), or video description in video, such as the Canadian Radio-television and Telecommunications Commission (CRTC).

Audio description is also used by sighted individuals, so both audio and video elements are needed (for example, someone with some vision loss who can not read the text but wants to see the rest).

Audio description and described video make TV programs accessible for people who are blind or who have visual impairments:

Audio description (AD):
Relies on a program host or announcer to provide a voice-over by reading aloud or describing key elements of programming, such as text and graphics that appear on the screen. It is often used for information-based programming, including newscasts, weather reports, sports scores, and financial data. Most broadcasters are required to provide audio description.
Described video (DV), or video description:
A narrated description of a program's main visual elements, such as settings, costumes, and body language. The description is added during pauses in dialogue and enables people to form a mental picture of what is happening in the program. Described video typically uses a separate audio track.

Source: TV access for people who are blind or partially sighted : Described video and audio description | CRTC

Note: If audio description is being used for a video, then the descriptions need to be included in the transcript.

Audio Description Checklist

Does the audio description:

Is the audio description:

Keyboard Access Guidelines

Accessible media players provide a user interface that works without a mouse, through speech interface, when the page is zoomed larger, and with screen readers. For example, media players need to:

Some media players provide additional accessibility functionality to users such as:

Keyboard Access Checklist

Using a keyboard, does the media player:

Does the time-based media player support (have an icon/link for)?

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Audio Description Guidelines

Audio description allows any user with a visual disability or cognitive disability to receive a very detailed and descriptive experience of what is happening on the screen for every aspect of the video.

Audio description is sometimes known as described video, video description, or visual interpretation.

Audio description allows any user with a visual disability or cognitive disability to receive a very detailed and descriptive experience of what is happening on the screen for every aspect of the video. A number of organizations require Audio description (AD) and Described video (DV), or video description in video, such as the Canadian Radio-television and Telecommunications Commission (CRTC).

Audio description is also used by sighted individuals, so both audio and video elements are needed (for example, someone with some vision loss who can not read the text but wants to see the rest).

Audio description and described video make TV programs accessible for people who are blind or who have visual impairments:

Audio description (AD):
Relies on a program host or announcer to provide a voice-over by reading aloud or describing key elements of programming, such as text and graphics that appear on the screen. It is often used for information-based programming, including newscasts, weather reports, sports scores, and financial data. Most broadcasters are required to provide audio description.
Described video (DV), or video description:
A narrated description of a program's main visual elements, such as settings, costumes, and body language. The description is added during pauses in dialogue and enables people to form a mental picture of what is happening in the program. Described video typically uses a separate audio track.

Source: TV access for people who are blind or partially sighted : Described video and audio description | CRTC

Note: If audio description is being used for a video, then the descriptions need to be included in the transcript.

Audio Description Checklist

Does the audio description:

Is the audio description:

Keyboard Access Guidelines

Accessible media players provide a user interface that works without a mouse, through speech interface, when the page is zoomed larger, and with screen readers. For example, media players need to:

Some media players provide additional accessibility functionality to users such as:

Keyboard Access Checklist

Using a keyboard, does the media player:

Does the time-based media player support (have an icon/link for)?

Page details

Date modified:
\ No newline at end of file diff --git a/en/auditory-disabilities/index.html b/en/auditory-disabilities/index.html index 502af7054..920e954e6 100644 --- a/en/auditory-disabilities/index.html +++ b/en/auditory-disabilities/index.html @@ -1,4 +1,4 @@ -Auditory Disabilities - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Auditory Disabilities

Auditory disabilities are sensory disabilities that range from partial to complete hearing loss.

Deafness

Definition:
Deafness is the total or near total loss of hearing.
Characteristics:
A person who is deaf or hard of hearing has difficulty with sounds, including the audio part of multimedia materials. Many, but not all, people who are deaf know sign language. For people who were born deaf, sign language is often their first language and so their preferred native language. They may feel less comfortable reading printed or digital text because it is a foreign language for them, and the phonetic notation does not help their comprehension. By way of contrast, those who lose their hearing later in life (deafened) may never learn sign language, or if they learn it, they may not feel as comfortable speaking in sign, and may prefer text.

Hard of Hearing

Definition:
Hard of hearing (HOH) refers to people with hearing loss ranging from mild to severe, who still have some useful hearing, and may communicate through sign language, spoken language, or both, understand spoken language in some situations, with or without amplification. Most HOH people can use the phone and use hearing aids.
Characteristics:
Individuals who are hard of hearing have partially-impaired hearing in one or both ears, resulting in a mild-to-moderate hearing loss. There may be enough residual hearing that an auditory device, such as a hearing aid or frequency modulation (FM) system, provides sufficient assistance to process speech. A person who hard of hearing has difficulty with sounds, including the audio part of multimedia materials.

Central Auditory Processing Disorder

Definition:

According to the American Speech-Language-Hearing Association:

  • Auditory processing disorder (APD) is often described as greater than expected difficulty hearing and understanding speech even though no measurable hearing loss exists. Individuals with auditory processing disorders may act as though a hearing loss is present when in fact, hearing sensitivity is often within normal limits. APD is often confused with other disorders such as as Attention-Deficit Hyperactivity Disorder (ADHD), language impairment, learning disabilities, social and emotional delays or cognitive deficits.
  • APD isn’t the inability to hear. It is the inability to interpret, organize, or analyze what is heard. All the parts of the hearing pathway are working well. But parts of the brain are not.
Characteristics:

Behaviors can vary depending on the individual and the presence of other disorders. People with Central Auditory Processing Disorder can have difficulty with, among other things:

  • Finding the source of a sound
  • Understanding what someone is saying in noisy environments or with competing sounds
  • Following spoken directions
  • Learning songs or instruments
  • Paying attention
  • Responding in a timely way
  • Learning a new language

Barriers for People with Auditory Disabilities

From the W3C’s Web Accessibility Initiative and other sources:

Deafness and Hard of Hearing Challenges and Solutions

Cannot hear talks, presentations, and performances:

Cannot hear the audio part of videos:

Cannot hear doorbells, alarms, and other alerts:

Adaptive Technologies and Adaptive Strategies

Here are some commonly used products and strategies:

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Auditory Disabilities

Auditory disabilities are sensory disabilities that range from partial to complete hearing loss.

Deafness

Definition:
Deafness is the total or near total loss of hearing.
Characteristics:
A person who is deaf or hard of hearing has difficulty with sounds, including the audio part of multimedia materials. Many, but not all, people who are deaf know sign language. For people who were born deaf, sign language is often their first language and so their preferred native language. They may feel less comfortable reading printed or digital text because it is a foreign language for them, and the phonetic notation does not help their comprehension. By way of contrast, those who lose their hearing later in life (deafened) may never learn sign language, or if they learn it, they may not feel as comfortable speaking in sign, and may prefer text.

Hard of Hearing

Definition:
Hard of hearing (HOH) refers to people with hearing loss ranging from mild to severe, who still have some useful hearing, and may communicate through sign language, spoken language, or both, understand spoken language in some situations, with or without amplification. Most HOH people can use the phone and use hearing aids.
Characteristics:
Individuals who are hard of hearing have partially-impaired hearing in one or both ears, resulting in a mild-to-moderate hearing loss. There may be enough residual hearing that an auditory device, such as a hearing aid or frequency modulation (FM) system, provides sufficient assistance to process speech. A person who hard of hearing has difficulty with sounds, including the audio part of multimedia materials.

Central Auditory Processing Disorder

Definition:

According to the American Speech-Language-Hearing Association:

  • Auditory processing disorder (APD) is often described as greater than expected difficulty hearing and understanding speech even though no measurable hearing loss exists. Individuals with auditory processing disorders may act as though a hearing loss is present when in fact, hearing sensitivity is often within normal limits. APD is often confused with other disorders such as as Attention-Deficit Hyperactivity Disorder (ADHD), language impairment, learning disabilities, social and emotional delays or cognitive deficits.
  • APD isn’t the inability to hear. It is the inability to interpret, organize, or analyze what is heard. All the parts of the hearing pathway are working well. But parts of the brain are not.
Characteristics:

Behaviors can vary depending on the individual and the presence of other disorders. People with Central Auditory Processing Disorder can have difficulty with, among other things:

  • Finding the source of a sound
  • Understanding what someone is saying in noisy environments or with competing sounds
  • Following spoken directions
  • Learning songs or instruments
  • Paying attention
  • Responding in a timely way
  • Learning a new language

Barriers for People with Auditory Disabilities

From the W3C’s Web Accessibility Initiative and other sources:

Deafness and Hard of Hearing Challenges and Solutions

Cannot hear talks, presentations, and performances:

Cannot hear the audio part of videos:

Cannot hear doorbells, alarms, and other alerts:

Adaptive Technologies and Adaptive Strategies

Here are some commonly used products and strategies:

Page details

Date modified:
\ No newline at end of file diff --git a/en/best-practices-for-accessible-virtual-events/index.html b/en/best-practices-for-accessible-virtual-events/index.html index 82a567aa8..c751498c4 100644 --- a/en/best-practices-for-accessible-virtual-events/index.html +++ b/en/best-practices-for-accessible-virtual-events/index.html @@ -1,4 +1,4 @@ -Best practices for accessible virtual events - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Best practices for accessible virtual events

This guide is all about planning events, covering a broad range of activities like conferences, meetings, and presentations. It includes common barriers faced by people with disabilities during events and a suggested timeline for organizing your event. The goal is to work together to create more inclusive and accessible experiences.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

Best practices for accessible virtual events (Word, 71 KB)

On this page

Introduction

For the purposes of this content, the term “event” includes activities such as: events, conferences, meetings, kiosks, training, presentations, and more.

This guide provides a suggested timeline for planning your event, but it is not prescriptive.

Common issues reported by people with disabilities

Before exploring this guide, we invite you to review common barriers about events that we collected from persons with disabilities. Please collaborate with us to address the following challenges.

Audio

Visual

Mobility

Cognitive

In Canada, the Accessible Canada Act, along with the Canadian Human Rights Act and the Directive on the Duty to Accommodate, urges us to create accessible events. This legal framework protects the rights of persons with disabilities to ensure their full participation in society.

Here is a short summary of their relationship with handling events:

Accessible Canada Act

Aims for a barrier-free Canada by January 1, 2040, requiring the identification, removal and prevention of barriers in areas which include:

Human Rights Legislation

Prohibits disability-based discrimination.

Directive on the Duty to Accommodate

Ensures the full participation of persons with disabilities by designing all systems, processes and facilities to be accessible from the start. When a barrier cannot be removed, the individual must be accommodated.

Facts to keep in mind

About accommodations

About disabilities

About careful planning

Virtual events

Roadmap

First, you will be planning your event. Multiple decisions will have to be made, notably:

Second you will get ready to run your event. We recommend:

Third, you will run your event. Please ensure:

Finally, after the event, you will want to:

Plan the event: 1 to 2 months before the event (approximately)

Decide if the event is bilingual or two unilingual sessions

One session in French one session in English (best choice for accessibility)

When possible schedule two separate sessions, one in French and one in English. This is especially good for mandatory and statutory training.

Bilingual (best choice for official languages requirement)

Bilingual events are an option, especially for conferences and all-staff / weekly events.

When organizing a bilingual event, you will want to ensure:

Resources for bilingual events

Decide which virtual platform to host your event

Please choose a platform whose user interface that conforms to level AA of the WCAG 2.1 standard. Additionally, we recommend reaching out to users with disabilities to test the usability of your platform and the way you’ve implemented your event. Refer to Selecting an accessible remote meeting platform from the Accessibility of Remote Meetings W3C Group Note (w3.org) for detailed guidance.

Assign roles and responsibilities to your event staff

Smaller events may have some staff with multiple roles. Bigger events will present more challenges and will necessitate a greater distribution of tasks. Keep in mind that third parties, like audio-visual production companies, can be used to handle some of these tasks.

In general, we usually see the following roles, this guidance is not prescriptive:

Host / Leader of the event

Note: It is recommended to have one host / leader of the event as attendees feel more comfortable hearing a familiar voice.

Moderator(s)
Presenter(s)
Administrator / Support
Notetaker

Note: The distribution of notes after the event is important, especially for attendees who have difficulties listening and writing at the same time.

Book accommodation services once the date is confirmed

Accommodations may be necessary to fulfill the obligations outlines in the Directive on the Duty to Accommodate.

Note: Please provide the presentation material (such as PowerPoint, Word, email, pre-recorded videos) to service providers in advance. Due to high demand, we suggest submitting your requests at least 4 weeks before the event.

Sign language interpretation services (ASL, LSQ)

People who are deaf, hard of hearing, or sign language-fluent may struggle with written captions as it's their second language. Sign language interpretation also enhances the experience by conveying intonation, emotion, and meaningful audio information.

Communication Access Realtime Translation (CART)

Captions enables people who are deaf, have a hearing loss and people who have cognitive disabilities like auditory processing difficulties, and even people for who French and English might not be their first language, to be able to fully participate in live events.

Warning: Some virtual events platforms offer automated live captions, like Microsoft Teams Live Captions. Unfortunately, these technologies often make errors which disadvantages users who rely on captions. Automated captions should be used as a last resort only or for events of lower importance. Use Communication Access Realtime Translation (CART) instead.

Simultaneous translation interpretation services

Bilingual events can be a barrier for unilingual individuals with disabilities. To ensure full accessibility, simultaneous voiced translations are necessary. Translated captions or on-screen content alone cannot be accessed by non-visual users. As a result, they must wait for language switches without any stimuli and rely solely on summaries of the talking points in their language.

Note: This requires a virtual platform that offers multiple voice channels, one for each language. When the presenter is no longer speaking the voice channel’s language, the interpreter assigned to the voice channel must speak the translation.

Ensure all event materials are accessible (such as email, PowerPoints, Word…)

All content distributed must be accessible and in both official languages. When possible, favour more accessible formats like HTML, Word, PowerPoint, ePub over less accessible formats like PDF.

Important: Always review the presenters’ material even when the presenter is external as you will be accountable for the accessibility of the content.

Training

Consider taking some training about accessibility. When content is made by people who have built their accessibility knowledge and they apply it from the beginning, it saves a lot of time and money by reducing the need for remediation and avoids potential complaints.

Please refer to the Digital Accessibility Toolkit to access more in-dept information through our guides. Additionally, we recommend watching the recorded CSPS workshop called “Making Documents Accessible (INC1-V46)”.

General document accessibility advice (applies to all)
Email quick tips
Power point quick tips
Word quick tips
Pre-recorded video quick tips

Send invitations to attendees

Build an agenda
Include event information in invitation

Make sure to include the following information in your event invitation:

Get ready: 1 to 2 weeks before the event (approximately)

Prepare the scripts

A script for the host can be especially useful to guide the event. Usually such a script contains the opening statements of the host, statements for during the Q&A sections and finally, closing remarks.

Below you will find an example of an opening statements script template that you can modify for your own purposes:

Welcome to our [name of event] about [add a quick description of the event]. My name is [say name] and I will be your Host today. [Host should take some time to acknowledge First Peoples and traditional territory (see guide).] I will first cover a few housekeeping points about today’s virtual event:

  • If you haven’t disconnected from the VPN yet, please do so for an optimal experience
  • Please keep your microphone muted and your video turned off throughout the event
  • To ask questions, either type into the chat function or wait until the question period to use the “raise your hand” feature, the keyboard shortcut is [give the keyboard shortcut]. Once you are selected to ask your question, please unmute yourself and show your video if you would like. We will triage your questions asked in the chat and answer them either in the chat or during the question period. Alternatively, we may ask that you email your question to our event email so we can address your question after this event I’m going to introduce our presenter today: [introduce presenter]

Preparing to present – Accessibility awareness for speakers

Host dry-runs (if needed)

The bigger or the more critical the event is, the better it is to host a dry-run.

We strongly recommend practice to ensure everyone is on the same page.

Day of the event

Test your set up about 15 to 30 minutes before the event

Start the event!

Invite participants to:

Fix mistakes

Wrap up the event

After the event

Send recap content

Make sure to distribute content in an accessible format, this is often done through a post-event “Thank you” email:

Respond to post-event questions

Respond in a timely manner.

Gather participants feedback

Ask for participants feedback and offer multiple ways to receive it, like either through email or through a form. It is important to get feedback to keep improving the quality of the events.

Here are some examples of topics and questions that can be asked:

For reference: What will affect your budget

For reference: Virtual platforms

Security warning: virtual event “bombing”

Terms like “Zoombombing”, “T-BOMB”, etc. have become popular terms to describe intrusion by strangers on the internet into virtual events. Usually, intruders try to disrupt the event by sharing their camera, making noise in their mic or using the “Share Screen” feature.

Here are a few tips to risk manage these attacks:

Information about Microsoft Teams

Accessibility standards conformance

Completed Voluntary Product Accessibility Template (VPAT)s for MS Teams can be found among Microsoft’s Accessibility Conformance Reports, use the Filter and choose “Teams” for the “Category”.

After setting up an event in MS Teams, it is possible to change the event options. To access the event options, activate the link at the bottom of the Teams generated event invite.

When possible, we recommend:

Additional resources for the organizer
Information you can include into invitation for attendees

Please visit the following links to learn more about Microsoft Teams:

Getting started

Accessibility

Reduce distractions

Event features

Note: Participants who enter a Microsoft Teams meeting after 1000 individuals have already joined will have a restricted, view-only experience. For more information on the controls and actions available in this view-only meeting experience, please refer to the following resource: "View-only meeting experience - Microsoft Teams | Microsoft Learn".

Information about WebEx

Accessibility standards conformance

Completed VPATs for WebEx can be found among those for their other products on their Voluntary Product Accessibility Templates - Cisco page, under the section “WebEx App”.

Information you can include into invitation for attendees

Please visit the following links to learn more about WebEx:

Getting Started

Accessibility

Reduce distractions

Event features

Information about Zoom

Accessibility standards conformance

Completed VPATs for Zoom can be found on their Accessibility page under the “Accessibility Documents” section.

Information you can include into invitation for attendees

Please visit the following links to learn more about Zoom:

Getting started

Accessibility

Reduce distractions

Event features

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Best practices for accessible virtual events

This guide is all about planning events, covering a broad range of activities like conferences, meetings, and presentations. It includes common barriers faced by people with disabilities during events and a suggested timeline for organizing your event. The goal is to work together to create more inclusive and accessible experiences.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

Best practices for accessible virtual events (Word, 71 KB)

On this page

Introduction

For the purposes of this content, the term “event” includes activities such as: events, conferences, meetings, kiosks, training, presentations, and more.

This guide provides a suggested timeline for planning your event, but it is not prescriptive.

Common issues reported by people with disabilities

Before exploring this guide, we invite you to review common barriers about events that we collected from persons with disabilities. Please collaborate with us to address the following challenges.

Audio

Visual

Mobility

Cognitive

In Canada, the Accessible Canada Act, along with the Canadian Human Rights Act and the Directive on the Duty to Accommodate, urges us to create accessible events. This legal framework protects the rights of persons with disabilities to ensure their full participation in society.

Here is a short summary of their relationship with handling events:

Accessible Canada Act

Aims for a barrier-free Canada by January 1, 2040, requiring the identification, removal and prevention of barriers in areas which include:

Human Rights Legislation

Prohibits disability-based discrimination.

Directive on the Duty to Accommodate

Ensures the full participation of persons with disabilities by designing all systems, processes and facilities to be accessible from the start. When a barrier cannot be removed, the individual must be accommodated.

Facts to keep in mind

About accommodations

About disabilities

About careful planning

Virtual events

Roadmap

First, you will be planning your event. Multiple decisions will have to be made, notably:

Second you will get ready to run your event. We recommend:

Third, you will run your event. Please ensure:

Finally, after the event, you will want to:

Plan the event: 1 to 2 months before the event (approximately)

Decide if the event is bilingual or two unilingual sessions

One session in French one session in English (best choice for accessibility)

When possible schedule two separate sessions, one in French and one in English. This is especially good for mandatory and statutory training.

Bilingual (best choice for official languages requirement)

Bilingual events are an option, especially for conferences and all-staff / weekly events.

When organizing a bilingual event, you will want to ensure:

Resources for bilingual events

Decide which virtual platform to host your event

Please choose a platform whose user interface that conforms to level AA of the WCAG 2.1 standard. Additionally, we recommend reaching out to users with disabilities to test the usability of your platform and the way you’ve implemented your event. Refer to Selecting an accessible remote meeting platform from the Accessibility of Remote Meetings W3C Group Note (w3.org) for detailed guidance.

Assign roles and responsibilities to your event staff

Smaller events may have some staff with multiple roles. Bigger events will present more challenges and will necessitate a greater distribution of tasks. Keep in mind that third parties, like audio-visual production companies, can be used to handle some of these tasks.

In general, we usually see the following roles, this guidance is not prescriptive:

Host / Leader of the event

Note: It is recommended to have one host / leader of the event as attendees feel more comfortable hearing a familiar voice.

Moderator(s)
Presenter(s)
Administrator / Support
Notetaker

Note: The distribution of notes after the event is important, especially for attendees who have difficulties listening and writing at the same time.

Book accommodation services once the date is confirmed

Accommodations may be necessary to fulfill the obligations outlines in the Directive on the Duty to Accommodate.

Note: Please provide the presentation material (such as PowerPoint, Word, email, pre-recorded videos) to service providers in advance. Due to high demand, we suggest submitting your requests at least 4 weeks before the event.

Sign language interpretation services (ASL, LSQ)

People who are deaf, hard of hearing, or sign language-fluent may struggle with written captions as it's their second language. Sign language interpretation also enhances the experience by conveying intonation, emotion, and meaningful audio information.

Communication Access Realtime Translation (CART)

Captions enables people who are deaf, have a hearing loss and people who have cognitive disabilities like auditory processing difficulties, and even people for who French and English might not be their first language, to be able to fully participate in live events.

Warning: Some virtual events platforms offer automated live captions, like Microsoft Teams Live Captions. Unfortunately, these technologies often make errors which disadvantages users who rely on captions. Automated captions should be used as a last resort only or for events of lower importance. Use Communication Access Realtime Translation (CART) instead.

Simultaneous translation interpretation services

Bilingual events can be a barrier for unilingual individuals with disabilities. To ensure full accessibility, simultaneous voiced translations are necessary. Translated captions or on-screen content alone cannot be accessed by non-visual users. As a result, they must wait for language switches without any stimuli and rely solely on summaries of the talking points in their language.

Note: This requires a virtual platform that offers multiple voice channels, one for each language. When the presenter is no longer speaking the voice channel’s language, the interpreter assigned to the voice channel must speak the translation.

Ensure all event materials are accessible (such as email, PowerPoints, Word…)

All content distributed must be accessible and in both official languages. When possible, favour more accessible formats like HTML, Word, PowerPoint, ePub over less accessible formats like PDF.

Important: Always review the presenters’ material even when the presenter is external as you will be accountable for the accessibility of the content.

Training

Consider taking some training about accessibility. When content is made by people who have built their accessibility knowledge and they apply it from the beginning, it saves a lot of time and money by reducing the need for remediation and avoids potential complaints.

Please refer to the Digital Accessibility Toolkit to access more in-dept information through our guides. Additionally, we recommend watching the recorded CSPS workshop called “Making Documents Accessible (INC1-V46)”.

General document accessibility advice (applies to all)
Email quick tips
Power point quick tips
Word quick tips
Pre-recorded video quick tips

Send invitations to attendees

Build an agenda
Include event information in invitation

Make sure to include the following information in your event invitation:

Get ready: 1 to 2 weeks before the event (approximately)

Prepare the scripts

A script for the host can be especially useful to guide the event. Usually such a script contains the opening statements of the host, statements for during the Q&A sections and finally, closing remarks.

Below you will find an example of an opening statements script template that you can modify for your own purposes:

Welcome to our [name of event] about [add a quick description of the event]. My name is [say name] and I will be your Host today. [Host should take some time to acknowledge First Peoples and traditional territory (see guide).] I will first cover a few housekeeping points about today’s virtual event:

  • If you haven’t disconnected from the VPN yet, please do so for an optimal experience
  • Please keep your microphone muted and your video turned off throughout the event
  • To ask questions, either type into the chat function or wait until the question period to use the “raise your hand” feature, the keyboard shortcut is [give the keyboard shortcut]. Once you are selected to ask your question, please unmute yourself and show your video if you would like. We will triage your questions asked in the chat and answer them either in the chat or during the question period. Alternatively, we may ask that you email your question to our event email so we can address your question after this event I’m going to introduce our presenter today: [introduce presenter]

Preparing to present – Accessibility awareness for speakers

Host dry-runs (if needed)

The bigger or the more critical the event is, the better it is to host a dry-run.

We strongly recommend practice to ensure everyone is on the same page.

Day of the event

Test your set up about 15 to 30 minutes before the event

Start the event!

Invite participants to:

Fix mistakes

Wrap up the event

After the event

Send recap content

Make sure to distribute content in an accessible format, this is often done through a post-event “Thank you” email:

Respond to post-event questions

Respond in a timely manner.

Gather participants feedback

Ask for participants feedback and offer multiple ways to receive it, like either through email or through a form. It is important to get feedback to keep improving the quality of the events.

Here are some examples of topics and questions that can be asked:

For reference: What will affect your budget

For reference: Virtual platforms

Security warning: virtual event “bombing”

Terms like “Zoombombing”, “T-BOMB”, etc. have become popular terms to describe intrusion by strangers on the internet into virtual events. Usually, intruders try to disrupt the event by sharing their camera, making noise in their mic or using the “Share Screen” feature.

Here are a few tips to risk manage these attacks:

Information about Microsoft Teams

Accessibility standards conformance

Completed Voluntary Product Accessibility Template (VPAT)s for MS Teams can be found among Microsoft’s Accessibility Conformance Reports, use the Filter and choose “Teams” for the “Category”.

After setting up an event in MS Teams, it is possible to change the event options. To access the event options, activate the link at the bottom of the Teams generated event invite.

When possible, we recommend:

Additional resources for the organizer
Information you can include into invitation for attendees

Please visit the following links to learn more about Microsoft Teams:

Getting started

Accessibility

Reduce distractions

Event features

Note: Participants who enter a Microsoft Teams meeting after 1000 individuals have already joined will have a restricted, view-only experience. For more information on the controls and actions available in this view-only meeting experience, please refer to the following resource: "View-only meeting experience - Microsoft Teams | Microsoft Learn".

Information about WebEx

Accessibility standards conformance

Completed VPATs for WebEx can be found among those for their other products on their Voluntary Product Accessibility Templates - Cisco page, under the section “WebEx App”.

Information you can include into invitation for attendees

Please visit the following links to learn more about WebEx:

Getting Started

Accessibility

Reduce distractions

Event features

Information about Zoom

Accessibility standards conformance

Completed VPATs for Zoom can be found on their Accessibility page under the “Accessibility Documents” section.

Information you can include into invitation for attendees

Please visit the following links to learn more about Zoom:

Getting started

Accessibility

Reduce distractions

Event features

Page details

Date modified:
\ No newline at end of file diff --git a/en/canada-school-of-public-service-csps/index.html b/en/canada-school-of-public-service-csps/index.html index 734c754b8..e35c3870a 100644 --- a/en/canada-school-of-public-service-csps/index.html +++ b/en/canada-school-of-public-service-csps/index.html @@ -1,4 +1,4 @@ -Canada School of Public Service (CSPS) - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Canada School of Public Service (CSPS)

The Canada School of Public Service leads the government's enterprise-wide approach to learning by providing a common, standardized curriculum that supports public servants through key career transitions, ensuring that they are equipped to serve Canadians with excellence. Multiple teams at the School support accessibility with the goal of creating a barrier free learning environment for its learners.

Policy, Priorities, and Partnership team

The Canada School of Public Service (CSPS) Policy, Priorities, and Partnership team have been focused on the development of the Accessibility Strategy for the School. As we are on route to creating a Barrier Free Canada by 2040 Government wide, at the School, we are ensuring that all our policy related tools all align with the expected accessibility requirements as defined on the Accessibility Act. In collaboration with the Future of Work Team, the School’s Diversity, and Inclusion Forum, and the UX Directorate we look forward to working towards achieving current and emerging initiatives in the Accessibility Strategy.

Future of Work/Employee Experience team

The CSPS Future of Work / Employee Experience team is working on the creation of the corporate accessibility plan, as required by the Accessible Canada Act. The plan is based on the current CSPS Accessibility Strategy, while ensuring that the CSPS is compliant with the new technical Accessible Canada Regulations.

The Future of Work team will be coordinating with all CSPS business lines involved in accessibility related policy, both from an employer and service provider standpoint. As well, we will be conducting consultations with employees who identify as Persons with Disabilities during the process of preparation of the accessibility plan which is scheduled to be published prior to December 2022.

Digital Academy team

The CSPS Digital Academy was established by the Canada School of Public Service (CSPS) in 2018 to help federal public servants gain the knowledge, skills and mindsets they need in the digital age. It supports the principles of Canada's Beyond2020 initiative for an agile, inclusive and equipped workforce and advocates for a digital-first approach that aligns with Canada's Digital Standards. These ten digital standards form the foundation of the government's shift to becoming more agile, open and user focused. One of the Digital Standards is to build in accessibility from the start. The CSPS Digital Academy endeavors to do this in our work, and we co-create content to support other public servants in doing the same.

Respectful and Inclusive Workplace (RIW) business line

CSPS’ Respectful and Inclusive Workplace (RIW) business line is responsible for the development and delivery of learning products on accessibility for the federal public servants. RIW works in close collaboration with partners such as the Office of Public Service Accessibility (OPSA), the Office of the Chief Human Resource Officer (OCHRO), the Accessibility, Accommodation and Adaptive Computer Technology (AAACT) team, and many other stakeholders to create informative, innovative, and engaging learning experiences on the topic of accessibility.

Digital Accessibility in Learning team

The CSPS Digital Accessibility in Learning team, under the User Experience division, provides our business lines with training, tools, guidelines, and advice to meet accessibility standards so that they can provide learners with a meaningful, inclusive, and accessible learning experience. Accessibility must be by design and by default. We are here to:

  • Lead the culture change towards accessible and inclusive design through training and technology support.
  • Establish and reinforce accessible and inclusive design best practices from the start.
  • Support the purchase of accessible learning solutions and accessible authoring tools.
  • Collaborate with other accessibility, design, research, and usability specialists within the School, and across the public service.
  • Establish guidelines, best practices, and processes for implementing and maintaining accessibility and inclusive products and services.
  • Provide coaching and professional development to School employees on accessibility.

To learn more about inclusion and accessibility, or to access help with your learning design or development, please contact the Digital Accessibility team.

digitalaccessibilityinlearning-accessibilitenumerique@csps-efpc.gc.ca

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Canada School of Public Service (CSPS)

The Canada School of Public Service leads the government's enterprise-wide approach to learning by providing a common, standardized curriculum that supports public servants through key career transitions, ensuring that they are equipped to serve Canadians with excellence. Multiple teams at the School support accessibility with the goal of creating a barrier free learning environment for its learners.

Policy, Priorities, and Partnership team

The Canada School of Public Service (CSPS) Policy, Priorities, and Partnership team have been focused on the development of the Accessibility Strategy for the School. As we are on route to creating a Barrier Free Canada by 2040 Government wide, at the School, we are ensuring that all our policy related tools all align with the expected accessibility requirements as defined on the Accessibility Act. In collaboration with the Future of Work Team, the School’s Diversity, and Inclusion Forum, and the UX Directorate we look forward to working towards achieving current and emerging initiatives in the Accessibility Strategy.

Future of Work/Employee Experience team

The CSPS Future of Work / Employee Experience team is working on the creation of the corporate accessibility plan, as required by the Accessible Canada Act. The plan is based on the current CSPS Accessibility Strategy, while ensuring that the CSPS is compliant with the new technical Accessible Canada Regulations.

The Future of Work team will be coordinating with all CSPS business lines involved in accessibility related policy, both from an employer and service provider standpoint. As well, we will be conducting consultations with employees who identify as Persons with Disabilities during the process of preparation of the accessibility plan which is scheduled to be published prior to December 2022.

Digital Academy team

The CSPS Digital Academy was established by the Canada School of Public Service (CSPS) in 2018 to help federal public servants gain the knowledge, skills and mindsets they need in the digital age. It supports the principles of Canada's Beyond2020 initiative for an agile, inclusive and equipped workforce and advocates for a digital-first approach that aligns with Canada's Digital Standards. These ten digital standards form the foundation of the government's shift to becoming more agile, open and user focused. One of the Digital Standards is to build in accessibility from the start. The CSPS Digital Academy endeavors to do this in our work, and we co-create content to support other public servants in doing the same.

Respectful and Inclusive Workplace (RIW) business line

CSPS’ Respectful and Inclusive Workplace (RIW) business line is responsible for the development and delivery of learning products on accessibility for the federal public servants. RIW works in close collaboration with partners such as the Office of Public Service Accessibility (OPSA), the Office of the Chief Human Resource Officer (OCHRO), the Accessibility, Accommodation and Adaptive Computer Technology (AAACT) team, and many other stakeholders to create informative, innovative, and engaging learning experiences on the topic of accessibility.

Digital Accessibility in Learning team

The CSPS Digital Accessibility in Learning team, under the User Experience division, provides our business lines with training, tools, guidelines, and advice to meet accessibility standards so that they can provide learners with a meaningful, inclusive, and accessible learning experience. Accessibility must be by design and by default. We are here to:

  • Lead the culture change towards accessible and inclusive design through training and technology support.
  • Establish and reinforce accessible and inclusive design best practices from the start.
  • Support the purchase of accessible learning solutions and accessible authoring tools.
  • Collaborate with other accessibility, design, research, and usability specialists within the School, and across the public service.
  • Establish guidelines, best practices, and processes for implementing and maintaining accessibility and inclusive products and services.
  • Provide coaching and professional development to School employees on accessibility.

To learn more about inclusion and accessibility, or to access help with your learning design or development, please contact the Digital Accessibility team.

digitalaccessibilityinlearning-accessibilitenumerique@csps-efpc.gc.ca

Page details

Date modified:
\ No newline at end of file diff --git a/en/cart-services-and-sign-language-interpreters/index.html b/en/cart-services-and-sign-language-interpreters/index.html index fb49aaaa9..58762659b 100644 --- a/en/cart-services-and-sign-language-interpreters/index.html +++ b/en/cart-services-and-sign-language-interpreters/index.html @@ -1,4 +1,4 @@ -CART Services and Sign Language Interpreters - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

CART Services and Sign Language Interpreters

The most common accommodations for meetings or events are computer-assisted real-time translation (CART) and sign language interpretation services (SLI).

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

Important to consider that people who are culturally Deaf, may prefer to have sign language interpreters because their first language is likely American Sign Language (ASL – English) or Langue des signes québécoise (LSQ), but do not assume this. Ask them what their preferred accommodation would be. Indeed, there are people who have become deaf later in life and have not learned to communicate by ASL or LSQ.

Communication Access Real-Time (CART)

Sign Language Interpreters

SLI are booked two different ways – through the Translation Bureau or external suppliers.

Translation Bureau

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

CART Services and Sign Language Interpreters

The most common accommodations for meetings or events are computer-assisted real-time translation (CART) and sign language interpretation services (SLI).

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

Important to consider that people who are culturally Deaf, may prefer to have sign language interpreters because their first language is likely American Sign Language (ASL) or <span =lang="fr">Langue des signes québécoise (LSQ), but do not assume this. Ask them what their preferred accommodation would be. Indeed, there are people who have become deaf later in life and have not learned to communicate by ASL or LSQ.

Communication Access Real-Time (CART)

Sign Language Interpreters

SLI are booked two different ways – through the Translation Bureau or external suppliers.

Translation Bureau

Page details

Date modified:
\ No newline at end of file diff --git a/en/cognitive-disabilities/index.html b/en/cognitive-disabilities/index.html index 8df1a3d59..e3a6399b4 100644 --- a/en/cognitive-disabilities/index.html +++ b/en/cognitive-disabilities/index.html @@ -1,4 +1,4 @@ -Cognitive Disabilities - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Cognitive Disabilities

Cognitive impairments take many forms, including short and long-term memory impairments, and perceptual differences. Language impairments, including dyslexia and temporary impairments associated with those trying to learn new languages, are also common cognitive problems.

Intellectual Disabilities

Definition:

Intellectual disability is characterized by significant limitations both in intellectual functioning (reasoning, learning, problem solving) and in adaptive behavior, which covers a range of everyday social and practical skills.

According to the American Association of Intellectual and Developmental Disabilities, an individual has intellectual disability if they meet three criteria:

  • Their IQ is below 70 to 75
  • There are significant limitations in two or more adaptive areas (skills that are needed to live, work, and play in the community, such as communication or selfcare)
  • The condition manifests itself before the age of 18
Characteristics:

People with an intellectual disability may:

  • Sit up, crawl, or walk later than other children
  • Learn to talk later or have trouble understanding and speaking
  • Find it hard to remember things
  • Have trouble understanding social rules and cues
  • Have trouble seeing the results of their actions
  • Have trouble solving problems and decision-making

Reading and Dyslexia

Definition:

Dyslexia is a learning disability that impairs a person’s ability to read. The disability could be the result of a congenital difference, an injury, delayed development, a neurological or physical disability. Professionals identify and diagnose specific reading disabilities, such as Dyslexia in children and teenagers. Often the diagnosis of a learning disability will include components of a reading impairment.

People with adult-onset dyslexia typically develop after a brain injury or in the context of dementia. Recent research has shown a number of genes that may predispose a person to developing dyslexia. Dyslexia can be inherited in some families.

Characteristics:

Although the disorder differs from person to person, reading disabilities may include:

  • An inability to perceive text or to process the meaning of words, phrases and ideas
  • Read at lower levels than expected despite having normal intelligence
  • Difficulty with phonological processing (the manipulation of sounds), spelling, and / or rapid visual-verbal responding

Math and Computation

Definition:
Math and computational disabilities impact a person’s ability to learn and communicate math. Dyscalculia involves an inability to understand arithmetic and how to calculate. This disability can be complicated by dysgraphia, which can include an inability to draw or copy figures and graphs, and by anxiety. Dyscalculia may be congenital or result from an injury, disease, or aging.
Characteristics:

According to Understood’s What is Dyscalculia and other sources, common signs of dyscalculia include difficulty with:

  • Grasping the meaning of quantities or concepts like biggest vs smallest
  • Word problems that require math skills
  • Understanding that the numeral 4 is the same as the word four, and that these both mean four items
  • Basic math concepts, such as addition, subtraction, multiplying, and dividing
  • Remembering math facts, such as multiplication tables
  • Math operations, such as such as carrying, borrowing, and regrouping
  • Time and money, such as estimating time, counting money and making change
  • Spatial reasoning, such as judging speed or distance
  • Sequences of numbers, such as phone numbers and addresses

Attention Deficit Hyperactivity Disorder

Definition:
Attention Deficit Hyperactivity Disorder (ADHD) is a neurodevelopmental disorder that affects both children and adults. Symptoms usually appear by age 7. While people do not outgrow ADHD, they do learn to adapt. ADHD is characterized by difficulties with attention, impulsivity and hyperactivity that can interfere with daily functioning and relationships.
Characteristics:

The main symptoms of ADHD are:

  • Inattention: difficulty focusing, forgetfulness, distractibility and disorganization
  • Impulsivity: acting without thinking, interrupting others and difficulty waiting for one’s turn
  • Hyperactivity: fidgeting, restlessness, excessive talking, and inability to sit still

Autism Spectrum Disorders

Definition:

According to the World Health Organization: Autism spectrum disorders (ASD) refers to a range of conditions marked by some degree of impairment in social behaviour, communication and language, and a narrow range of interests and activities that are both unique to the individual and carried out repetitively.

ASD begins in childhood and tends to continue into adolescence and adulthood. People with ASD often have co-occurring conditions, such as epilepsy, depression, anxiety and attention deficit hyperactivity disorder (ADHD). The level of intellectual functioning in individuals with ASDs is extremely variable, extending from profound impairment to superior levels.

Characteristics:

People with ASD may exhibit some of the following traits:

  • Difficulty with social interaction: making and maintaining relationships, understanding social cues, and understanding or talking about feelings
  • Communication difficulties: using and understanding language, making eye contact, giving unrelated answers to questions and repeating words or phrases over and over
  • Difficulty with change, such as getting upset by minor changes
  • Narrow interests, such as having obsessive interests
  • Repetitive behaviour, such as flap their hands or lining up objects
  • Unusual motor movements, such as flap their hands and rock their body
  • Sensory sensitivities: unusual reactions to the way things sound, smell, taste, look, or feel

Non-verbal Learning Disability

Definition:
According to the University of Michigan, Michigan Medicine resource, Your Child Development and Behavior Resources, Non-verbal Learning Disability (NLD): Nonverbal Learning Disability is very much like Asperger Syndrome (AS), in which people with the syndrome have normal intelligence and language development, but have trouble with social skills, sensory input, and making transitions. AS and NLD are generally thought to describe the same kind of disorder but to differ in severity, with AS describing more severe symptoms.
Characteristics:

Some of the signs of NLD include:

  • Great vocabulary, verbal expression and reading comprehension
  • Excellent memory recall for details
  • Attention to detail, but missing the big picture
  • Poor abstract reasoning and problem solving
  • Difficulty reading maps, interpreting graphs, and solving puzzles and time management
  • Difficulty with planning, organizing, and managing tasks
  • Physical awkwardness, poor coordination
  • Poor social skills
  • Trouble understanding social cues, body language, sarcasm and humour
  • Trouble adjusting to changes
  • Anxiety, depression, low self-esteem

Barriers for People with Cognitive Disabilities

From the W3C’s Web Accessibility Initiative and other sources:

Reading and Dyslexia Challenges and Solutions

Perceives words as floating and not in a line:

Perceives words differently than others, such as by confusing the letters p, b, d, and q:

Requires additional time to read and process content:

Has the burden of deciphering content from the way it is presented:

May have difficulty solving problems presented through security features such as CAPTCHA:

May have difficulty processing content through visual means:

Difficulties with spelling:

Math and Computation Challenges and Solutions

Inability to distinguish right from left in graphic images:

Inability to perform calculations:

Adaptive Technologies and Adaptive Strategies

Here are some commonly used products and strategies:

Here are links to tutorials:

For Communication:

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Cognitive Disabilities

Cognitive impairments take many forms, including short and long-term memory impairments, and perceptual differences. Language impairments, including dyslexia and temporary impairments associated with those trying to learn new languages, are also common cognitive problems.

Intellectual Disabilities

Definition:

Intellectual disability is characterized by significant limitations both in intellectual functioning (reasoning, learning, problem solving) and in adaptive behavior, which covers a range of everyday social and practical skills.

According to the American Association of Intellectual and Developmental Disabilities, an individual has intellectual disability if they meet three criteria:

  • Their IQ is below 70 to 75
  • There are significant limitations in two or more adaptive areas (skills that are needed to live, work, and play in the community, such as communication or selfcare)
  • The condition manifests itself before the age of 18
Characteristics:

People with an intellectual disability may:

  • Sit up, crawl, or walk later than other children
  • Learn to talk later or have trouble understanding and speaking
  • Find it hard to remember things
  • Have trouble understanding social rules and cues
  • Have trouble seeing the results of their actions
  • Have trouble solving problems and decision-making

Reading and Dyslexia

Definition:

Dyslexia is a learning disability that impairs a person’s ability to read. The disability could be the result of a congenital difference, an injury, delayed development, a neurological or physical disability. Professionals identify and diagnose specific reading disabilities, such as Dyslexia in children and teenagers. Often the diagnosis of a learning disability will include components of a reading impairment.

People with adult-onset dyslexia typically develop after a brain injury or in the context of dementia. Recent research has shown a number of genes that may predispose a person to developing dyslexia. Dyslexia can be inherited in some families.

Characteristics:

Although the disorder differs from person to person, reading disabilities may include:

  • An inability to perceive text or to process the meaning of words, phrases and ideas
  • Read at lower levels than expected despite having normal intelligence
  • Difficulty with phonological processing (the manipulation of sounds), spelling, and / or rapid visual-verbal responding

Math and Computation

Definition:
Math and computational disabilities impact a person’s ability to learn and communicate math. Dyscalculia involves an inability to understand arithmetic and how to calculate. This disability can be complicated by dysgraphia, which can include an inability to draw or copy figures and graphs, and by anxiety. Dyscalculia may be congenital or result from an injury, disease, or aging.
Characteristics:

According to Understood’s What is Dyscalculia and other sources, common signs of dyscalculia include difficulty with:

  • Grasping the meaning of quantities or concepts like biggest vs smallest
  • Word problems that require math skills
  • Understanding that the numeral 4 is the same as the word four, and that these both mean four items
  • Basic math concepts, such as addition, subtraction, multiplying, and dividing
  • Remembering math facts, such as multiplication tables
  • Math operations, such as such as carrying, borrowing, and regrouping
  • Time and money, such as estimating time, counting money and making change
  • Spatial reasoning, such as judging speed or distance
  • Sequences of numbers, such as phone numbers and addresses

Attention Deficit Hyperactivity Disorder

Definition:
Attention Deficit Hyperactivity Disorder (ADHD) is a neurodevelopmental disorder that affects both children and adults. Symptoms usually appear by age 7. While people do not outgrow ADHD, they do learn to adapt. ADHD is characterized by difficulties with attention, impulsivity and hyperactivity that can interfere with daily functioning and relationships.
Characteristics:

The main symptoms of ADHD are:

  • Inattention: difficulty focusing, forgetfulness, distractibility and disorganization
  • Impulsivity: acting without thinking, interrupting others and difficulty waiting for one’s turn
  • Hyperactivity: fidgeting, restlessness, excessive talking, and inability to sit still

Autism Spectrum Disorders

Definition:

According to the World Health Organization: Autism spectrum disorders (ASD) refers to a range of conditions marked by some degree of impairment in social behaviour, communication and language, and a narrow range of interests and activities that are both unique to the individual and carried out repetitively.

ASD begins in childhood and tends to continue into adolescence and adulthood. People with ASD often have co-occurring conditions, such as epilepsy, depression, anxiety and attention deficit hyperactivity disorder (ADHD). The level of intellectual functioning in individuals with ASDs is extremely variable, extending from profound impairment to superior levels.

Characteristics:

People with ASD may exhibit some of the following traits:

  • Difficulty with social interaction: making and maintaining relationships, understanding social cues, and understanding or talking about feelings
  • Communication difficulties: using and understanding language, making eye contact, giving unrelated answers to questions and repeating words or phrases over and over
  • Difficulty with change, such as getting upset by minor changes
  • Narrow interests, such as having obsessive interests
  • Repetitive behaviour, such as flap their hands or lining up objects
  • Unusual motor movements, such as flap their hands and rock their body
  • Sensory sensitivities: unusual reactions to the way things sound, smell, taste, look, or feel

Non-verbal Learning Disability

Definition:
According to the University of Michigan, Michigan Medicine resource, Your Child Development and Behavior Resources, Non-verbal Learning Disability (NLD): Nonverbal Learning Disability is very much like Asperger Syndrome (AS), in which people with the syndrome have normal intelligence and language development, but have trouble with social skills, sensory input, and making transitions. AS and NLD are generally thought to describe the same kind of disorder but to differ in severity, with AS describing more severe symptoms.
Characteristics:

Some of the signs of NLD include:

  • Great vocabulary, verbal expression and reading comprehension
  • Excellent memory recall for details
  • Attention to detail, but missing the big picture
  • Poor abstract reasoning and problem solving
  • Difficulty reading maps, interpreting graphs, and solving puzzles and time management
  • Difficulty with planning, organizing, and managing tasks
  • Physical awkwardness, poor coordination
  • Poor social skills
  • Trouble understanding social cues, body language, sarcasm and humour
  • Trouble adjusting to changes
  • Anxiety, depression, low self-esteem

Barriers for People with Cognitive Disabilities

From the W3C’s Web Accessibility Initiative and other sources:

Reading and Dyslexia Challenges and Solutions

Perceives words as floating and not in a line:

Perceives words differently than others, such as by confusing the letters p, b, d, and q:

Requires additional time to read and process content:

Has the burden of deciphering content from the way it is presented:

May have difficulty solving problems presented through security features such as CAPTCHA:

May have difficulty processing content through visual means:

Difficulties with spelling:

Math and Computation Challenges and Solutions

Inability to distinguish right from left in graphic images:

Inability to perform calculations:

Adaptive Technologies and Adaptive Strategies

Here are some commonly used products and strategies:

Here are links to tutorials:

For Communication:

Page details

Date modified:
\ No newline at end of file diff --git a/en/community-directory/index.html b/en/community-directory/index.html index fcaca6b37..fd72bf915 100644 --- a/en/community-directory/index.html +++ b/en/community-directory/index.html @@ -9,4 +9,4 @@ w.gtag('js', new Date()); w.gtag('config', 'G-SM9MSHWDVN'); } - })(window);

Language selection

Government of Canada / Government of Canada

Search

Community Directory

Learn more about the organizations, projects, and people working on accessibility within the Government of Canada.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

Accessibility Standards Canada

Accessibility Standards Canada’s role is to:

  • create accessibility standards for federally-regulated organizations,
  • advance accessibility research, and
  • share best practices related to accessibility.

As an accredited standards development organization, their standards are recognized as national standards of Canada. Their work also opens doors so that Canada can be a global leader on matters related to accessibility.

Canada School of Public Service (CSPS)

The Canada School of Public Service leads the government's enterprise-wide approach to learning by providing a common, standardized curriculum that supports public servants through key career transitions, ensuring that they are equipped to serve Canadians with excellence. Multiple teams at the School support accessibility with the goal of creating a barrier free learning environment for its learners.

internal linkCommunity of Practice for Accessible Communications

The Community of Practice for Accessible Communications encompasses colleagues from all fields and from all areas of communications across the Government of Canada. Its mandate is to connect the GC community to exchange ideas and to support policies, guidelines, and best practices related to internal and external accessible communications.

Their objectives include:

  • Help clarify Canada.ca guidance and develop best practices around using accessible internal and external communications.
  • Enable employees to use accessible communications across the GC.
  • Identify gaps in GC practices, policies and standards for accessible communications and make strategic recommendations to central agencies in this regard.

Employment and Social Development Canada (ESDC)

Employment and Social Development Canada (ESDC) works to improve the standard of living and quality of life for all Canadians. We do this by promoting a labour force that is highly skilled. We also promote an efficient and inclusive labour market. ESDC has multiple teams working in digital accessibility with the goal of creating a barrier free environment for Canadians and employees!

Statistics Canada (StatCan)

Statistics Canada, in collaboration with partners from Employment and Social Development Canada, will continue to develop and release products to better understand the accessibility experiences of Canadians. The Accessibility Data Hub provides a centralized location of topics related to accessibility and disability through data tables, articles, infographics and interactive data visualization tools.

Other participating departments

  • Agriculture and Agri-Food Canada (AAFC)
  • Canada Revenue Agency (CRA)
  • Department of Finance Canada (FIN)
  • Health Canada (HC)
  • Public Safety Canada (PS)
  • Public Service Commission of Canada (PSC)
  • Public Services and Procurement Canada (PSPC)
  • Shared Services Canada (SSC)
  • Treasury Board of Canada Secretariat (TBS)
  • Veterans Affairs Canada (VAC)

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Community Directory

Learn more about the organizations, projects, and people working on accessibility within the Government of Canada.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

Accessibility Standards Canada

Accessibility Standards Canada’s role is to:

  • create accessibility standards for federally-regulated organizations,
  • advance accessibility research, and
  • share best practices related to accessibility.

As an accredited standards development organization, their standards are recognized as national standards of Canada. Their work also opens doors so that Canada can be a global leader on matters related to accessibility.

Canada School of Public Service (CSPS)

The Canada School of Public Service leads the government's enterprise-wide approach to learning by providing a common, standardized curriculum that supports public servants through key career transitions, ensuring that they are equipped to serve Canadians with excellence. Multiple teams at the School support accessibility with the goal of creating a barrier free learning environment for its learners.

internal linkCommunity of Practice for Accessible Communications

The Community of Practice for Accessible Communications encompasses colleagues from all fields and from all areas of communications across the Government of Canada. Its mandate is to connect the GC community to exchange ideas and to support policies, guidelines, and best practices related to internal and external accessible communications.

Their objectives include:

  • Help clarify Canada.ca guidance and develop best practices around using accessible internal and external communications.
  • Enable employees to use accessible communications across the GC.
  • Identify gaps in GC practices, policies and standards for accessible communications and make strategic recommendations to central agencies in this regard.

Employment and Social Development Canada (ESDC)

Employment and Social Development Canada (ESDC) works to improve the standard of living and quality of life for all Canadians. We do this by promoting a labour force that is highly skilled. We also promote an efficient and inclusive labour market. ESDC has multiple teams working in digital accessibility with the goal of creating a barrier free environment for Canadians and employees!

Statistics Canada (StatCan)

Statistics Canada, in collaboration with partners from Employment and Social Development Canada, will continue to develop and release products to better understand the accessibility experiences of Canadians. The Accessibility Data Hub provides a centralized location of topics related to accessibility and disability through data tables, articles, infographics and interactive data visualization tools.

Other participating departments

  • Agriculture and Agri-Food Canada (AAFC)
  • Canada Revenue Agency (CRA)
  • Department of Finance Canada (FIN)
  • Health Canada (HC)
  • Public Safety Canada (PS)
  • Public Service Commission of Canada (PSC)
  • Public Services and Procurement Canada (PSPC)
  • Shared Services Canada (SSC)
  • Treasury Board of Canada Secretariat (TBS)
  • Veterans Affairs Canada (VAC)

Page details

Date modified:
\ No newline at end of file diff --git a/en/design-a-course/index.html b/en/design-a-course/index.html index ff860591c..49cd4d2db 100644 --- a/en/design-a-course/index.html +++ b/en/design-a-course/index.html @@ -9,4 +9,4 @@ w.gtag('js', new Date()); w.gtag('config', 'G-SM9MSHWDVN'); } - })(window);

Language selection

Government of Canada / Government of Canada

Search

Design a course

Learn about the roles and processes involved in designing and developing an accessible course.

Do’s and Don’ts for developing online courses

Do’s and don’ts for writing, designing and developing online courses.

Personas with Disabilities for inclusive user experience (UX) design

The case to include disabilities into user personas, the types of technologies they use, and sample personas with disabilities.

Tips for creating online courses

Tips and tricks for writing, designing and developing online courses.

Universal Design for Learning (UDL)

Universal Design for Learning (UDL) is a framework that avoids a ‘one-size fits all approach’ to learning materials. It encourages using multiple ways of engagement, representation and action and expression can meet the needs of a larger number of learners. Learn about the three main UDL principles, advantages, benefits and tips.

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Design a course

Learn about the roles and processes involved in designing and developing an accessible course.

Do’s and Don’ts for developing online courses

Do’s and don’ts for writing, designing and developing online courses.

Personas with Disabilities for inclusive user experience (UX) design

The case to include disabilities into user personas, the types of technologies they use, and sample personas with disabilities.

Tips for creating online courses

Tips and tricks for writing, designing and developing online courses.

Universal Design for Learning (UDL)

Universal Design for Learning (UDL) is a framework that avoids a ‘one-size fits all approach’ to learning materials. It encourages using multiple ways of engagement, representation and action and expression can meet the needs of a larger number of learners. Learn about the three main UDL principles, advantages, benefits and tips.

Page details

Date modified:
\ No newline at end of file diff --git a/en/digital-accessibility-toolkit-project/index.html b/en/digital-accessibility-toolkit-project/index.html index 8c3698285..379b3b21c 100644 --- a/en/digital-accessibility-toolkit-project/index.html +++ b/en/digital-accessibility-toolkit-project/index.html @@ -1,4 +1,4 @@ -Digital Accessibility Toolkit project - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Digital Accessibility Toolkit project

About the project, who we are and what is our goal.

Purpose

Collaborate on the creation of a platform to centralize Government of Canada (GC) information on accessibility.

The Access Working Group (AWG) would like to enable interdepartmental centralization and sharing of accessibility information produced by GC departments in a central repository sharing space and in the open.

Sharing

The Digital Accessibility Toolkit (DAT) will focus on:

Task force’s key role

The Digital Accessibility Toolkit will leverage accessibility expertise across government, showcase best practices, promote inclusive design and accessibility by default.

The Digital Accessibility Toolkit (DAT) will also:

  1. Support the Public Service Accessibility Strategy’s Goal 3: Make information and communications technology usable by all;
  2. Provide recommendations for the creation of the accessibility resources and work from Government of Canada (GC) central repository;
  3. Supporting the implementation through various phases of work; and
  4. Discussion and initiate supporting activities to identify which information / materials would be appropriate to share.

Roles and responsibilities

The key roles will be defined based on the World Wide Web Consortium's (W3C) ARRM Project - Accessibility Roles and Responsibilities Mapping project.

Mandate and decision-making authority

The Digital Accessibility Toolkit (DAT) is a recommendation-making forum that has a mandate to:

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Digital Accessibility Toolkit project

About the project, who we are and what is our goal.

Purpose

Collaborate on the creation of a platform to centralize Government of Canada (GC) information on accessibility.

The Access Working Group (AWG) would like to enable interdepartmental centralization and sharing of accessibility information produced by GC departments in a central repository sharing space and in the open.

Sharing

The Digital Accessibility Toolkit (DAT) will focus on:

Task force’s key role

The Digital Accessibility Toolkit will leverage accessibility expertise across government, showcase best practices, promote inclusive design and accessibility by default.

The Digital Accessibility Toolkit (DAT) will also:

  1. Support the Public Service Accessibility Strategy’s Goal 3: Make information and communications technology usable by all;
  2. Provide recommendations for the creation of the accessibility resources and work from Government of Canada (GC) central repository;
  3. Supporting the implementation through various phases of work; and
  4. Discussion and initiate supporting activities to identify which information / materials would be appropriate to share.

Roles and responsibilities

The key roles will be defined based on the World Wide Web Consortium's (W3C) ARRM Project - Accessibility Roles and Responsibilities Mapping project.

Mandate and decision-making authority

The Digital Accessibility Toolkit (DAT) is a recommendation-making forum that has a mandate to:

Page details

Date modified:
\ No newline at end of file diff --git a/en/employment-and-social-development-canada-esdc/index.html b/en/employment-and-social-development-canada-esdc/index.html index 263d56bbc..58ee75deb 100644 --- a/en/employment-and-social-development-canada-esdc/index.html +++ b/en/employment-and-social-development-canada-esdc/index.html @@ -1,4 +1,4 @@ -Employment and Social Development Canada (ESDC) - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Employment and Social Development Canada (ESDC)

Employment and Social Development Canada (ESDC) works to improve the standard of living and quality of life for all Canadians. We do this by promoting a labour force that is highly skilled. We also promote an efficient and inclusive labour market. ESDC has multiple teams working in digital accessibility with the goal of creating a barrier free environment for Canadians and employees!

Centre of Expertise for Accessible Client Service

The Centre of Expertise for Accessible Client Service helps to foster an accessibility-focused culture by offering expert advice and support to:

  • Adopt inclusive design principles into new or existing program design and service improvement initiatives;
  • Understand the way people live with a disability and the service barriers that create a challenge for them;
  • Identify the accessibility solutions that will make it easier for clients to access our programs and services;
  • Lead on the program and service design and delivery to realize Goal 4 of the Public Service Accessibility Strategy (PSAS).

ESDC Accessibility Office

The ESDC Accessibility Office is responsible for development and implementation of the Department’s accessibility plan, including ensuring the requirements under the Accessible Canada Act related to publishing the plan, receiving feedback and reporting on progress are met. The ESDC Accessibility Office collaborates with and convenes partners both within and outside ESDC, working horizontally together to achieve the goal of identifying, eliminating and preventing barriers to accessibility.

IT Accessibility Office

The IT Accessibility Office (ITAO) remains to be a provider of adaptive technology and an advocate for inclusiveness of people with disabilities in the workplace. We are demonstrated leaders, committed to our accessibility mandate, continuing to provide support to employees with disabilities. In accordance with the Accessible Canada Act and in collaboration with our partners in central agencies, we recommend internationally recognized standards, guidelines and best practices. Our services span over topics such as procurement, training, awareness, product assessments, as well as expert advice on Accessible Information and Communication Technology (ICT).

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Employment and Social Development Canada (ESDC)

Employment and Social Development Canada (ESDC) works to improve the standard of living and quality of life for all Canadians. We do this by promoting a labour force that is highly skilled. We also promote an efficient and inclusive labour market. ESDC has multiple teams working in digital accessibility with the goal of creating a barrier free environment for Canadians and employees!

Centre of Expertise for Accessible Client Service

The Centre of Expertise for Accessible Client Service helps to foster an accessibility-focused culture by offering expert advice and support to:

  • Adopt inclusive design principles into new or existing program design and service improvement initiatives;
  • Understand the way people live with a disability and the service barriers that create a challenge for them;
  • Identify the accessibility solutions that will make it easier for clients to access our programs and services;
  • Lead on the program and service design and delivery to realize Goal 4 of the Public Service Accessibility Strategy (PSAS).

ESDC Accessibility Office

The ESDC Accessibility Office is responsible for development and implementation of the Department’s accessibility plan, including ensuring the requirements under the Accessible Canada Act related to publishing the plan, receiving feedback and reporting on progress are met. The ESDC Accessibility Office collaborates with and convenes partners both within and outside ESDC, working horizontally together to achieve the goal of identifying, eliminating and preventing barriers to accessibility.

IT Accessibility Office

The IT Accessibility Office (ITAO) remains to be a provider of adaptive technology and an advocate for inclusiveness of people with disabilities in the workplace. We are demonstrated leaders, committed to our accessibility mandate, continuing to provide support to employees with disabilities. In accordance with the Accessible Canada Act and in collaboration with our partners in central agencies, we recommend internationally recognized standards, guidelines and best practices. Our services span over topics such as procurement, training, awareness, product assessments, as well as expert advice on Accessible Information and Communication Technology (ICT).

Page details

Date modified:
\ No newline at end of file diff --git a/en/find-out-how-to-make-accessible-digital-forms/index.html b/en/find-out-how-to-make-accessible-digital-forms/index.html index d654fb375..e40f185aa 100644 --- a/en/find-out-how-to-make-accessible-digital-forms/index.html +++ b/en/find-out-how-to-make-accessible-digital-forms/index.html @@ -1,4 +1,4 @@ -Find out how to make accessible digital forms - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Find out how to make accessible digital forms

With this guide, find out what the best format is and other helpful tips for making accessible digital forms.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

The most accessible format for forms: HTML

HTML is the best and most flexible format, even compared to Word and PDF. When coded correctly, HTML forms provide the best accessibility features including:

For websites using the Web Experience Toolkit, follow the Web Experience Toolkit Design Guide to create an accessible HTML form.

Easy and accessible: simple Word document

Microsoft Word documents (without form fields) are the next best option to create accessible forms. A Word document, like HTML, can be adapted to meet specific user needs (e.g. font size can be increased), and can be a good choice despite some limitations. The document should be laid out in a simple, single column question and answer style, with a blank line provided under each question for the response to be entered. However, in such a simple Word document, you will not be able to provide form elements such as checkboxes or automated validation to ensure that required fields have been completed. Protecting content which you don’t want edited (such as the form questions) can make it difficult for users of adaptive technology to access that content at all. Working within these limitations, a simple Word document may be all you need to gather information. It is both the easiest format to create, and the easiest to adapt to specific user needs.

Using built-in form elements such as checkboxes in Microsoft Word will result in an inaccessible form. For more information on why this is, read the accessibility limitations of Microsoft Word forms. Microsoft has even hidden these features in recent versions of Word under “Legacy tools”. Form fields in Word are difficult to navigate using only the keyboard, and don’t have explicit label associations. This poses difficulties for users of adaptive technologies. For example, a screen reader user will need to navigate away from the form field to find a nearby label – an issue compounded by the difficulties in keyboard navigation and accessing protected content.

Difficult and semi-accessible: PDF

Portable Document Format (PDF) is the most common format for forms in the GC. It is also one of the hardest formats to make accessible. In order to preserve the formatting when printing the form, much of the presentation is “baked in” into the file. This significantly limits adaptability when a user is filling a PDF form electronically. For example, most PDF forms do not successfully reflow in response to a smaller viewport, decreasing usability for users with low vision or on mobile devices. User preferences for colors and fonts are rarely reflected. It is also difficult to adapt a pdf form to alternate formats such as large print or braille.

Fillable pdf forms are widely used because they offer many of the features of HTML forms: form elements like checkboxes, programmatic labels, and even JavaScript validation. If you can’t use an HTML form but need these features, take steps to ensure the PDF is as accessible as the format allows.

Creating a PDF form

While specific tools for creating PDF forms exist (e.g. Adobe LiveCycle), you can use Microsoft Word as a starting point to create a PDF form (See Create accessible PDFs). Do not create the form fields themselves in Word. Rather, just leave blank space to create them in the PDF editor (e.g. Acrobat Pro, Foxit PDF Editor).

First, the Word document must itself be accessible. In addition to following general document accessibility guidelines, avoid common form design errors:

  1. Don’t use tables for visual layout.
    1. Instead, a linear order is the simplest and most accessible option, with each form field on a new line.
    2. If you want a “multi-column” visual style, use tab stops or columns. You can use custom Styles to create box outlines. Do not use text boxes.
  2. Create headings to identify the various sections of the form, to make it easier to navigate.
    1. Note that headings will only work outside of a table.

Once the form template has been created in Word to be as accessible as possible, export it to PDF. Ensure that the options are selected to create Bookmarks from headings and to create tags in the PDF.

You will then have to create the form fields in the PDF software. Please see this guide from Adobe on creating accessible forms in Acrobat Pro DC. You must explicitly indicate form field labels as “tooltips”. See also Foxit PDF Editor video tutorials and user manuals.

E-signatures

Carefully consider the requirements for a signature. The Treasury Board of Canada Secretariat provides guidance on using electronic signatures. Often, asking the user to type their name on a line or insert a signature image is sufficient for a Word or PDF document. The identity verification is accomplished by sending the document as an email attachment. For an HTML form, asking the user to type their name and select a checkbox confirming their identity may also be sufficient.

When greater security is required, a digital signature can be used in both PDF and Microsoft Word documents. In order to digitally sign a document, you will need to have a myKey. See Transport Canada’s Digital Signatures Technical User Guide Internal link Word, 1.1 MB for more information.

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Find out how to make accessible digital forms

With this guide, find out what the best format is and other helpful tips for making accessible digital forms.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

The most accessible format for forms: HTML

HTML is the best and most flexible format, even compared to Word and PDF. When coded correctly, HTML forms provide the best accessibility features including:

For websites using the Web Experience Toolkit, follow the Web Experience Toolkit Design Guide to create an accessible HTML form.

Easy and accessible: simple Word document

Microsoft Word documents (without form fields) are the next best option to create accessible forms. A Word document, like HTML, can be adapted to meet specific user needs (e.g. font size can be increased), and can be a good choice despite some limitations. The document should be laid out in a simple, single column question and answer style, with a blank line provided under each question for the response to be entered. However, in such a simple Word document, you will not be able to provide form elements such as checkboxes or automated validation to ensure that required fields have been completed. Protecting content which you don’t want edited (such as the form questions) can make it difficult for users of adaptive technology to access that content at all. Working within these limitations, a simple Word document may be all you need to gather information. It is both the easiest format to create, and the easiest to adapt to specific user needs.

Using built-in form elements such as checkboxes in Microsoft Word will result in an inaccessible form. For more information on why this is, read the accessibility limitations of Microsoft Word forms. Microsoft has even hidden these features in recent versions of Word under “Legacy tools”. Form fields in Word are difficult to navigate using only the keyboard, and don’t have explicit label associations. This poses difficulties for users of adaptive technologies. For example, a screen reader user will need to navigate away from the form field to find a nearby label – an issue compounded by the difficulties in keyboard navigation and accessing protected content.

Difficult and semi-accessible: PDF

Portable Document Format (PDF) is the most common format for forms in the GC. It is also one of the hardest formats to make accessible. In order to preserve the formatting when printing the form, much of the presentation is “baked in” into the file. This significantly limits adaptability when a user is filling a PDF form electronically. For example, most PDF forms do not successfully reflow in response to a smaller viewport, decreasing usability for users with low vision or on mobile devices. User preferences for colors and fonts are rarely reflected. It is also difficult to adapt a pdf form to alternate formats such as large print or braille.

Fillable pdf forms are widely used because they offer many of the features of HTML forms: form elements like checkboxes, programmatic labels, and even JavaScript validation. If you can’t use an HTML form but need these features, take steps to ensure the PDF is as accessible as the format allows.

Creating a PDF form

While specific tools for creating PDF forms exist (e.g. Adobe LiveCycle), you can use Microsoft Word as a starting point to create a PDF form (See Create accessible PDFs). Do not create the form fields themselves in Word. Rather, just leave blank space to create them in the PDF editor (e.g. Acrobat Pro, Foxit PDF Editor).

First, the Word document must itself be accessible. In addition to following general document accessibility guidelines, avoid common form design errors:

  1. Don’t use tables for visual layout.
    1. Instead, a linear order is the simplest and most accessible option, with each form field on a new line.
    2. If you want a “multi-column” visual style, use tab stops or columns. You can use custom Styles to create box outlines. Do not use text boxes.
  2. Create headings to identify the various sections of the form, to make it easier to navigate.
    1. Note that headings will only work outside of a table.

Once the form template has been created in Word to be as accessible as possible, export it to PDF. Ensure that the options are selected to create Bookmarks from headings and to create tags in the PDF.

You will then have to create the form fields in the PDF software. Please see this guide from Adobe on creating accessible forms in Acrobat Pro DC. You must explicitly indicate form field labels as “tooltips”. See also Foxit PDF Editor video tutorials and user manuals.

E-signatures

Carefully consider the requirements for a signature. The Treasury Board of Canada Secretariat provides guidance on using electronic signatures. Often, asking the user to type their name on a line or insert a signature image is sufficient for a Word or PDF document. The identity verification is accomplished by sending the document as an email attachment. For an HTML form, asking the user to type their name and select a checkbox confirming their identity may also be sufficient.

When greater security is required, a digital signature can be used in both PDF and Microsoft Word documents. In order to digitally sign a document, you will need to have a myKey. See Transport Canada’s Digital Signatures Technical User Guide Internal link Word, 1.1 MB for more information.

Page details

Date modified:
\ No newline at end of file diff --git a/en/index.html b/en/index.html index 97dfad42b..4d624686f 100644 --- a/en/index.html +++ b/en/index.html @@ -9,4 +9,4 @@ w.gtag('js', new Date()); w.gtag('config', 'G-SM9MSHWDVN'); } - })(window);

Language selection

Government of Canada / Government of Canada

Search

Digital Accessibility Toolkit

Welcome to the Digital Accessibility Toolkit. We offer a variety of learning materials and resources to help you learn and implement accessibility in your digital projects.

Exploring your toolkit

Accessibility Fundamentals

Discover the principles behind accessible digital products and services. These principles remove barriers for people living with disabilities and ensures ease of use for all.

Digital accessibility in the Government of Canada

Learn more about the Information and Communication Technology (ICT) accessibility standards, including the EN 301 549, which includes WCAG 2.1 level A and AA, when purchasing goods or services or designing a project, roles, and teams related to the Government of Canada.

How to’s

Tips and core steps to help make all your digital products and content, such as documents, meetings, accessible.

Learning and Development

Discover a curated collection of learning products to enhance your understanding of accessibility. Whether you're a developer, designer, or enthusiast, explore our links to courses, tutorials, and tools. Join us in creating a more inclusive digital world.

Resources and Tools

Explore the various guides and learning materials created by federal public servants working to advance digital accessibility.

Latest updates

Explore our latest content

About the Digital Accessibility Toolkit

Learn more about this project and what the Digital Accessibility Toolkit is.

Contact us

Interested in learning more? Reach out and get connected to our team.

Digital Accessibility Toolkit project

About the project, who we are and what is our goal.

Research on our target audience

The main goal of creating these personas was to better understand our target audience. By developing a greater understanding of our users. By developing a greater understanding of our users, we would be able to build a responsive site architecture for all existing and future content hosted on the Digital Accessibility Toolkit’s website.

Terms of Reference

Terms of Reference define the purpose and scope of the Digital Accessibility Toolkit project. It includes information regarding the structures of a project, key roles, membership, meeting, and more.

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Digital Accessibility Toolkit

Welcome to the Digital Accessibility Toolkit. We offer a variety of learning materials and resources to help you learn and implement accessibility in your digital projects.

Exploring your toolkit

Accessibility Fundamentals

Discover the principles behind accessible digital products and services. These principles remove barriers for people living with disabilities and ensures ease of use for all.

Digital accessibility in the Government of Canada

Learn more about the Information and Communication Technology (ICT) accessibility standards, including the EN 301 549, which includes WCAG 2.1 level A and AA, when purchasing goods or services or designing a project, roles, and teams related to the Government of Canada.

How to’s

Tips and core steps to help make all your digital products and content, such as documents, meetings, accessible.

Learning and Development

Discover a curated collection of learning products to enhance your understanding of accessibility. Whether you're a developer, designer, or enthusiast, explore our links to courses, tutorials, and tools. Join us in creating a more inclusive digital world.

Resources and Tools

Explore the various guides and learning materials created by federal public servants working to advance digital accessibility.

Latest updates

Explore our latest content

About the Digital Accessibility Toolkit

Learn more about this project and what the Digital Accessibility Toolkit is.

Contact us

Interested in learning more? Reach out and get connected to our team.

Digital Accessibility Toolkit project

About the project, who we are and what is our goal.

Research on our target audience

The main goal of creating these personas was to better understand our target audience. By developing a greater understanding of our users. By developing a greater understanding of our users, we would be able to build a responsive site architecture for all existing and future content hosted on the Digital Accessibility Toolkit’s website.

Terms of Reference

Terms of Reference define the purpose and scope of the Digital Accessibility Toolkit project. It includes information regarding the structures of a project, key roles, membership, meeting, and more.

Page details

Date modified:
\ No newline at end of file diff --git a/en/information-and-communication-technology-ict-accessibility-requirements/index.html b/en/information-and-communication-technology-ict-accessibility-requirements/index.html index 58404d0a1..ba1a6fe5d 100644 --- a/en/information-and-communication-technology-ict-accessibility-requirements/index.html +++ b/en/information-and-communication-technology-ict-accessibility-requirements/index.html @@ -1,4 +1,4 @@ -Information and Communication Technology (ICT) Accessibility Requirements - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Information and Communication Technology (ICT) Accessibility Requirements

This page is to share some of the work that Shared Services Canada (SSC) has done for the piloting of the EN 301 549 (2021) harmonized Information and Communications Technology (ICT) accessibility standards. This is not a full copy / paste / translation of either the EN 301 549 (2021) or Web Content Accessibility Guidelines (WCAG) 2.1.

Information and Communication Technology (ICT) Accessibility Requirements ( Word, 88 KB)

What is ICT?

Information and Communications Technology (ICT) includes hardware, software, voice communication, video capabilities and digital content (including web and non-web-based information).

What is ICT accessibility and why is it important?

"ICT accessibility ensures that people with and without disabilities can access the same information, perform the same tasks, and receive the same services using information technology. It is the digital equivalent to accessibility in the physical environment —the curb cuts, ramps, railings, etc., of the digital age. While ICT accessibility can provide usability benefits to everyone who uses ICT, it is a vital necessity to many people with disabilities." - NASCIO - Accessibility in IT Procurement

About this document and Copyright Notice

This document reproduces relevant ICT accessibility requirements from the EN 301 549 v3.2.1 (2021-03) Harmonised European Standard – Accessibility requirements for ICT products and services (© used under license from European Telecommunications Standards Institute 2021. © Comité Européen de Normalisation 2021. © Comité Européen de Normalisation Électrotechnique 2021. All rights reserved.), which includes the Web Content Accessibility Guidelines (WCAG) 2.1 level AA. Note, where the EN 301 549 references VOID criteria, for the purposes of this document, we have excluded the technical explanation as to why the WCAG criteria no longer apply. Refer to the EN 301 549 (hyperlink below) for this information if necessary.

Intellectual Property Rights (IPRs) essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https://ipr.etsi.org/). Please visit ETSI IPR database to search for any IPRs.

At first glance, some requirements may appear to be unrelated to this product or service. They have been included for consideration since the full feature set of a Vendor’s product or service may not be known. For example, a video may be embedded into product documentation, so accessibility requirements for video and audio may become relevant.

Appendices include definitions, references, and practical guidance on creating accessible documentation.

Internal to this document references are included but not always linked (footnotes or otherwise).

Sources used to compile this document

On this page:

You can find here partial information and present it in two languages for informational purposes. Specific procurements will have the appropriate ICT requirements within the tender package.

Part A - Functional performance statements

These are explanatory (non-testable) statements that introduce the core aspects that the offered product or service must provide to be considered accessible.

4.2.1. Usage without vision: Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that does not require vision. This is essential for users without vision and benefits many more users in different situations.

4.2.2. Usage with limited vision: Where ICT provides visual modes of operation, the ICT provides features that enable users to make better use of their limited vision. This is essential for users with limited vision and benefits many more users in different situations.

4.2.3. Usage without perception of colour: Where ICT provides visual modes of operation, the ICT provides a visual mode of operation that does not require user perception of colour. This is essential for users with limited colour perception and benefits many more users in different situations.

4.2.4. Usage without hearing: Where ICT provides auditory modes of operation, the ICT provides at least one mode of operation that does not require hearing. This is essential for users without hearing and benefits many more users in different situations.

4.2.5. Usage with limited hearing: Where ICT provides auditory modes of operation, the ICT provides enhanced audio features. This is essential for users with limited hearing and benefits many more users in different situations.

4.2.6. Usage with no or limited vocal capability: Where ICT requires vocal input from users, the ICT provides at least one mode of operation that does not require them to generate vocal output. This is essential users with no or limited vocal capability and benefits many more users in different situations.

4.2.7. Usage with limited manipulation or strength: Where ICT requires manual actions, the ICT provides features that enable users to make use of the ICT through alternative actions not requiring manipulation, simultaneous action or hand strength. This is essential for users with limited manipulation or strength and benefits many more users in different situations.

4.2.8. Usage with limited reach: : Where ICT products are free-standing or installed, all the elements required for operation will need to be within reach of all users. This is essential for users with limited reach and benefits many more users in different situations.

4.2.9. Minimize photosensitive seizure triggers: Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that minimizes the potential for triggering photosensitive seizures. This is essential for users with photosensitive seizure triggers.

4.2.10. Usage with limited cognition, language or learning: The ICT provides features and/or presentation that makes it simpler and easier to understand, operate and use. This is essential for users with limited cognition, language or learning, and benefits many more users in different situations.

4.2.11. privacy: Where ICT provides features for accessibility, the ICT maintains the privacy of users of these features at the same level as other users.

Part B - Functional accessibility requirements

Explanation of the table columns

Scope

The following Functional Accessibility Requirements are applicable to the Functional Performance Statements in Part A. If a solution meets all of these it is considered to have met the Functional Performance Statements and is therefore deemed to conform with EN 301 549 v3.2.1.

Clauses deemed relevant to this ICT

Clauses deemed relevant to this ICT

  • 5
  • 5.1
  • 5.1.1
  • 5.1.2
  • 5.1.2.1
  • 5.1.2.2
  • 5.1.3
  • 5.1.3.1
  • 5.1.3.2
  • 5.1.3.3
  • 5.1.3.4
  • 5.1.3.5
  • 5.1.3.6
  • 5.1.3.7
  • 5.1.3.8
  • 5.1.3.9
  • 5.1.3.10
  • 5.1.3.11
  • 5.1.3.12
  • 5.1.3.13
  • 5.1.3.14
  • 5.1.3.15
  • 5.1.3.16
  • 5.1.4
  • 5.1.5
  • 5.1.6
  • 5.1.6.1
  • 5.1.6.2
  • 5.1.7
  • 5.2
  • 5.3
  • 5.4
  • 5.5
  • 5.5.1
  • 5.5.2
  • 5.6
  • 5.6.1
  • 5.6.2
  • 5.7
  • 5.8
  • 5.9
  • 6
  • 6.1
  • 6.2
  • 6.2.1
  • 6.2.1.1
  • 6.2.1.2
  • 6.2.2
  • 6.2.2.1
  • 6.2.2.2
  • 6.2.2.3
  • 6.2.2.4
  • 6.2.3
  • 6.2.4
  • 6.5.5
  • 6.5.6
  • 6.6
  • 7
  • 7.1
  • 7.1.1
  • 7.1.2
  • 7.1.3
  • 7.1.4
  • 7.1.5
  • 7.2
  • 7.2.1
  • 7.2.2
  • 7.2.3
  • 7.3
  • 8
  • 8.1
  • 8.1.1
  • 8.1.2
  • 8.1.3
  • 8.2
  • 8.2.1
  • 8.2.1.1
  • 8.2.1.2
  • 8.2.2
  • 8.2.2.1
  • 8.2.2.2
  • 8.3
  • 8.3.0
  • 8.3.1
  • 8.3.2
  • 8.3.2.1
  • 8.3.2.2
  • 8.3.2.3
  • 8.3.2.3.1
  • 8.3.2.3.2
  • 8.3.2.3.3
  • 8.3.2.4
  • 8.3.2.5
  • 8.3.2.6
  • 8.3.3
  • 8.3.3.1
  • 8.3.3.2
  • 8.3.3.3
  • 8.3.3.3.1
  • 8.3.3.3.2
  • 8.3.4
  • 8.3.4.1
  • 8.3.4.2
  • 8.3.4.3
  • 8.3.4.3.1
  • 8.3.4.3.2
  • 8.3.4.3.3
  • 8.3.5
  • 8.3.6
  • 8.4
  • 8.4.1
  • 8.4.2
  • 8.3.4.3
  • 8.3.4.3.1
  • 8.3.4.3.2
  • 8.3.4.3.3
  • 8.3.5
  • 8.3.6
  • 8.4
  • 8.4.1
  • 8.4.2
  • 8.4.2.1
  • 8.4.2.2
  • 8.4.3
  • 8.5
  • 9
  • 9.0
  • 9.1
  • 9.1.1
  • 9.1.1.1
  • 9.1.2
  • 9.1.2.1
  • 9.1.2.2
  • 9.1.2.3
  • 9.1.2.4
  • 9.1.2.5
  • 9.1.3
  • 9.1.3.1
  • 9.1.3.2
  • 9.1.3.3
  • 9.1.3.4
  • 9.1.3.5
  • 9.1.4
  • 9.1.4.1
  • 9.1.4.2
  • 9.1.4.3
  • 9.1.4.4
  • 9.1.4.5
  • 9.1.4.10
  • 9.1.4.11
  • 9.1.4.12
  • 9.1.4.13
  • 9.2
  • 9.2.1
  • 9.2.1.1
  • 9.2.1.2
  • 9.2.1.4
  • 9.2.2
  • 9.2.2.1
  • 9.2.2.2
  • 9.2.3
  • 9.2.3.1
  • 9.2.4
  • 9.2.4.1
  • 9.2.4.2
  • 9.2.4.3
  • 9.2.4.4
  • 9.2.4.5
  • 9.2.4.6
  • 9.2.4.7
  • 9.2.5
  • 9.2.5.1
  • 9.2.5.2
  • 9.2.5.3
  • 9.2.5.4
  • 9.3
  • 9.3.1
  • 9.3.1.1
  • 9.3.1.2
  • 9.3.2
  • 9.3.2.1
  • 9.3.2.2
  • 9.3.2.3
  • 9.3.2.4
  • 9.3.3
  • 9.3.3.1
  • 9.3.3.2
  • 9.3.3.3
  • 9.3.3.4
  • 9.4
  • 9.4.1
  • 9.4.1.1
  • 9.4.1.2
  • 9.4.1.3
  • 9.5
  • 9.6
  • 10
  • 10.0
  • 10.1
  • 10.1.1
  • 10.1.1.1
  • 10.1.2
  • 10.1.2.1
  • 10.1.2.2
  • 10.1.2.3
  • 10.1.2.4
  • 10.1.2.5
  • 10.1.3
  • 10.1.3.1
  • 10.1.3.2
  • 10.1.3.3
  • 10.1.3.4
  • 10.1.3.5
  • 10.1.4
  • 10.1.4.1
  • 10.1.4.2
  • 10.1.4.3
  • 10.1.4.4
  • 10.1.4.5
  • 10.1.4.10
  • 10.1.4.11
  • 10.1.4.12
  • 10.1.4.13
  • 10.2
  • 10.2.1
  • 10.2.1.1
  • 10.2.1.2
  • 10.2.1.4
  • 10.2.2
  • 10.2.2.1
  • 10.2.2.2
  • 10.2.3
  • 10.2.3.1
  • 10.2.4
  • 10.2.4.2
  • 10.2.4.3
  • 10.2.4.4
  • 10.2.4.6
  • 10.2.4.7
  • 10.2.5
  • 10.2.5.1
  • 10.2.5.2
  • 10.2.5.3
  • 10.2.5.4
  • 10.3
  • 10.3.1
  • 10.3.1.1
  • 10.3.1.2
  • 10.3.2
  • 10.3.2.1
  • 10.3.2.2
  • 10.3.3
  • 10.3.3.1
  • 10.3.3.2
  • 10.3.3.3
  • 10.3.3.4
  • 10.4
  • 10.4.1
  • 10.4.1.1
  • 10.4.1.2
  • 10.4.1.3
  • 10.5
  • 10.6
  • 11
  • 11.0
  • 11.1
  • 11.1.1
  • 11.1.1.1
  • 11.1.1.1.1
  • 11.1.1.1.2
  • 11.1.2
  • 11.1.2.1
  • 11.1.2.1.1
  • 11.1.2.1.2
  • 11.1.2.1.2.1
  • 11.1.2.1.2.2
  • 11.1.2.2
  • 11.1.2.3
  • 11.1.2.3.1
  • 11.1.2.3.2
  • 11.1.2.4
  • 11.1.2.5
  • 11.1.3
  • 11.1.3.1
  • 11.1.3.1.1
  • 11.1.3.1.2
  • 11.1.3.2
  • 11.1.3.2.1
  • 11.1.3.2.2
  • 11.1.3.3
  • 11.1.3.4
  • 11.1.3.5
  • 11.1.3.5.1
  • 11.1.3.5.2
  • 11.1.4.1
  • 11.1.4.2
  • 11.1.4.3
  • 11.1.4.4
  • 11.1.4.4.1
  • 11.1.4.4.2
  • 11.1.4.5
  • 11.1.4.5.1
  • 11.1.4.5.2
  • 11.1.4.10
  • 11.1.4.11
  • 11.1.4.12
  • 11.1.4.13
  • 11.2
  • 11.2.1
  • 11.2.1.1
  • 11.2.1.1.1
  • 11.2.1.1.2
  • 11.2.1.2
  • 11.2.1.4
  • 11.2.1.4.1
  • 11.2.1.4.2
  • 11.2.2
  • 11.2.2.1
  • 11.2.2.2
  • 11.2.3
  • 11.2.3.1
  • 11.2.4
  • 11.2.4.3
  • 11.2.4.4
  • 11.2.4.6
  • 11.2.4.7
  • 11.2.5
  • 11.2.5.1
  • 11.2.5.2
  • 11.2.5.3
  • 11.2.5.3.1
  • 11.2.5.3.2
  • 11.2.5.4
  • 11.3
  • 11.3.1
  • 11.3.1.1
  • 11.3.1.1.1
  • 11.3.1.1.2
  • 11.3.2
  • 11.3.2.1
  • 11.3.2.2
  • 11.3.3
  • 11.3.3.1
  • 11.3.3.1.1
  • 11.3.3.1.2
  • 11.3.3.2
  • 11.3.3.3
  • 11.3.3.4
  • 11.4
  • 11.4.1
  • 11.4.1.1
  • 11.4.1.1.1
  • 11.4.1.1.2
  • 11.4.1.2
  • 11.4.1.2.1
  • 11.4.1.2.2
  • 11.4.1.3
  • 11.4.1.3.1
  • 11.4.1.3.2
  • 11.5
  • 11.5.1
  • 11.5.2
  • 11.5.2.1
  • 11.5.2.2
  • 11.5.2.3
  • 11.5.2.4
  • 11.5.2.5
  • 11.5.2.6
  • 11.5.2.7
  • 11.5.2.8
  • 11.5.2.9
  • 11.5.2.10
  • 11.5.2.11
  • 11.5.2.12
  • 11.5.2.13
  • 11.5.2.14
  • 11.5.2.15
  • 11.5.2.16
  • 11.5.2.17
  • 11.6
  • 11.6.1
  • 11.6.2
  • 11.7
  • 11.8
  • 11.8.1
  • 11.8.2
  • 11.8.3
  • 11.8.4
  • 11.8.5
  • 12
  • 12.1
  • 12.1.1
  • 12.1.2
  • 12.2
  • 12.2.1
  • 12.2.2
  • 12.2.3
  • 12.2.4
  • 13
  • 13.1
  • 13.1.1
  • 13.1.2
  • 13.1.3
  • 13.1.4
  • 13.1.5
  • 13.1.6
  • 13.2
  • 13.3

Found in this section

5 Generic requirements

5.1 Closed functionality
EN 301 549 clauseDetermination of conformance

5.1.1 Introduction (informative)

ICT has closed functionality for many reasons, including design or policy. Some of the functionality of products can be closed because the product is self-contained and users are precluded from adding peripherals or software in order to access that functionality.

ICT may have closed functionality in practice even though the ICT was not designed, developed or supplied to be closed.

Computers that do not allow end-users to adjust settings or install software are functionally closed.

C.5.1.1 Introduction (informative)

Clause 5.1.1 is informative and does not contain requirements that require testing.

5.1.2 General
EN 301 549 clauseDetermination of conformance

5.1.2.1 Closed functionality

Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.

NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to the requirements of clause 5.1.

NOTE 2: The requirements within this clause replace those in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. This may be because they relate to compatibility with assistive technology or to the ability for the user to adjust system accessibility settings in products with closed functionality (e.g. products that prevent access to the system settings control panel).

C.5.1.2.1 Closed functionality

See clauses C.5.2 to C.13, as applicable.

5.1.2.2 Assistive technology

Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.6 as applicable. Personal headsets and induction loops shall not be classed as assistive technology for the purpose of this clause.

C.5.1.2.2 Assistive technology

Type of assessment

Testing

Pre-conditions

1. The ICT has closed functionality.

Procedure

1. Determine the closed functions of the ICT.

2. Check that the tests C.5.1.3 to C.5.1.6 can be carried out without the attachment or installation of any assistive technology except personal headsets or inductive loops.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1 is not met

5.1.3 Non-visual access
EN 301 549 clauseDetermination of conformance

5.1.3.1 Audio output of visual information

Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.

NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form.

NOTE 2: The visual information needed to enable use of some functions may include operating instructions and orientation, transaction prompts, user input verification, error messages and non-text content.

C.5.1.3.1 Audio output of visual information

Type of assessment

Testing

Pre-conditions

1. Visual information is needed to enable the use of those functions of the ICT that are closed to assistive technology for screen reading.

Procedure

1. Determine the functions of the ICT closed to screen reading.

2. Check that they are all operable using non-visual access.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1 is not met.

5.1.3.2 Auditory output delivery including speech

Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:

1. either directly by a mechanism included in or provided with the ICT; or

2. by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision.

NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in handset/headset, or other industry standard coupled peripheral.

NOTE 2: An industry standard connection could be a wireless connection.

NOTE 3: Some users may benefit from the provision of an inductive loop.

C.5.1.3.2 Auditory output delivery including speech

Type of assessment

Inspection

Pre-conditions

1. Auditory output is provided as non-visual access to closed functionality.

Procedure

1. Check that the auditory output is delivered by a mechanism included in or provided with the ICT.

2. Check that the auditory output is delivered by a personal headset that can be connected through a 3,5 mm audio jack or an industry standard connection without requiring the use of vision.

Result

Pass: Check 1 or 2 is true

Fail: Checks 1 and 2 are false

Not applicable: Pre-condition 1 is not met

5.1.3.3 Auditory output correlation

Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

C.5.1.3.3 Auditory output correlation

Clause 5.1.3.3 is informative only and contains no requirements requiring test.

5.1.3.4 Speech output user control

Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.

NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.

NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to start from the beginning.

C.5.1.3.4 Speech output user control

Type of assessment

Inspection

Pre-condition

1. Speech output is provided as non-visual access to closed functionality.

Procedure

1. Check that the speech output is capable of being interrupted when requested by the user.

2. Check that the speech output is capable of being repeated when requested by the user.

Result

Pass: All checks are true

Fail: Any check is false

Not applicable: Pre-condition 1 is not met

5.1.3.5 Speech output automatic interruption

Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.

NOTE: Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT may need to block all user action so that speech is not interrupted.

C.5.1.3.5 Speech output automatic interruption

Type of assessment

Inspection

Pre-conditions

1. Speech output is provided as non-visual access to closed functionality.

Procedure

1. Determine the closed functions of the ICT.

2. Check that the speech output for each single function is interrupted on a user action.

3. Check that the speech output for each single function is interrupted when new speech output begins.

Result

Pass: Check 2 and 3 are true

Fail: Check 2 or 3 are false

Not applicable: Pre-condition 1 is not met

5.1.3.6 Speech output for non-text content

Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1 Non-text content.

C.5.1.3.6 Speech output for non-text content

Type of assessment

Testing

Pre-conditions

1. Non-text content is presented to users via speech output.

Procedure

1. Check that speech output is provided as an alternative for non-text content.

2. Check that the non-text content is not pure decoration.

3. Check that the non-text content is not used only for visual formatting.

4. Check that the speech output follows the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1 Non-text content.

Result

Pass: Checks 1 and 2 and 3 and 4 are true; or 1 and 2 are false; or 1 and 3 are false

Fail: Checks 1 is true and 2 false; or 1 is true and 3 false; or 1 and 2 and 3 are true and 4 is false

Not applicable: Pre-condition 1 is not met

5.1.3.7 Speech output for video information

Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content.

NOTE: This speech output can take the form of an audio description or an auditory transcript of the video content.

C.5.1.3.7 Speech output for video information

Type of assessment

Testing

Pre-conditions

1. Pre-recorded video content is needed to enable the use of closed functions of ICT.

2. Speech output is provided as non-visual access to non-text content displayed on closed functionality.

Procedure

1. Check that the speech output presents equivalent information for the pre-recorded video content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

C.5.1.3.8 Masked entry

Type of assessment

Testing

Pre-conditions

1. Auditory output is provided as non-visual access to closed functionality.

2. The characters displayed are masking characters.

3. Any option to allow non-private auditory output has not been activated.

Procedure

1. Check that the auditory output is not a spoken version of the characters entered.

2. Check that the auditory output is known to be delivered only to a mechanism for private listening.

Result

Pass: Any check is true

Fail: All checks are false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.9 Private access to personal data

Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.

NOTE 1: This requirement does not apply in cases where data is not defined as being private according to the applicable privacy policy or where there is no applicable privacy policy.

NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

C.5.1.3.9 Private access to personal data

Type of assessment

Testing

Pre-conditions

1. Auditory output is provided as non-visual access to closed functionality.

2. The output contains data.

3. There is an applicable privacy policy which considers that data to be private.

Procedure

1. Check that the auditory output is only delivered through a mechanism for private listening.

2. Check that the mechanism for private listening can be connected without requiring the use of vision.

3. Check that the auditory output is delivered through all user-selectable mechanisms.

Result

Pass: Checks 1 and 2 or 3 are true

Fail: Checks 1 or 2 and 3 are false

Not applicable: Pre-conditions 1 or 3 are not met

5.1.3.10 Non-interfering audio output

Where auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.

C.5.1.3.10 Non-interfering audio output

Type of assessment

Testing

Pre-conditions

1. Auditory output is provided as non-visual access to closed functionality.

2. The ICT automatically plays interfering audible output.

Procedure

1. Check that the interfering audible output lasts no longer than three seconds.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.11 Private listening volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.

C.5.1.3.11 Private listening volume

Type of assessment

Inspection

Pre-conditions

1. The auditory output is provided as non-visual access to closed functionality.

2. The auditory output is delivered through a mechanism for private listening.

Procedure

1. Check that there is at least one non-visual mode of operation for controlling the volume.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.12 Speaker volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).

NOTE: For noisy environments, 65 dBA may not be sufficient.

C.5.1.3.12 Speaker volume

Type of assessment

Inspection and measurement

Pre-conditions

1. The auditory output is provided as non-visual access to closed functionality.

2. The auditory output is delivered through speakers.

Procedure

1. Check that a non-visual incremental volume control is provided.

2. Check that output amplification up to a level of at least 65 dBA (-29 dBPaA) is available.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.13 Volume reset

Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.

NOTE: A feature to disable the volume reset function may be provided in order to enable the single-user exception to be met.

C.5.1.3.13 Volume reset

Type of assessment

Inspection and measurement

Pre-conditions

1. The auditory output is provided as non-visual access to closed functionality.

2. The ICT is not dedicated to a single user.

Procedure

1. Check that a function that automatically resets the volume to be at a level of 65 dBA or less after every use is provided.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.14 Spoken languages

Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:

1. for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text;

2. where the content is generated externally and not under the control of the ICT vendor, the present clause shall not be required to apply for languages not supported by the ICT's speech synthesizer;

3. for displayed languages that cannot be selected using non-visual access;

4. where the user explicitly selects a speech language that is different from the language of the displayed content.

C.5.1.3.14 Spoken languages

Type of assessment

Testing

Pre-conditions

1. The speech output is provided as non-visual access to closed functionality.

2. The speech output is not proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

3. The content is not generated externally and is under the control of the ICT vendor.

4. The displayed languages can be selected using non-visual access.

5. The user has not selected a speech language that is different from the language of the displayed content.

Procedure

1. Check that the speech output is in the same human language of the displayed content provided.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1 or 3 are not met

5.1.3.15 Non-visual error identification

Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.

C.5.1.3.15 Non-visual error identification

Type of assessment

Testing

Pre-conditions

1. Speech output is provided as non-visual access to closed functionality.

2. An input error is automatically detected.

Procedure

1. Check that speech output identifies the item that is in error.

2. Check that the speech output describes the item that is in error.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or check 2 false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.16 Receipts, tickets, and transactional outputs

Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.

NOTE: The speech output may be provided by any element of the total ICT system.

C.5.1.3.16 Receipts, tickets, and transactional outputs

Type of assessment

Testing

Pre-conditions

1. The ICT is closed to visual access.

2. The ICT provides receipts, tickets, or other outputs as a result of a self-service transaction.

3. The information being checked is not printed copies of itineraries and maps.

Procedure

1. Check that speech output is provided which includes all information necessary to complete or verify the transaction.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1, 2 or 3 are not met

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE 1: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

NOTE 2: Table 5.1 and Figure 1 illustrate the relationship between the maximum viewing distance and minimum character height at the specified minimum subtended angle.

(See Table 5.1 and Figure 1)

C.5.1.4 Functionality closed to text enlargement

Type of assessment

Inspection and measurement

Pre-conditions

1. A functionality of the ICT is closed to enlargement features of platform or assistive technology.

2. A viewing distance is specified by the supplier.

Procedure

1. Measure the height of a capital letter H.

2. Check that it subtends an angle of at least 0,7 degrees at the specified viewing distance.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.5 Visual output for auditory information

Where auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the auditory output.

NOTE: This visual information can take the form of captions or text transcripts

C.5.1.5 Visual output for auditory information

Type of assessment

Inspection

Pre-conditions

1. Pre-recorded auditory information is needed to enable the use of closed functions of ICT.

Procedure

1. Check that the visual information is equivalent to the pre-recorded auditory output.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.1.6 Operation without keyboard interface
EN 301 549 clauseDetermination of conformance

5.1.6.1 Closed functionality

Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.

C.5.1.6.1 Closed functionality

Type of assessment

Inspection

Pre-conditions

1. ICT functionality is closed to keyboards or keyboard interfaces.

Procedure

1. Check that all functionality is operable without vision.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.1.6.2 Input focus

Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.

C.5.1.6.2 Input focus

Type of assessment

Inspection

Pre-conditions

1. ICT functionality is closed to keyboards or keyboard interfaces.

2. Input focus can be moved to a user interface element.

Procedure

1. Check that it is possible to move the input focus away from that element using the same mechanism.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

5.1.7 Access without speech

Where speech is needed to operate closed functions of ICT, the ICT shall provide at least one mode of operation using an alternative input mechanism that does not require speech.

C.5.1.7 Access without speech

Type of assessment

Inspection

Pre-conditions

1. Speech is needed to enable the use of closed functions of ICT.

Procedure

1. Check that the closed functions can be enabled by an alternative input mechanism that does not require speech.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.2 Activation of accessibility features

Where ICT has documented accessibility features, it shall be possible to activate those documented accessibility features that are required to meet a specific need without relying on a method that does not support that need.

C.5.2 Activation of accessibility features

Type of assessment

Inspection

Pre-conditions

1. The ICT has documented accessibility features to meet a specific need.

Procedure

1. Check that it is possible to activate those accessibility features without relying on a method that does not support that need.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.3 Biometrics

Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.

NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.

NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals with disabilities possess at least one of the specified biological characteristics. Examples of dissimilar biological characteristics are fingerprints, eye retinal patterns, voice, and face.

C.5.3 Biometrics

Type of assessment

Test 1

Pre-conditions

1. The ICT uses biological characteristic for user identification.

Procedure

1. Check that more than one means can be used for user identification.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Type of assessment

Test 2

Pre-conditions

1. The ICT uses biological characteristic for control of ICT.

Procedure

1. Check that more than one means can be used for control of ICT.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

C.5.4 Preservation of accessibility information during conversion

Type of assessment

Inspection

Pre-conditions

1. The non-proprietary information provided for accessibility is documented.

2. The ICT converts information or communication.

3. The non-proprietary information provided for accessibility can be contained in the destination format.

4. The non-proprietary information provided for accessibility can be supported by the destination format.

Procedure

1. Check that the non-proprietary information provided for accessibility is preserved when the ICT converts information or communication.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, 3 or 4 is not met

5.5 Operable parts
EN 301 549 clauseDetermination of conformance

5.5.1 Means of operation

Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.

C.5.5.1 Means of operation

Type of assessment

Testing

Pre-conditions

The ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate.

Procedure

1. Check that there is an accessible alternative means of operation that does not require these actions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

C.5.5.2 Operable parts discernibility

Type of assessment

Testing

Pre-conditions

The ICT has operable parts.

Procedure

1. Identify that there is a means to discern each operable part without vision.

2. Check that the action associated with the operable part has not been performed when using the means to discern each operable part of step 1.

Result

Pass: Checks 1 and 2 are true

Fail: Checks 1 or 2 are false

Not applicable: Pre-condition 1 is not met

5.6 Locking or toggle controls
EN 301 549 clauseDetermination of conformance

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

C.5.6.1 Tactile or auditory status

Type of assessment

Inspection

Pre-conditions

1. The ICT has a locking or toggle control.

2. The locking or toggle control is visually presented to the user.

Procedure

1. Check that there is at least one mode of operation where the status of all locking or toggle controls can be determined through touch without operating the control.

2. Check that there is at least one mode of operation where the status of all locking or toggle controls can be determined through sound without operating the control.

Result

Pass: Check 1 or 2 is true

Fail: Checks 1 and 2 are false

Not applicable: Pre-condition 1 or 2 is not met

5.6.2 Visual status

Where ICT has a locking or toggle control and the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example of making the status of a control determinable is a visual status indicator on a keyboard.

C.5.6.2 Visual status

Type of assessment

Inspection

Pre-conditions

1. The ICT has a locking or toggle control.

2. The locking or toggle control is presented to the user.

Procedure

1. Check that there is at least one mode of operation where the status of all locking or toggle controls can be visually determined when the control is presented.

Result: Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

1. the delay before the key repeat shall be adjustable to at least 2 seconds; and

2. the key repeat rate shall be adjustable down to one character per 2 seconds.

C.5.7 Key repeat

Type of assessment

Testing

Pre-conditions

1. The ICT has a key repeat function A keyboard or keypad with key repeat is provided.

2. The key repeat cannot be turned off.

Procedure

1. Check that the delay before key repeat can be adjusted to at least 2 seconds.

2. Check that the key repeat rate can be adjusted to 2 seconds per character.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-condition 1 or 2 is not met

5.8 Double-strike key acceptance

Where ICT has a keyboard or keypad, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.

C.5.8 Double-strike key acceptance

Type of assessment

Testing

Pre-conditions

1. The ICT has a keyboard or keypad

Procedure

1. Check that there is a mechanism that allows adjustment of the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke.

2. Adjust that mechanism to its maximum setting.

3. Press any key.

4. After a delay of 0,5 seconds press the same key as that pressed in step 3.

5. Check whether the keystroke of step 4 has been accepted.

Result

Pass: Check 1 is true and check 5 is false

Fail: Check 1 is false or check 5 is true

Not applicable: Pre-condition 1 is not met

5.9 Simultaneous user actions

Where ICT uses simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.

NOTE: Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or having to touch a surface with more than one finger are examples of simultaneous user actions.

C.5.9 Simultaneous user actions

Type of assessment

Inspection

Pre-conditions

1. ICT has a mode of operation requiring simultaneous user actions.

Procedure

1. Check that there is a mode of operation that does not require simultaneous user actions.

2. Determine all the user controllable functions of the ICT.

3. Check that each user controllable function can be operated with a single user action.

Result

Pass: Check 3 is true

Fail: Check 3 is false for all modes of operation.

Not applicable: Pre-condition 1 is not met

6 ICT with two-way voice communication

EN 301 549 clauseDetermination of conformance

6.1 Audio bandwidth for speech

Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT shall be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7000 Hz.

NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 [i.21] is widely used.

NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation ITU-T G.722.2 [i.22] are sometimes used so as to avoid transcoding.

C.6.1 Audio bandwidth for speech

Type of assessment

Measurement

Pre-conditions

1. The ICT under test provides two-way voice communication.

Procedure

1. Check that the ICT can encode and decode audio with a frequency range with an upper limit of at least 7000 Hz.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

6.2 Real-time text (RTT) functionality
6.2.1 RTT provision
EN 301 549 clauseDetermination of conformance

6.2.1.1 RTT communication

Where ICT is in a mode that provides a means for two-way voice communication, the ICT shall provide a means for two-way RTT communication, except where this would require design changes to add input or output hardware to the ICT.

NOTE 1: This requirement includes those products which do not have physical display or text entry capabilities but have the capability to connect to devices that do have such capabilities. It also includes intermediate ICT between the endpoints of the communication.

NOTE 2: There is no requirement to add: a hardware display, a hardware keyboard, or hardware to support the ability to connect to a display or keyboard, wired or wirelessly, if this hardware would not normally be provided.

NOTE 3: For the purposes of interoperability, support of Recommendation ITU-T T.140 [i.36] is widely used.

C.6.2.1.1 RTT communication

Type of assessment

Inspection

Pre-conditions

1. The ICT under test has a mode that provides a means for two-way voice communication.

2. The ICT is in the mode that provides a means for two-way voice communication.

3. An "RTT reference terminal" is available.

Procedure

1. Check that the ICT allows two-way RTT communication with the "reference" ICT.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

Not testable: Pre-condition 3 is not met

NOTE: An "RTT reference terminal" is a terminal specifically designed for testing RTT capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent "RTT reference terminal".

6.2.1.2 Concurrent voice and text

Where ICT provides a means for two-way voice communication and for users to communicate by RTT, it shall allow concurrent voice and text through a single user connection.

NOTE 1: With many-party communication, as in a conference system, it is allowed (but not required or necessarily recommended) that RTT be handled in a single display field and that "turn-taking" be necessary to avoid confusion (in the same way that turn-taking is required for those presenting/talking with voice).

NOTE 2: With many-party communication, best practice is for hand-raising for voice users and RTT users to be handled in the same way, so that voice and RTT users are in the same queue

NOTE 3: With a many-party conference system that has chat as one of its features - the RTT (like the voice) would typically be separate from the chat so that RTT use does not interfere with chat (i.e. people can be messaging in the chat field while the person is presenting/talking with RTT - in the same manner that people message using the chat feature while people are talking with voice). RTT users would then use RTT for presenting and use the Chat feature to message while others are presenting (via Voice or RTT).

NOTE 4: The availability of voice and RTT running concurrently (and separately from chat) can also allow the RTT field to support text captioning when someone is speaking (and it is therefore not being used for RTT since it is not the RTT user's turn to speak).

NOTE 5: Where both server-side software and local hardware and software are required to provide voice communication, where neither part can support voice communication without the other and are sold as a unit for the voice communication function, the local and server-side components are considered a single product.

C.6.2.1.2 Concurrent voice and text

Type of assessment

Inspection

Pre-conditions

1. The ICT supports two-way voice communication.

2. The ICT provides a means for two-way RTT communication.

Procedure

1. Check that ICT allows the concurrent use of voice and RTT through a single user connection.

Result

Pass: Checks 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

6.2.2 Display of RTT (Real-time Text)
EN 301 549 clauseDetermination of conformance

6.2.2.1 Visually distinguishable display

Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from and separated from received text.

NOTE: The ability of the user to choose between having the send and receive text be displayed in-line or separately, and with options to select, allows users to display RTT in a form that works best for them. This would allow Braille users to use a single field and take turns and have text appear in the sequential way that they may need or prefer.

C.6.2.2.1 Visually distinguishable display

Type of assessment

Inspection

Pre-conditions

1. The ICT under test has RTT send and receive capabilities.

2. The ICT supports RTT mechanism(s).

3. A "reference" RTT-capable terminal using mechanisms supported by the ICT system is connected at the other end of the system to the ICT under test.

Procedure

1. The ICT under test is connected to the ICT system terminated by the "reference" terminal.

2. The different elements of the ICT are in an operational status (the connection is active and the terminals are in the relevant RTT mode) and the two terminals are communicating to each other.

3. A Short text sequence is sent by the ICT under test.

4. A Short text sequence is sent by the "reference" terminal.

5. Check, on the ICT under test, that displayed sent text is visually differentiated from and separated from received text.

Result

Pass: Check 5 is true

Fail: Check 5 is false

NOTE: A "reference" terminal is a terminal having RTT send and receive capabilities that uses the RTT mechanisms supported by the ICT system. This "reference" terminal is the responsibility of the test laboratory.

6.2.2.2 Programmatically determinable send and receive direction

Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted/received text shall be programmatically determinable, unless the RTT is implemented as closed functionality.

NOTE: This enables screen readers to distinguish between incoming text and outgoing text when used with RTT functionality.

C.6.2.2.2 Programmatically determinable send and receive direction

Type of assessment

Inspection

Pre-conditions

1. The ICT under test has RTT send and receive capabilities.

2. The RTT is open functionality.

3. A “RTT reference terminal” is available.

Procedure

1. The ICT under test is connected to the "RTT reference terminal".

2. The different elements of the ICT are in an operational status (the connection is active and the terminals are in the relevant RTT mode) and the two terminals are communicating with each other

3. A Short text sequence is sent by the ICT under test.

4. A Short text sequence is sent by the "RTT reference terminal".

5. Check that the send/receive direction of transmitted text is programmatically determinable.

Result

Pass: Check 5 is true

Fail: Check 5 is false

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

NOTE: An "RTT reference terminal" is a terminal specifically designed for testing RTT capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent "RTT reference terminal".

6.2.2.3 Speaker identification

Where ICT has RTT capabilities, and provides speaker identification for voice, the ICT shall provide speaker identification for RTT.

NOTE: This is necessary to enable both voice and RTT participants to know who is currently communicating, whether it be in RTT or voice.

C.6.2.2.3 Speaker identification

Type of assessment

Inspection

Pre-conditions

1. The ICT has RTT capabilities.

2. The ICT provides speaker identification for voice.

3. An "RTT reference terminal" is available.

Procedure

1. The ICT under test is connected to the "RTT reference terminal".

2. RTT is sent from the "RTT reference terminal".

3. Check by observation whether the ICT under test provides speaker identification for RTT incoming text.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

NOTE: An "RTT reference terminal" is a terminal specifically designed for testing RTT capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent "RTT reference terminal".

6.2.2.4 Visual indicator of audio with RTT

Where ICT provides two-way voice communication, and has RTT capabilities, the ICT shall provide a real-time visual indicator of audio activity on the display.

NOTE 1: The visual indicator may be a simple character position on the display that flickers on and off to reflect audio activity, or presentation of the information in another way that can be both visible to sighted users and passed on to deaf-blind users who are using a braille display.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

C.6.2.2.4 Visual indicator of audio with RTT

Type of assessment

Inspection

Pre-conditions

1. ICT provides two-way voice communication.

2. ICT has RTT capabilities.

Procedure

1. ICT under test is connected to another ICT providing two-way voice communication that is compatible with the voice communication on the ICT under test.

2. A person speaks into the other ICT.

3. Check by observation whether there is a real-time visual indicator of audio activity.

Result

Pass: Check 3 is true

Fail: Check 3 is false

Not applicable: Pre-condition 1 or 2 is not met

NOTE: The indicator should flicker in real time in a way that reflects the audio activity.

6.2.3 Interoperability

Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by clause 6.2.1.1) shall support the applicable RTT interoperability mechanisms described below:

1. ICT interoperating with other ICT directly connected over the Public Switched Telephone Network (PSTN) using Recommendation ITU-T V.18 [i.23] or any of its annexes for text telephony signals at the PSTN interface;

2. ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using RTT that conforms to IETF RFC 4103 [i.13]. For ICT interoperating with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, the set of protocols specified in ETSI TS 126 114 [i.10], ETSI TS 122 173 [i.11] and ETSI TS 134 229 [i.12] describe how IETF RFC 4103 [i.13] would apply;

3. ICT interoperating with other ICT using technologies other than a or b, above, using a relevant and applicable common specification for RTT exchange that is published and available for the environments in which they will be operating. This common specification shall include a method for indicating loss or corruption of characters;

4. ICT interoperating with other ICT using a standard for RTT that has been introduced for use in any of the above environments, and is supported by all of the other active ICT that support voice and RTT in that environment.

NOTE 1: In practice, new standards are introduced as an alternative codec/protocol that is supported alongside the existing common standard and used when all end-to-end components support it while technology development, combined with other reasons including societal development and cost efficiency, may make others become obsolete.

NOTE 2: Where multiple technologies are used to provide voice communication, multiple interoperability mechanisms may be needed to ensure that all users are able to use RTT.

EXAMPLE: A conferencing system that supports voice communication through an internet connection might provide RTT over an internet connection using a proprietary RTT method (option c). However, regardless of whether the RTT method is proprietary or non-proprietary, if the conferencing system also offers telephony communication it will also need to support options a or b to ensure that RTT is supported over the telephony connection.

C.6.2.3 Interoperability

a)

Type of assessment

Test

Pre-conditions

1. The ICT provides a means for two-way voice communication over the Public Switched Telephone Network (PSTN).

2. The ICT provides a means for two-way RTT communication.

3. A "V.18 reference terminal" is available.

Procedure

1. Check that the ICT interoperates over the Public Switched Telephone Network (PSTN), with the V.18 reference terminal connected to the PSTN as described in Recommendation ITU-T V.18 [i.23] or any of its annexes for text telephony signals at the PSTN interface

Result

Pass: Check 1 is true

Fail: Checks 1 is false

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

NOTE: A "V.18 reference terminal" is a terminal specifically designed for testing V.18 capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent reference terminal.

b)

Type of assessment

Test

Pre-conditions

1. The ICT provides a means for two-way voice communication using VOIP with Session Initiation Protocol (SIP).

2. The ICT provides a means for two-way RTT communication.

3. An "RTT reference terminal" is available.

Procedure

1. Check that the ICT interoperates with the "RTT reference terminal" using VOIP with Session Initiation Protocol (SIP) and using RTT that conforms to IETF RFC 4103 [i.13].

2. If the ICT interoperates with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, check that it follows the set of protocols in ETSI TS 126 114 [i.10], ETSI TS 122 173 [i.11] and ETSI TS 134 229 [i.12] that specify how IETF RFC 4103 [i.13] applies.

Result

Pass: Check 1 is true and, if the ICT interoperates with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, check 2 is true.

Fail: Check 1 is false or, if the ICT interoperates with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, check 2 is false.

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

NOTE: An "RTT reference terminal" is a terminal specifically designed for testing RTT capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent "RTT reference terminal".

c)

Type of assessment

Test

Pre-conditions

1. The ICT provides a means for two-way voice communication using technologies other than PSTN or VOIP with Session Initiation Protocol (SIP).

2. The ICT provides a means for two-way RTT communication.

3. An "RTT reference terminal" is available for that mode of RTT communication.

Procedure

1. Check that the ICT interoperates with the "RTT reference terminal" using a relevant and applicable common specification for RTT exchange that is published and available for the environment in which the ICT will be operating.

2. Check that the common specification in check 1 includes a method for indicating loss or corruption of characters.

Result

Pass: Check 1 and 2 are true

Fail: Checks 1 or 2 are false

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

NOTE: An "RTT reference terminal" is a terminal specifically designed for testing RTT capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent "RTT reference terminal".

d)

Type of assessment

Test

Pre-conditions

1. The ICT provides a means for two-way voice communication.

2. The ICT provides a means for two-way RTT communication.

3. An "RTT reference terminal" is available using the new RTT Standard.

Procedure

1. Check that the ICT under test interoperates with the "RTT reference terminal" for the new RTT standard that has been introduced for use.

2. Check that the new RTT standard is supported by all of the other active ICT that support voice and RTT in the same environment.

Result

Pass: Check 1 and 2 are true

Fail: Checks 1 or 2 are false

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

RTT (Real-time text) responsiveness

Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network or platform on which the ICT runs within 500 ms of the time that the smallest reliably composed unit of text entry is available to the ICT for transmission. Delays due to platform or network performance shall not be included in the 500 ms limit.

NOTE 1: For character by character input, the "smallest reliably composed unit of text entry" would be a character. For word prediction it would be a word. For some voice recognition systems - the text may not exit the recognition software until an entire word (or phrase) has been spoken. In this case, the smallest reliably composed unit of text entry available to the ICT would be the word (or phrase).

NOTE 2: The 500 ms limit allows buffering of characters for this period before transmission so character by character transmission is not required unless the characters are generated more slowly than 1 per 500 ms.

NOTE 3: A delay of 300 ms, or less, produces a better impression of flow to the user.

C.6.2.4 RTT (Real-time text) responsiveness

Type of assessment

Inspection of Measurement data or Test

Pre-conditions

1. The ICT under test utilises RTT input.

2. The ICT under test is connected to a device or software that can determine when characters are transmitted by the ICT under test.

Procedure

1. Enter single characters to the terminal under test.

2. Check the time at which input entry has occurred (e.g. characters appear up on the local screen).

3. Check the period between input entry to the ICT under test and the time when the text is transmitted to the ICT network or platform.

Result

Pass: Check 3 is less than or equal to 500 ms.

Fail: Check 3 is greater than 500 ms.

Not applicable: Pre-condition 1 is not met

Not testable: Pre-condition 2 is not met

NOTE: As described in the notes to clause 6.2.4, the identification of when input entry has occurred may vary according to the type of RTT system under test.

6.3 Caller ID

Where ICT provides caller identification or similar telecommunications functions are provided, the caller identification and similar telecommunications functions shall be available in text form as well as being programmatically determinable, unless the functionality is closed.

C.6.3 Caller ID

Type of assessment

Inspection

Pre-conditions

1. The ICT provides caller identification, or similar telecommunications functions are provided.

Procedure

1. Check that the information delivered by each function is available in text form.

2. Check that the information delivered by each function is programmatically determinable.

Result

Pass: Check 1 is true and either check 2 is true or the functionality is closed

Fail: Check 1 is false or check 2 is false when the functionality is not closed

Not applicable: Pre-condition 1 is not met.

6.4 Alternatives to voice-based services

Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT shall offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.

NOTE 1: Tasks that involve both operating the interface and perceiving the information would require that both the interface and information be accessible without use of speech or hearing.

NOTE 2: Solutions capable of handling audio, RTT and video media could satisfy the above requirement.

C.6.4 Alternatives to voice-based services

Type of assessment

Inspection

Pre-conditions

1. The ICT provides real-time voice-based communication.

2. The ICT provides voice mail, auto-attendant, or interactive voice response facilities.

Procedure

1. Check that the ICT offers users a means to access the information without the use of hearing or speech.

2. Check that a user can carry out the tasks provided by the system without the use of hearing or speech.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-condition 1 or 2 is not met

6.5 Video communication
EN 301 549 clauseDetermination of conformance

6.5.1 General (informative)

Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with a resolution of at least Quarter Video Graphics Array (QVGA, 320 x 240), a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.

Increasing the resolution and frame rate further improves both sign language (especially finger spelling) and lipreading, with frame rate being more important than resolution.

Time differences between audio and video (asynchronicity) can have a great impact on lip-reading - with video that lags behind audio having greater negative effect.

End-to-end latency can be a problem in video (sign) communication. Overall delay values below 400 ms are preferred, with an increase in preference down to 100 ms. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.

NOTE: Recommendation ITU-T F.703 [i.37] defines and gives requirements for Total Conversation that relate to the integration of audio, RTT and video in a single user connection.

C.6.5.1 General (informative)

Clause 6.5.1 is informative only and contains no requirements requiring test.

6.5.2 Resolution

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

1. shall support at least QVGA resolution;

2. should preferably support at least VGA resolution.

C.6.5.2 Resolution

Type of assessment

Inspection

Pre-conditions

1. The ICT provides 2 way voice communication.

2. The ICT includes real-time video functionality.

Procedure

1. Check that the video communication resolution is QVGA resolution or better.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

6.5.3 Frame rate

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

1. shall support a frame rate of at least 20 frames per second (FPS);

2. should preferably support a frame rate of at least 30 frames per second (FPS) with or without sign language in the video stream.

C.6.5.3 Frame rate

Type of assessment

Inspection

Pre-conditions

1. The ICT provides 2 way voice communication.

2. The ICT includes real-time video functionality.

Procedure

1. Check that the video communication frame rate is equal to or higher than 20 frames per second.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

6.5.4 Synchronization between audio and video

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT shall ensure a maximum time difference of 100 ms between the speech and video presented to the user.

NOTE: Recent research shows that, if audio leads the video, the intelligibility suffers much more than the reverse.

C.6.5.4 Synchronization between audio and video

Type of assessment

Measurement

Pre-conditions

1. The ICT provides 2 way voice communication.

2. The ICT includes real-time video functionality.

Procedure

1. Check that the time difference between the speech and video presented to the user is equal to or less than 100 ms.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

6.5.5 Visual indicator of audio with video

Where ICT provides two-way voice communication, and includes real-time video functionality, the ICT shall provide a real-time visual indicator of audio activity.

NOTE 1: The visual indicator may be a simple visual dot or LED, or other type of on/off indicator, that flickers to reflect audio activity.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

C.6.5.5 Visual indicator of audio with video

Type of assessment

Measurement

Pre-conditions

1. ICT provides two-way voice communication.

2. ICT has real-time video capabilities.

Procedure

1. ICT under test is connected to another ICT providing two-way voice communication that is compatible with the voice communication on the ICT under test.

2. A person speaks into the other ICT.

3. Check by observation whether there is a real-time visual indicator of audio activity

Result

Pass: Check 3 is true

Fail: Check 3 is false

Not applicable: Pre-condition 1 or 2 is not met

NOTE: The indicator should flicker in real time in a way that reflects the audio activity.

6.5.6 Speaker identification with video (sign language) communication

Where ICT provides speaker identification for voice users, it shall provide a means for speaker identification for real-time signing and sign language users once the start of signing has been indicated.

NOTE 1: The speaker ID can be in the same location as for voice users for multiparty calls.

NOTE 2: This mechanism might be triggered manually by a user, or automatically where this is technically achievable.

C.6.5.6 Speaker identification with video (sign language) communication

Type of assessment

Measurement

Pre-conditions

1. The ICT provides 2 way voice communication.

2. The ICT includes real-time video.

Procedure

1. The ICT under test is connected to a compatible ICT that supports video and a person communicates in sign language.

2. Check by observation whether the ICT under test provides a means for speaker identification for the sign language users.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1 or 2 is not met

Where ICT provides speaker identification for voice users, it shall provide a means for speaker identification for real-time signing and sign language users once the start of signing has been indicated.

NOTE 1: The speaker ID can be in the same location as for voice users for multiparty calls.

NOTE 2: This mechanism might be triggered manually by a user, or automatically where this is technically achievable.

6.6 Alternatives to video-based services

Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:

1. for audible information, without the use of hearing;

2. for spoken commands, without the use of speech;

3. for visual information, without the use of vision.

NOTE: Solutions capable of generating real-time captions or handling RTT (real-time text) could satisfy the above requirement.

C.6.6 Alternatives to video-based services

Clause 6.6 is advisory only and contains no testable requirements.

7 ICT with video capabilities

7.1 Caption processing technology
EN 301 549 clauseDetermination of conformance

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

NOTE 3: Clause 7.1.1 refers to the ability of the player to display captions. Clauses 9.1.2.2, 10.1.2.2 and 11.1.2.2 refer to the provision of captions for the content (the video).

C.7.1.1 Captioning playback

Type of assessment

Test 1

Pre-conditions

1. The ICT displays or processes video with synchronized audio.

2. Captions are provided in the video.

Procedure

1. Check that there is a mechanism to display the captions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Type of assessment

Test 2

Pre-conditions

1. The ICT displays or processes video with synchronized audio.

2. Closed captions are provided by the content.

Procedure

1. Check that there is a mechanism to choose to display the captions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions as follows:

  • Captions in recorded material: within 100 ms of the time stamp of the caption.
  • Live captions: within 100 ms of the availability of the caption to the player.

C.7.1.2 Captioning synchronization

Type of assessment

Inspection

Pre-conditions

1. The ICT has a mechanism to display captions.

Procedure

1. Check that the mechanism to display the captions preserves the synchronization between the audio and corresponding captions within a tenth of a second of the time stamp of the caption, or the availability of the caption to the player if a live caption.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

C.7.1.3 Preservation of captioning

Type of assessment

Inspection

Pre-conditions

1. The ICT transmits converts or records video with synchronized audio.

Procedure

1. Check that the ICT preserves caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

7.1.4 Captions characteristics

Where ICT displays captions, it shall provide a way for the user to adapt the displayed characteristics of captions to their individual requirements, except where the captions are displayed as unmodifiable characters.

NOTE 1: Defining the background and foreground colour of subtitles, font type, size opacity of the background box of subtitles, and the contour or border of the fonts can contribute to meeting this requirement.

NOTE 2: Subtitles that are bitmap images are examples of unmodifiable characters.

C.7.1.4 Captions characteristics

Type of assessment

Inspection

Pre-conditions

1. The ICT displays captions.

2. The captions under test are displayed as modifiable characters.

Procedure

1. Check that the ICT provides a way for the user to adapt the displayed characteristics of captions to their individual requirements.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

7.1.5 Spoken subtitles

Where ICT displays video with synchronized audio, it shall have a mode of operation to provide a spoken output of the available captions, except where the content of the displayed captions is not programmatically determinable.

NOTE 1: Being able to manage speech output range for spoken subtitles independently from general ICT speech is preferable for most users. That is possible when the audio file with spoken subtitle is delivered in a separate audio track and mixed in the end user’s device.

NOTE 2: Presenting the separate audio track with spoken subtitles in synchronization with the displayed subtitles/captions improves understandability of the subtitles.

NOTE 3: Providing subtitles/captions as separate text-streams, facilitates converting the respective texts into audio.

NOTE 4: Subtitles that are bitmap images are examples where the content of the displayed captions will not be programmatically determinable.

C.7.1.5 Spoken subtitles

Type of assessment

Inspection

Pre-conditions

1. The ICT displays video with synchronized audio.

2. The content of the captions under test are programmatically determinable.

Procedure

1. Check that there is a mode of operation to provide a spoken output of the available captions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

7.2 Audio description technology
EN 301 549 clauseDetermination of conformance

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks

NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.

NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

C.7.2.1 Audio description playback

Type of assessment

Inspection

Pre-conditions

1. The ICT displays video with synchronized audio.

Procedure

1. Check that there is an explicit and separate mechanism for audio description.

2. Check that there is a mechanism to select and play the audio description to the default audio channel.

3. Check that the ICT enables the user to select and play several audio tracks.

Result

Pass: Check 1 and 2 are true or 1 is false and 3 is true

Fail: Check 1 is true and 2 is false or 1 is false and 3 is false

Not applicable: Pre-condition 1 is not met.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

C.7.2.2 Audio description synchronization

Type of assessment

Inspection

Pre-conditions

1. The ICT has a mechanism to play audio description.

Procedure

1. Check that the synchronization between the audio/visual content and the corresponding audio description is preserved.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

C.7.2.3 Preservation of audio description

Type of assessment

Inspection

Pre-conditions

1. The ICT transmits converts or records video with synchronized audio.

Procedure

1. Check that the ICT preserves audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

C.7.3 User controls for captions and audio description

Type of assessment

Inspection

Pre-conditions

1. The ICT primarily display materials containing video with associated audio content.

Procedure

1. Check that user controls to activate subtitling and audio descriptions are provided to the user at the same level of interaction as the primary media controls.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8 Hardware

8.1 General
EN 301 549 clauseDetermination of conformance

8.1.1 Generic requirements

The "generic requirements" of clause 5 also apply to ICT that is hardware.

C.8.1.1 Generic requirements

Clause 8.1.1 is advisory only and contains no testable requirements.

8.1.2 Standard connections

Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.

NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the use of standard connections on ICT.

NOTE 2: The word connection applies to both physical and wireless connections.

NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.

C.8.1.2 Standard connections

Type of assessment

Inspection

Pre-conditions

1. The ICT provides user input or output device connection points.

Procedure

1. Check that one type of connection conforms to an industry standard non-proprietary format.

2. Check that one type of connection conforms to an industry standard non-proprietary format through the use of commercially available adapters.

Result

Pass: Check 1 or 2 is true

Fail: Checks 1 and 2 are false

Not applicable: Pre-condition 1 is not met.

NOTE: The connections may be physical or wireless connections.

8.1.3 Colour

Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

C.8.1.3 Colour

Type of assessment

Inspection

Pre-conditions

1. The hardware aspects of the ICT conveys visual information using colour coding as a means to indicate an action, to prompt a response, or to distinguish a visual element.

Procedure

1. Check that an alternative form of visual coding is provided.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8.2 Hardware products with speech output
8.2.1 Speech volume gain
EN 301 549 clauseDetermination of conformance

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 [i.2] are deemed to comply with this requirement.

C.8.2.1.1 Speech volume range

Type of assessment

Inspection based on measurement data

Pre-conditions

1. The ICT hardware has speech output.

Procedure

1. Check that the ICT is certified to meet ANSI/TIA-4965 [i.2].

2. Measure the level (in dB) of the speech output at the lowest volume setting.

3. Measure the level (in dB) of the speech output at the highest volume setting.

4. Check that the range between 1 and 2 is greater than or equal to 18 dB.

Result

Pass: Check 1 or 4 is true

Fail: Check 1 and 4 are false

Not applicable: Pre-condition 1 is not met.

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

C.8.2.1.2 Incremental volume control

Type of assessment

Inspection based on measurement data

Pre-conditions

1. The ICT hardware has speech output.

2. The volume control is incremental.

Procedure

1. Measure the level (in dB) of the speech output at the lowest volume setting.

2. Check if one intermediate step provides a level 12 dB above the lowest volume level measured in step 1.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1 or 2 is not met.

8.2.2 Magnetic coupling
EN 301 549 clauseDetermination of conformance

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETSI ETS 300 381 [1], it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1 [2].

NOTE 1: ICT fulfilling the requirements of TIA-1083-A [i.24] is deemed to comply with the requirements of this clause.

NOTE 2: Magnetic coupling is also known as inductive coupling for T-coil.

C.8.2.2.1 Fixed-line devices

Type of assessment

Inspection based on measurement data

Pre-conditions

1. The ICT hardware is a fixed line communication device with an audio output that is normally held to the ear.

Procedure

1. Check that the ICT is certified to meet TIA-1083-A [i.24].

2. Measurements are made according to ETSI ES 200 381-1 [2] which prove that the requirements defined in that standard are fulfilled.

3. The ICT carries the "T" symbol specified in ETSI ETS 300 381 [1].

Result

Pass: Check 1 or 2 is true and check 3 is true

Fail: Checks 1 and 2 are false or check 3 is false

Not applicable: Pre-condition 1 is not met.

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2 [3].

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 [i.1] is deemed to comply with the requirements of this clause.

C.8.2.2.2 Wireless communication devices

Type of assessment

Inspection based on measurement data

Pre-conditions

1. The ICT hardware is a wireless communication device which is normally held to the ear.

Procedure

1. Check that the ICT is certified to meet ANSI/IEEE C63.19 [i.1].

2. Check that the ICT provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2 [3].

Result

Pass: Check 1 or 2 is true

Fail: Checks 1 and 2 are false

Not applicable: Pre-condition 1 is not met.

8.3 Stationary ICT
EN 301 549 clauseDetermination of conformance

8.3.0 General (informative)

The present document defines the dimensions for accessing stationary ICT that can be placed in a built environment, but does not define the dimensions of the built environment in general.

The scope includes stationary ICT, of which floors and circulation spaces are "an integral part" (typically kiosks and cabins), and where there are external reach ranges relevant for operating the stationary ICT.

Clauses 8.3.2 to 8.3.4 specify mandatory limits for the maximum and minimum height of operable parts and displays. Based on dimensions shown in Figure 53 of ISO 21542:2011 [i.34], it is recommended that the possible height range is reduced to:

  • minimum and maximum heights of operable parts: 800 mm and 1100 mm respectively, and
  • minimum and maximum heights of displays: 1200 mm and 1400 mm respectively.

C.8.3.0 General (informative)

Clause 8.3.0 is advisory only and contains no testable requirements.

8.3.1 Forward or side reach

Stationary ICT shall conform to either clause 8.3.2 or clause 8.3.3

NOTE 1: This does not preclude conforming to both clauses.

NOTE 2: The dimensions set out in clauses 407.8.3 and 407.8.2 of Section 508 of the Rehabilitation Act, as published in January 2017 [i.25], are identical to those given in clauses 8.3.2 and 8.3.3 of the present document

NOTE 3: Physical access to stationary ICT is dependent on the dimensions of both the ICT and the environment in which it is installed and operated. Clause 8.3 does not apply to the accessibility of the physical environment external to the ICT.

C.8.3.1 Forward or side reach

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT.

Procedure

1. Check whether the ICT conforms to clause 8.3.2.2.

2. Check whether the ICT conforms to clause 8.3.2.3.

Result

Pass: Check 1 or 2 is true

Fail: Checks 1 and 2 are false

Not applicable: Pre-condition 1 is not met.

8.3.2 Forward reach
EN 301 549 clauseDetermination of conformance

8.3.2.1 Unobstructed high forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no higher than 1220 mm (48 inches) above the floor of the access space. This is shown in Figure 2.

C.8.3.2.1 Unobstructed high forward reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. No part of the stationary ICT obstructs the forward reach.

Procedure

1. Check that at least one of each type of operable part is located no higher than 1200 mm (48 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.2.2 Unobstructed low forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no lower than 380 mm (15 inches) above the floor of the access space. This is shown in Figure 2

C.8.3.2.2 Unobstructed low forward reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. No part of the stationary ICT obstructs the forward reach.

Procedure

1. Check that at least one of each type of operable part is located no lower than 380 mm (15 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

8.3.2.3 Obstructed forward reach
EN 301 549 clauseDetermination of conformance

8.3.2.3.1 Clear space

Where an obstruction is an integral part of the stationary ICT and hinders the access to any type of operable part, the ICT shall provide a clear space which extends beneath the obstructing element for a distance not less than the required reach depth over the obstruction.

NOTE: Ensuring that there will be unhindered "access to any type of operable part" guarantees that a user will be able access at least one of each type of operable part.

C.8.3.2.3.1 Clear space

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT.

2. An integral part of the stationary ICT forms an obstruction which hinders to any type of operable part.

Procedure

1. Check that the ICT provides a clear space which extends beneath the obstructing element for a distance not less than the required reach depth over the obstruction.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

8.3.2.3.2 Obstructed (<510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1220 mm (48 inches) above the floor contact of the ICT. This is shown in Figure 3 (a).

C.8.3.2.3.2 Obstructed (<510 mm) forward reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. An integral part of the stationary ICT forms an obstruction which is less than 510 mm (20 inches) deep.

Procedure

1. Check that the forward reach to at least one of each type of operable part is no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Result

Pass: Check 1 is true.

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

8.3.2.3.3 Obstructed (<635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1120 mm (44 inches) above the floor contact of the ICT. This is shown in Figure 3 (b).

8.3.2.3.3 Obstructed (<635 mm) forward reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. An integral part of the stationary ICT forms an obstruction which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) deep.

Procedure

1. Check that the forward reach to at least one of each type of operable part is no higher than 1120 mm (44 inches) above the floor contact of the ICT.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not meted.

8.3.2.4 Knee and toe clearance width

Where the space under an obstacle that is integral to the ICT is part of access space, the clearance shall be at least 760 mm (30 inches) wide.

C.8.3.2.4 Knee and toe clearance width

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. The space under an obstacle that is an integral part of the ICT is part of an access space.

Procedure

1. Check that the width of the knee clearance is greater than 760 mm (30 inches).

2. Check that the width of the toe clearance is greater than 760 mm (30 inches).

Result

Pass: Checks 1 and 2 are true

Fail: Checks 1 or 2 are false

Not applicable: Pre-condition 1 or 2 is not met

8.3.2.5 Toe clearance

Where an obstacle is integral to the ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and shall:

1. extend 635 mm (25 inches) maximum under the whole obstacle;

2. provide a space at least 430 mm (17 inches) deep and 230 mm (9 inches) above the floor under the obstacle;

3. extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

This is shown in Figure 4.

C.8.3.2.5 Toe clearance

a)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. The space under an obstacle that is an integral part of the ICT is part of an access space.

Procedure

1. Check that the width of the knee clearance is greater than 760 mm (30 inches).

2. Check that the width of the toe clearance is greater than 760 mm (30 inches).

Result

Pass: Checks 1 and 2 are true

Fail: Checks 1 or 2 are false

Not applicable: Pre-condition 1 or 2 is not met.

b)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a toe clearance space under any obstacle that is an integral part of the ICT that is less than 230 mm (9 inches) above the floor.

Procedure

1. Check that the toe clearance is at least 430 mm (17 inches) deep and 230 mm (9 inches) above the floor under the obstacle.

Result

Pass: Checks 1 is true

Fail: Checks 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

c)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a toe clearance space under any obstacle that is an integral part of the ICT that is less than 230 mm (9 inches) above the floor.

Procedure

1. Check that the toe clearance extends no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

Result

Pass: Checks 1 is true

Fail: Checks 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

8.3.2.6 Knee clearance

Where an obstacle is integral to the ICT, the space under the obstacle that is between 230 mm (9 inches) and 685 mm (27 inches) above the floor is considered knee clearance and shall:

1. extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;

2. extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;

3. extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;

4. be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.

This is shown in Figure 5.

C.8.3.2.6 Knee clearance

a)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a knee clearance space under the obstacle between 230 mm (9 inches) and 685 mm (25 inches) above the floor.

Procedure

1. Check that there is a knee clearance that extends less than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

b)

Type of assessment

Inspection and measurement

Pre-conditions

1.The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a knee clearance space under the obstacle between 230 mm (9 inches) and 685 mm (25 inches) above the floor.

Procedure

1. Check that there is a knee clearance that extends at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

c)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a knee clearance space under the obstacle between 230 mm (9 inches) and 685 mm (25 inches) above the floor.

Procedure

1. Check that there is a knee clearance that extends more than 205 mm (9 inches) under the obstruction at a height of 685 mm (25 inches) above the floor.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

d)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a knee clearance space under the obstacle between 230 mm (9 inches) and 685 mm (25 inches) above the floor.

Procedure

1. Check that the reduction in depth of the knee clearance is no greater than 25 mm (1 inch) for each 150 mm (6 inches) in height.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

8.3.3 Side reach
EN 301 549 clauseDetermination of conformance

8.3.3.1 Unobstructed high side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space. This is shown in Figure 6.

C.8.3.3.1 Unobstructed high side reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. Side reach is unobstructed or is obstructed by an element that is an integral part of the stationary ICT which is less than 510 mm (20 inches).

Procedure

1. Check that the high side reach to at least one of each type of operable part is no higher than 1 220 mm (48 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.3.2 Unobstructed low side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space. This is shown in Figure 6.

C.8.3.3.2 Unobstructed low side reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. Side reach is unobstructed or is obstructed by an element that is an integral part of the stationary ICT which is less than 510 mm (20 inches).

Procedure

1. Check that the low side reach to at least one of each type of operable part is greater than or equal to 380 mm (15 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.3.3 Obstructed side reach
EN 301 549 clauseDetermination of conformance

8.3.3.3.1 Obstructed (≤ 255 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is less than or equal to 255 mm (10 inches), the high side reach to at least one of each type of operable part shall be no higher than 1220 mm (48 inches) above the floor of the access space. This is shown in Figure 7 (a).

C.8.3.3.3.1 Obstructed (≤ 255 mm) side reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstruction, less than or equal to 255 mm (10 inches) in depth, that is an integral part of the ICT.

Procedure

1. Check that the high side reach to at least one of each type of operable part is no higher than 1 220 mm (48 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.3.3.2 Obstructed (≤ 610 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is greater than 255 mm (10 inches) with a maximum depth of 610 mm (24 inches), the high side reach to at least one of each type of operable part shall be no higher than 1170 mm (46 inches) above the floor of the access space. This is shown in Figure 7 (b)

C.8.3.3.3.2 Obstructed (≤ 610 mm) side reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstruction, greater than 255 mm (10 inches) and no more than 610 mm (24 inches) in depth, that is an integral part of the ICT.

Procedure

1. Check that the high side reach to at least one of each type of operable part is no higher than 1 170 mm (46 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.4 Clear floor or ground space
EN 301 549 clauseDetermination of conformance

8.3.4.1 Change in level

Where stationary ICT has a floor within it, then any change of floor level within it or entering it shall be ramped with a slope no steeper than 1:48. Exceptions:

1. If the change in floor level is less than or equal to 6,4 mm (¼ inch) the change may be vertical as shown in Figure 8.

2. If the change in floor level is less than or equal to 13 mm (½ inch) the change may have a slope not steeper than 1:2 as shown in Figure 9.

C.8.3.4.1 Change in level

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is a floor within the ICT.

3. The floor has a change in level.

Procedure

1. If the change in level is ramped, check that it has a slope less than 1:48.

2. If there is a vertical change of floor level, check that it is less than or equal to 6,4 mm.

3. If there is a vertical or sloped change in floor level, check that the slope is not greater than 1:2.

Result

Pass: Check 1 or 2 or 3 is true.

Fail: Checks 1 and 2 and 3 are false

Not applicable: Pre-condition 1 or 2 or 3 is not met

8.3.4.2 Clear floor or ground space

Where stationary ICT has an operating area within it, it shall provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1220 mm (48 inches) from which to operate the ICT. This is shown in Figure 10.

C.8.3.4.2 Clear floor or ground space

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an operating area within it.

Procedure

1. Check that there is a clear floor area with minimum rectangular dimensions of 760 mm on one edge and 1220 mm on the other edge.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.4.3 Approach
EN 301 549 clauseDetermination of conformance

8.3.4.3.1 General

Where stationary ICT has an access space inside it, at least one full side of the space shall be unobstructed.

C.8.3.4.3.1 General

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT.

2. There is an access space inside it.

Procedure

1. Check that one full side of the space is unobstructed.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

8.3.4.3.2 Forward approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space shall be a minimum of 915 mm (36 inches) wide. This is shown in Figure 11.

C.8.3.4.3.2 Forward approach

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT containing an alcove.

2. The operating area is within the alcove.

3. The depth of the alcove is greater than 610 mm

4. A forward approach is necessary.

Procedure

1. Check that the width of the alcove is greater than 915 mm.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, 3 or 4 is not met

8.3.4.3.3 Parallel approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space shall be a minimum of 1525 mm (60 inches) wide. This is shown in Figure 12.

C.8.3.4.3.3 Parallel approach

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT containing an alcove.

2. The operating area is within the alcove.

3. The depth of the alcove is greater than 380 mm.

4. A parallel approach is possible.

Procedure

1. Check that the width of the access space is greater than 1 525 mm.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, 3 or 4 is not met

8.3.5 Visibility

Where stationary ICT provides one or more display screens, at least one of each type of display screen shall be positioned such that the information on the screen is legible from a point located 1015 mm (40 inches) above the centre of the floor of the operating area.

NOTE: The intent of this requirement is that the information on the screen can be read by users with normal vision and appropriate language skills, when seated in a wheelchair.

C.8.3.5 Visibility

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT.

2. One or more display screens are provided.

Procedure

1. Check that at least one of each type of display screen is positioned such that the information on the screen is legible from a point located 1015 mm (40 inches) above the centre of the floor of the operating area.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.6 Installation instructions

Installation instructions shall be made available for all stationary ICT. These instructions shall give guidance on how to install the ICT in a manner that takes into account applicable requirements for accessibility of the built environment as they apply to the installation of the ICT. Where there are no such requirements the instructions should require that the dimensions of the installed ICT conform to clauses 8.3.2 to 8.3.5 of the present document.

C.8.3.6 Installation instructions

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT.

Procedure

1. Check that installation instructions are made available.

2. Check that the instructions give guidance on how to install the ICT in a manner that ensures that the dimensions of the installed ICT conform to clauses 8.3.2 to 8.3.4.

3. Check that the instructions say that the installers should also take into account applicable requirements for accessibility of the built environment as they apply to the installation of the ICT.

Result

Pass: Checks 1, 2 and 3 are true

Fail: Checks 1 or 2 or 3 are false

Not applicable: Pre-condition 1 is not met.

8.4 Mechanically operable parts
EN 301 549 clauseDetermination of conformance

8.4.1 Numeric keys

Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.

NOTE: Recommendation ITU-T E.161 [i.20] describes the 12-key telephone keypad layout and provides further details of the form of tactile markers.

C.8.4.1 Numeric keys

Type of assessment

Inspection

Pre-conditions

1. The ICT has physical numeric keys arranged in a 12-key telephone keypad layout.

Procedure

1. Check that the number five key is tactilely distinct from the other keys of the keypad.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8.4.2 Operation of mechanical parts
EN 301 549 clauseDetermination of conformance

8.4.2.1 Means of operation of mechanical parts

Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.

C.8.4.2.1 Means of operation of mechanical parts

Type of assessment

Inspection

Pre-conditions

1. The ICT has operable parts that requires grasping, pinching, or twisting of the wrist to operate.

Procedure

1. Check that there is an accessible alternative means of operation that does not require these actions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8.4.2.2 Force of operation of mechanical parts

Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.

NOTE: ISO 21542:2011 [i.34]: Building Construction - Accessibility and Usability of the Built Environment recommends a value between 2,5 and 5 Newtons.

C.8.4.2.2 Force of operation of mechanical parts

Type of assessment

Inspection

Pre-conditions

1. The ICT has a control which requires a force greater than 22,2 N to operate it.

Procedure

1. Check that an accessible alternative means of operation is provided that requires a force less than or equal to 22,2 N.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8.4.3 Keys, tickets and fare cards

Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.

NOTE: ETSI ETS 300 767 [i.6] defines suitable tactile indications for plastic cards.

C.8.4.3 Keys, tickets and fare cards

Type of assessment

Inspection

Pre-conditions

1. ICT provides keys, tickets or fare cards, and their orientation is important for further use.

Procedure

1. Check that keys, tickets or fare cards have an orientation that is tactilely discernible

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8.5 Tactile indication of speech mode

Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.

NOTE: The tactile indication could include Braille instructions.

C.8.5 Tactile indication of speech mode

Type of assessment

Inspection

Pre-conditions

1. The ICT is designed for shared use.

2. Speech output is available.

Procedure

1. Check that a tactile indication of the means to initiate the speech mode of operation is provided.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

9 Web

EN 301 549 clauseDetermination of conformance

9.0 General (informative)

Requirements in clause 9 apply to web pages (as defined in clause 3.1) including:

  • Conformance with W3C Web Content Accessibility Guidelines (WCAG 2.0) Level AA is equivalent to conforming with clauses 9.1.1, 9.1.2, 9.1.3.1 to 9.1.3.3, 9.1.4.1 to 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.2, 9.2.3, 9.2.4, 9.3, 9.4.1.1, 9.4.1.2 and the conformance requirements of clause 9.6 of the present document.
  • Conformance with W3C Web Content Accessibility Guidelines (WCAG 2.1) [5] Level AA is equivalent to conforming with all of clauses 9.1 to 9.4 and the conformance requirements of clause 9.6 of the present document.
  • Requirements for non-web documents and non-web software are given in clauses 10 and 11 respectively.

NOTE 1: When evaluating websites they are evaluated as individual web pages. Web applications, including mobile web applications, are covered under the definition of web page which is quite broad and covers all web content types.

NOTE 2: WCAG 2.0 is identical to ISO/IEC 40500:2012: "Information technology - W3C Web Content Accessibility Guidelines (WCAG) 2.0" [4].

The requirements in clauses 9.1 to 9.4 are written using the concept of satisfying success criteria (defined in clause 3.1). A web page satisfies a WCAG success criterion when the success criterion does not evaluate to false when applied to the web page. This implies that if the success criterion puts conditions on a specific feature and that specific feature does not occur in the web page, then the web page satisfies the success criterion.

NOTE 3: For example, a web page that does not contain pre-recorded audio content in synchronized media will automatically satisfy WCAG success criterion 1.2.2 (captions - pre-recorded) and, in consequence, will also conform to clause 9.1.2.2.

In addition to Level AA success criteria, the Web Content Accessibility Guidelines also include success criteria for Level AAA. These are listed in clause 9.5 of the present document. Web authors and procurement accessibility specialists are encouraged to consider whether any of the WCAG Level AAA success criteria offer suggestions that may be applicable and relevant to their project, as well as potentially beneficial to some users.

NOTE 4: The W3C states that "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content".

NOTE 5: "Void" clauses have been inserted in order to maintain alignment with the numbering of WCAG 2.1 Level A and Level AA Success Criteria.

C.9.0 General (informative)

Clause 9.0 is informative only and contains no requirements requiring test.

9.1 Perceivable
9.1.1 Text alternatives
EN 301 549 clauseDetermination of conformance

9.1.1.1 Non-text content

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.1.1 Non-text content.

C.9.1.1.1 Non-text content

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.1.1 Non-text content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.1.1 Non-text content.

9.1.2 Time-based media
EN 301 549 clauseDetermination of conformance

9.1.2.1 Audio-only and video-only (prerecorded)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

C.9.1.2.1 Audio-only and video-only (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

9.1.2.2 Captions (prerecorded)

Where ICT is a web page, it shall satisfy the WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

C.9.1.2.2 Captions (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

9.1.2.3 Audio description or media alternative (prerecorded)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

C.9.1.2.3 Audio description or media alternative (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

9.1.2.4 Captions (live)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

C.9.1.2.4 Captions (live)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

9.1.2.5 Audio description (prerecorded)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

C.9.1.2.5 Audio description (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

9.1.3 Adaptable
EN 301 549 clauseDetermination of conformance

9.1.3.1 Info and relationships

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

C.9.1.3.1 Info and relationships

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

9.1.3.2 Meaningful sequence

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

C.9.1.3.2 Meaningful sequence

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

9.1.3.3 Sensory characteristics

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

C.9.1.3.3 Sensory characteristics

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

9.1.3.4 Orientation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.4 Orientation.

C.9.1.3.4 Orientation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.4 Orientation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.3.4 Orientation.

9.1.3.5 Identify input purpose

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

C.9.1.3.5 Identify input purpose

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

9.1.4 Distinguishable
EN 301 549 clauseDetermination of conformance

9.1.4.1 Use of colour

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.1 Use of Color.

C.9.1.4.1 Use of colour

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.1 Use of Color.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.1 Use of Color.

9.1.4.2 Audio control

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.2 Audio Control.

C.9.1.4.2 Audio control

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.2 Audio Control.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.2 Audio Control.

9.1.4.3 Contrast (minimum)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

C.9.1.4.3 Contrast (minimum)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

9.1.4.4 Resize text

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.4 Resize text.

C.9.1.4.4 Resize text

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.4 Resize text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.4 Resize text.

9.1.4.5 Images of text

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.5 Images of Text.

C.9.1.4.5 Images of text

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.5 Images of Text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.5 Images of Text.

9.1.4.10 Reflow

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.10 Reflow.

C.9.1.4.10 Reflow

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.10 Reflow.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.10 Reflow.

9.1.4.11 Non-text contrast

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

C.9.1.4.11 Non-text contrast

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

9.1.4.12 Text spacing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

C.9.1.4.12 Text spacing

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.12 Text spacing.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.12 Text spacing.

9.1.4.13 Content on hover or focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

C.9.1.4.13 Content on hover or focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

9.2 Operable
9.2.1 Keyboard accessible
EN 301 549 clauseDetermination of conformance

9.2.1.1 Keyboard

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.1 Keyboard.

C.9.2.1.1 Keyboard

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.1.1 Keyboard.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.1.1 Keyboard.

9.2.1.2 No keyboard trap

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap.

C.9.2.1.2 No keyboard trap

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap.

9.2.1.4 Character key shortcuts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

C.9.2.1.4 Character key shortcuts

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts

9.2.2 Enough time
EN 301 549 clauseDetermination of conformance

9.2.2.1 Timing adjustable

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable.

C.9.2.2.1 Timing adjustable

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable.

9.2.2.2 Pause, stop, hide

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide.

C.9.2.2.2 Pause, stop, hide

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide.

9.2.3 Seizures and physical reactions
EN 301 549 clauseDetermination of conformance

9.2.3.1 Three flashes or below threshold

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold.

C.9.2.3.1 Three flashes or below threshold

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold.

9.2.4 Navigable
EN 301 549 clauseDetermination of conformance

9.2.4.1 Bypass blocks

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.1 Bypass Blocks.

C.9.2.4.1 Bypass blocks

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.1 Bypass Blocks.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.1 Bypass Blocks.

9.2.4.2 Page titled

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.2 Page Titled.

C.9.2.4.2 Page titled

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.2 Page Titled.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.2 Page Titled.

9.2.4.3 Focus Order

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.3 Focus Order.

C.9.2.4.3 Focus Order

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.3 Focus Order.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.3 Focus Order

9.2.4.4 Link purpose (in context)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context)-

C.9.2.4.4 Link purpose (in context)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

9.2.4.5 Multiple ways

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.5 Multiple Ways.

C.9.2.4.5 Multiple ways

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.5 Multiple Ways.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.5 Multiple Ways.

9.2.4.6 Headings and labels

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

C.9.2.4.6 Headings and labels

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

9.2.4.7 Focus visible

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

C.9.2.4.7 Focus visible

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

9.2.5 Input modalities
EN 301 549 clauseDetermination of conformance

9.2.5.1 Pointer gestures

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

C.9.2.5.1 Pointer gestures

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

9.2.5.2 Pointer cancellation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

C.9.2.5.2 Pointer cancellation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

9.2.5.3 Label in name

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

C.9.2.5.3 Label in name

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.3 Label in Name.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.5.3 Label in Name.

9.2.5.4 Motion actuation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

C.9.2.5.4 Motion actuation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

9.3 Understandable
9.3.1 Readable
EN 301 549 clauseDetermination of conformance

9.3.1.1 Language of page

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.1.1 Language of Page.

C.9.3.1.1 Language of page

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.1.1 Language of Page.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.1.1 Language of Page.

9.3.1.2 Language of parts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.1.2 Language of Parts.

C.9.3.1.2 Language of parts

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.1.2 Language of Parts.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.1.2 Language of Parts.

9.3.2 Predictable
EN 301 549 clauseDetermination of conformance

9.3.2.1 On focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.1 On Focus.

C.9.3.2.1 On focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.1 On Focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.2.1 On Focus.

9.3.2.2 On input

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.2 On Input.

C.9.3.2.2 On input

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.2 On Input.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.2.2 On Input.

9.3.2.3 Consistent navigation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.3 Consistent Navigation.

C.9.3.2.3 Consistent navigation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.3 Consistent Navigation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.2.3 Consistent Navigation.

9.3.2.4 Consistent identification

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.4 Consistent Identification.

C.9.3.2.4 Consistent identification

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.4 Consistent Identification.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.2.4 Consistent Identification.

9.3.3 Input assistance
EN 301 549 clauseDetermination of conformance

9.3.3.1 Error identification

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.1 Error Identification.

C.9.3.3.1 Error identification

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.1 Error Identification.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.3.1 Error Identification.

9.3.3.2 Labels or instructions

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

C.9.3.3.2 Labels or instructions

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

9.3.3.3 Error suggestion

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

C.9.3.3.3 Error suggestion

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

9.3.3.4 Error prevention (legal, financial, data)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data).

C.9.3.3.4 Error prevention (legal, financial, data)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data) .

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data).

9.4 Robust
9.4.1 Compatible
EN 301 549 clauseDetermination of conformance

9.4.1.1 Parsing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.1 Parsing.

C.9.4.1.1 Parsing

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 4.1.1 Parsing.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 4.1.1 Parsing.

9.4.1.2 Name, role, value

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value.

C.9.4.1.2 Name, role, value

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value.

9.4.1.3 Status messages

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

C.9.4.1.3 Status messages

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 4.1.3 Status Messages.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 4.1.3 Status Messages.

9.5 WCAG 2.1 AAA Success Criteria

In addition to the Level AA success criteria, included in clauses 9.1 to 9.4, the Web Content Accessibility Guidelines include success criteria for Level AAA. These are listed in Annex - Table 9.1. Web authors and procurement accessibility specialists are encouraged to consider the WCAG 2.1 Level AAA success criteria that, when it is possible to apply them, may provide access beyond that required in the present document.

NOTE: The W3C states that "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content". Refer to Table 9.1: WCAG 2.1 Level AAA Success Criteria in Annex – Tables and figures (from EN 301 549).

C.9.5 WCAG 2.1 AAA Success Criteria

Clause 9.5 is informative only and contains no requirements requiring test.

9.6 WCAG conformance requirements

Where ICT is a web page, it shall satisfy all the following five WCAG 2.1 conformance requirements at Level AA [5].

1. Conformance level

2. Full pages

3. Complete processes

4. Only Accessibility-Supported Ways of Using Technologies

5. Non-interference

NOTE 1: A Web page that meets all of requirements 9.1 to 9.4, or where a Level AA conforming alternate version (as defined in WCAG 2.1 [5]) is provided, will meet conformance requirement 1.

NOTE 2: According to W3C: "WCAG 2.1 extends Web Content Accessibility Guidelines 2.0 [4], which was published as a W3C Recommendation December 2008. Content that conforms to WCAG 2.1 also conforms to WCAG 2.0, and therefore to policies that reference WCAG 2.0" [4].

NOTE 3: Conformance requirement 5 states that all content on the page, including content that is not otherwise relied upon to meet conformance, meets clauses 9.1.4.2, 9.2.1.2, 9.2.2.2 and 9.2.3.1.

C.9.6 WCAG conformance requirements

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "1: Conformance level" at Level AA.

2. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "2: Full pages".

3. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "3: Complete processes".

4. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "4: Only Accessibility-Supported Ways of Using Technologies".

5. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "5: Non-interference".

Result

Pass: All checks are true

Fail: Any check is false

Not applicable: Pre-condition 1 is not met.

10 Non-web documents

EN 301 549 clauseDetermination of conformance

10.0 General (informative)

Requirements in clause 10 apply to documents:

  • documents that are not web pages;
  • documents that are not embedded in web pages; and
  • documents that are provided with web pages but are neither embedded nor rendered together with the web page from which they are provided (i.e. the present clause applies to downloadable documents).

Clause 9 provides requirements for documents that are in web pages or that are embedded in web pages and that are used in the rendering or that are intended to be rendered together with the web page in which they are embedded.

NOTE 1: Some examples of documents are letters, spreadsheets, emails, books, pictures, presentations, and movies that have an associated user agent such as a document reader, editor or media player.

NOTE 2: A single document may be composed of multiple files such as the video content, closed caption text, etc. This fact is not usually apparent to the end-user consuming the document/content.

NOTE 3: Documents require a user agent in order for the content to be presented to users. The requirements for user agents can be found in clause 11.

NOTE 4: The requirements for content that is part of software, can be found in clause 11.

NOTE 5: The success criteria set out in clause 10 are intended to harmonize with the Working Group Note [i.26] produced by the W3C's WCAG2ICT Task Force.

NOTE 6: "Void" clauses have been inserted in order to maintain alignment of the numbering in clauses 9, 10 and 11.

NOTE 7: Requirements in clause 10 also apply to documents that are protected using mechanisms such as digital signatures, encryption, password protection, and watermarks when they are presented to the user.

NOTE 8: It is best practice to provide meta data on the accessibility of the document within or separate to the document using WebSchemas/Accessibility 2.0 [i.38].

C.10.0 General (informative)

Clause 10.0 is advisory only and contains no requirements requiring test.

10.1 Perceivable
10.1.1 Text alternatives
EN 301 549 clauseDetermination of conformance

10.1.1.1 Non-text content

Where ICT is a non-web document, it shall satisfy the 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.

C.10.1.1.1 Non-text content

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.1.1 Non-text content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.1.1 Non-text content.

10.1.2 Time-based media
EN 301 549 clauseDetermination of conformance

10.1.2.1 Audio-only and video-only (prerecorded)

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

NOTE: The alternative can be provided directly in the document - or provided in an alternate version that meets the success criterion.

C.10.1.2.1 Audio-only and video-only (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

10.1.2.2 Captions (prerecorded)

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

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".

C.10.1.2.2 Captions (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

10.1.2.3 Audio description or media alternative (prerecorded)

Where ICT is a non-web document, 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.

C.10.1.2.3 Audio description or media alternative (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

10.1.2.4 Captions (live)

Where ICT is a non-web document, 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".

C.10.1.2.4 Captions (live)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

10.1.2.5 Audio description (prerecorded)

Where ICT is a non-web document, 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.

C.10.1.2.5 Audio description (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

10.1.3 Adaptable
EN 301 549 clauseDetermination of conformance

10.1.3.1 Info and relationships

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

NOTE: Where documents contain non-standard structure types (roles), it is best practice to map them to a standard structure type as a fall-back solution for the reader.

C.10.1.3.1 Info and relationships

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

10.1.3.2 Meaningful sequence

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

C.10.1.3.2 Meaningful sequence

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

10.1.3.3 Sensory characteristics

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

C.10.1.3.3 Sensory characteristics

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

10.1.3.4 Orientation

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

C.10.1.3.4 Orientation

Type of assessment

Inspection

Pre-conditions:

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.4 Orientation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.3.4 Orientation.

10.1.3.5 Identify input purpose

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

C.10.1.3.5 Identify input purpose

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

10.1.4 Distinguishable
EN 301 549 clauseDetermination of conformance

10.1.4.1 Use of colour

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.4.1 Use of Color.

C.10.1.4.1 Use of colour

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.1 Use of Color.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.1 Use of Color.

10.1.4.2 Audio control

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.1.

Table 10.1: Document success criterion: Audio control

If any audio in a document plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanismis available to control audio volume independently from the overall system volume level.

NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, all content in the document (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 document" "any content" with "any part of a document", "whole page" with "whole document", "on the Web page" with "in the document", removing "See Conformance Requirement 5: Non-Interference" and adding note 1.

C.10.1.4.2 Audio control

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.1.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

10.1.4.3 Contrast (minimum)

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

C.10.1.4.3 Contrast (minimum)

Type of assessment: Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

10.1.4.4 Resize text

Where ICT is a non-web document, 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.

NOTE 3: It is best practice to use only fonts that allow for scaling without loss of quality (e.g. pixelized presentation). This applies in particular to embedded fonts.

C.10.1.4.4 Resize text

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.4 Resize text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.4 Resize text.

10.1.4.5 Images of text

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.

C.10.1.4.5 Images of text

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.5 Images of Text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.5 Images of Text.

10.1.4.10 Reflow

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.2.

Table 10.2: Document success criterion: Reflow

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 1280 CSS pixels wide at 400% zoom. For documents which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024px 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.

C.10.1.4.10 Reflow

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.2.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.1.4.11 Non-text contrast

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

C.10.1.4.11 Non-text contrast

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document that does not have a fixed size content layout area that is essential to the information being conveyed.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

10.1.4.12 Text spacing

Where ICT is a non-web document that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

C.10.1.4.12 Text spacing

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.12 Text spacing.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.12 Text spacing.

10.1.4.13 Content on hover or focus

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

C.10.1.4.13 Content on hover or focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

10.2 Operable
10.2.1 Keyboard accessible
EN 301 549 clauseDetermination of conformance

10.2.1.1 Keyboard

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 2.1.1 Keyboard.

C.10.2.1.1 Keyboard

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.1.1 Keyboard.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.1.1 Keyboard.

10.2.1.2 No keyboard trap

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.3.

Table 10.3: Document success criterion: No keyboard trap

If keyboard focus can be moved to a component of the document using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, it is necessary for all content in the document (whether or not it is used to meet other success criteria) to meet this success criterion.

NOTE 2: Standard exit methods may vary by platform. For example, on many desktop platforms, the Escape key is a standard method for exiting.

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap replacing "page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference" and with the addition of note 2 above and with note 1 above re-drafted to avoid the use of the word "must".

C.10.2.1.2 No keyboard trap

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.3.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.1.4 Character key shortcuts

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

C.10.2.1.4 Character key shortcuts

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure:

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

10.2.2 Enough time
EN 301 549 clauseDetermination of conformance

10.2.2.1 Timing adjustable

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.4.

Table 10.4: Document success criterion: Timing adjustable

For each time limit that is set by the document, at least one of the following is true:

  • Turn off: The user is allowed to turn off the time limit before encountering it; or
  • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception: The time limit is essential and extending it would invalidate the activity; or
  • 20 Hour Exception: The time limit is longer than 20 hours.

NOTE 1: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with WCAG 2.1 Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable replacing "the content" with "documents" and with the words "WCAG 2.1" added before the word "Success Criterion" in note 1 above.

C.10.2.2.1 Timing adjustable

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.4.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.2.2 Pause, stop, hide

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.5.

Table 10.5: Document success criterion: Pause, stop, hide

For moving, blinking, scrolling, or auto-updating information, all of the following are true:

  • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
  • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

NOTE 1: For requirements related to flickering or flashing content, refer to WCAG 2.1 Guideline 2.3.

NOTE 2: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, it is necessary for all content in the document (whether it is used to meet other success criteria or not) to meet this success criterion.

NOTE 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

NOTE 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

NOTE 5: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide replacing "page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference" in note 2 of the success criterion, with the words "WCAG 2.1" added before the word "Guideline" in note 1 above and with note 2 above re-drafted to avoid the use of the word "must".

C.10.2.2.2 Pause, stop, hide

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.5.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.2.2 Pause, stop, hide.

10.2.3 Seizures and physical reactions
EN 301 549 clauseDetermination of conformance

10.2.3.1 Three flashes or below threshold

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.6.

Table 10.6: Document success criterion: Three flashes or below threshold

Documents do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, it is necessary for all content in the document (whether it is used to meet other success criteria or not) to meet this success criterion.

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold replacing "Web pages" with "documents", "the whole page" with "the whole document", "the Web page" with "the document" and removing "See Conformance Requirement 5: Non-Interference" and with note 1 above re-drafted to avoid the use of the word "must".

C.10.2.3.1 Three flashes or below threshold

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.6.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.4 Navigable
EN 301 549 clauseDetermination of conformance

10.2.4.2 Document titled

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.7.

Table 10.7: Document success criterion: Document titled

Documents have titles that describe topic or purpose.

NOTE 1: The name of a document (e.g. document, media file) is a sufficient title if it describes the topic or purpose.

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.4.2 Page Titled replacing "Web pages" with "documents" and with the addition of note 1 above.

C.10.2.4.2 Document titled

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.7.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.4.3 Focus Order

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.8.

Table 10.8: Document success criterion: Focus order

If a document can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

NOTE: This success criterion is identical to the WCAG 2.1 Success Criterion 2.4.3 Focus Order replacing "Web page" with "document".

C.10.2.4.3 Focus Order

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.8.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.4.4 Link purpose (in context)

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

C.10.2.4.4 Link purpose (in context)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

10.2.4.6 Headings and labels

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

C.10.2.4.6 Headings and labels

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

10.2.4.7 Focus visible

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

C.10.2.4.7 Focus visible

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

10.2.5 Input modalities
EN 301 549 clauseDetermination of conformance

10.2.5.1 Pointer gestures

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.9.

Table 10.9: Document success criterion: Pointer gestures

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to documents that interpret pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

C.10.2.5.1 Pointer gestures

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.9

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.5.2 Pointer cancellation

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.10.

Table 10.10: Document success criterion: Pointer cancellation

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to a document that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

C.10.2.5.2 Pointer cancellation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the success criterion in Table 10.10

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.5.3 Label in name

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

C.10.2.5.3 Label in name

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.5.3 Label in Name.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.5.3 Label in Name.

10.2.5.4 Motion actuation

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

C.10.2.5.4 Motion actuation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

10.3 Understandable
10.3.1 Readable
EN 301 549 clauseDetermination of conformance

10.3.1.1 Language of page

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.11.

Table 10.11: Document success criterion: Language of page

The default human language of each document can be programmatically determined.

NOTE: This success criterion is identical to the WCAG 2.1 Success Criterion 3.1.1 Language of Page replacing "web page" with "document".

C.10.3.1.1 Language of page

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.11.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.3.1.2 Language of parts

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.12.

Table 10.12: Document success criterion: Language of parts

The human language of each passage or phrase in the document can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

NOTE 1: There are some document technologies where there is no assistive technology supported method for marking the language for the different passages or phrases in the document, and it would not be possible to meet this success criterion with those technologies.

NOTE 2: Inheritance is one common method. For example a document provides the language that it is using and it can be assumed that all of the text or user interface elements within that document will be using the same language unless it is indicated.

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 3.1.2 Language of Parts replacing "content" with "document" and with the addition of notes 1 and 2 above.

C.10.3.1.2 Language of parts

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.12.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.3.2 Predictable
EN 301 549 clauseDetermination of conformance

10.3.2.1 On focus

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.2.1 On Focus.

NOTE: Some compound documents and their user agents are designed to provide significantly different viewing and editing functionality depending upon what portion of the compound document is being interacted with (e.g. a presentation that contains an embedded spreadsheet, where the menus and toolbars of the user agent change depending upon whether the user is interacting with the presentation content, or the embedded spreadsheet content). If the user uses a mechanism other than putting focus on that portion of the compound document with which they mean to interact (e.g. by a menu choice or special keyboard gesture), any resulting change of context would not be subject to this success criterion because it was not caused by a change of focus.

C.10.3.2.1 On focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 3.2.1 On Focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 3.2.1 On Focus.

10.3.2.2 On input

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.2.2 On Input.

C.10.3.2.2 On input

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 3.2.2 On Input.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 3.2.2 On Input.

10.3.3 Input assistance
EN 301 549 clauseDetermination of conformance

10.3.3.1 Error identification

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.3.1 Error Identification.

C.10.3.3.1 Error identification

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 3.3.1 Error Identification.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 3.3.1 Error Identification.

10.3.3.2 Labels or instructions

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

C.10.3.3.2 Labels or instructions

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

10.3.3.3 Error suggestion

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

C.10.3.3.3 Error suggestion

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 3.3.3 Error Suggestion">.

Result:

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 3.3.3 Error Suggestion

10.3.3.4 Error prevention (legal, financial, data)

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.13.

Table 10.13: Document success criterion: Error prevention (legal, financial, data)

For documents that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:

  • Reversible: Submissions are reversible.
  • Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
  • Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

NOTE: This success criterion is identical to the WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data) replacing "web pages" with "documents".

C.10.3.3.4 Error prevention (legal, financial, data)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.13.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.4 Robust
10.4.1 Compatible
EN 301 549 clauseDetermination of conformance

10.4.1.1 Parsing

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.14.

Table 10.14: Document success criterion: Parsing

For documents that use markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

NOTE 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.

NOTE 2: Markup is not always available to assistive technology or to user selectable user agents such as browsers. In such cases, conformance to this provision would have no impact on accessibility as it can for web content where it is exposed.

NOTE 3: Examples of markup that is separately exposed and available to assistive technologies and to user agents include but are not limited to: documents encoded in HTML, ODF, and OOXML. In these examples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may directly open the document, (b) by assistive technologies using DOM APIs of user agents for these document formats.

NOTE 4: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.1 Parsing replacing "In content implemented using markup languages" with "For documents that use markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent" with the addition of notes 2 and 3 above.

C.10.4.1.1 Parsing

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.14.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.4.1.2 Name, role, value

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.15.

Table 10.15: Document success criterion: Name, role, value

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification.

NOTE 2: For document formats that support interoperability with assistive technology, standard user interface components often meet this success criterion when used according to the general design and accessibility guidance for the document format.

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value replacing the original WCAG 2.1 note with note 1 and with the addition of note 2 above.

C.10.4.1.2 Name, role, value

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.15.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.4.1.3 Status messages

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

C.10.4.1.3 Status messages

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 4.1.3 Status Messages.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 4.1.3 Status Messages.

10.5 Caption positioning

Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.

C.10.5 Caption positioning

Clause 10.5 contains no requirements requiring test.

10.6 Audio description timing

Where ICT is a non-web document that contains synchronized media with audio description, the audio description should not interfere with relevant audio information in the synchronized media.

C.10.6 Audio description timing

Clause 10.6 contains no requirements requiring test.

11 Software

EN 301 549 clauseDetermination of conformance

11.0 General (informative)

This clause provides requirements for:

  • platform software;
  • software that provides a user interface including content that is in the software;
  • authoring tools;
  • software that operates as assistive technology.
  • mobile applications.

NOTE 1: User agents are examples of software that provide a user interface.

NOTE 2: The requirements for Web content, including software that is Web content, can be found in clause 9.

NOTE 3: The requirements for documents, that may be presented by user agents, can be found in clause 10.

NOTE 4: Although the accessibility of command line interfaces is not dealt with in the present document, accessibility may be achieved by context specific requirements, some of which may be found in clauses 5 or 11.

Requirements in clauses 11.1 to 11.5 apply to software:

  • that is not a web page;
  • not embedded in web pages nor used in the rendering or functioning of the page.

Clause 9 provides requirements for software that is in web pages or that is embedded in web pages and that is used in the rendering or that is intended to be rendered together with the web page in which it is embedded.

Some requirements in clauses 11.1 to 11.5 have different versions for open or closed functionality. In those cases, the corresponding clause will be divided into two subclauses.

The success criteria set out in clauses 11.1 to 11.5 are intended to harmonize with the W3C Working Group Note [i.26] produced by the W3C's WCAG2ICT Task Force.

NOTE 5: Software that provides a user interface includes its own content. Some examples of content in software include: the controls and text displayed in a menu bar of a graphical user interface application, images that appear in a toolbar, prompts spoken in an auditory user interface, other user interaction controls, and other text, graphics or material that is not loaded from outside the software.

C.11.0 General (informative)

Clause 11.0 is advisory only and contains no requirements requiring test.

11.1 Perceivable
11.1.1 Text alternatives
11.1.1.1 Non-text content
EN 301 549 clauseDetermination of conformance

11.1.1.1.1 Non-text content (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, 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.

C.11.1.1.1.1 Non-text content (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.1.1 Non-text Content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.1.1.1.2 Non-text content (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.6 (Speech output for non-text content).

C.11.1.1.1.2 Non-text content (closed functionality)

Type of assessment

Testing

Pre-conditions

1. The ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Non-text content is presented to users via speech output.

Procedure

1. Check that speech output is provided as an alternative for non-text content.

2. Check that the non-text content is not pure decoration.

3. Check that the non-text content is not used only for visual formatting.

4. Check that the speech output follows the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1 Non-text Content.

Result

Pass: Check (1 and 2 and 3 and 4 are true) or (1 and 2 are false) or (1 and 3 are false)

Fail: Checks (1 true and 2 false) or (1 true and 3 false) or (1 and 2 and 3 are true and 4 is false)

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.2 Time-based media
11.1.2.1 Audio-only and video-only (prerecorded)
EN 301 549 clauseDetermination of conformance

11.1.2.1.1 Audio-only and video-only (prerecorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading and where pre-recorded auditory information is not needed to enable the use of closed functions of ICT, 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.

Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)

Understanding Audio-only and Video-only (Prerecorded)

How to Meet 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-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
  • Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content

C.11.1.2.1.1 Audio-only and video-only (prerecorded - open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.2.1.2 Audio-only and video-only (prerecorded - closed functionality)
EN 301 549 clauseDetermination of conformance

11.1.2.1.2.1 Prerecorded audio-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the functionality of software that provides a user interface shall meet requirement 5.1.5 (Visual output for auditory information).

C.11.1.2.1.2.1 Prerecorded audio-only (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Pre-recorded auditory information is needed to enable the use of closed functions of ICT.

Procedure

1. Check that the visual information is equivalent to the pre-recorded auditory output.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.2.1.2.2 Prerecorded video-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

C.11.1.2.1.2.2 Prerecorded video-only (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Pre-recorded video content is needed to enable the use of closed functions of ICT.

4. Speech output is provided as non-visual access to non-text content displayed on closed functionality.

Procedure

1. Check that the speech output presents equivalent information for the pre-recorded video content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, 3 or 4 is not met.

11.1.2.2 Captions (prerecorded)

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

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".

C.11.1.2.2 Captions (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

11.1.2.3 Audio description or media alternative (prerecorded)
EN 301 549 clauseDetermination of conformance

11.1.2.3.1 Audio description or media alternative (prerecorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, 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.

C.11.1.2.3.1 Audio description or media alternative (prerecorded - open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

11.1.2.3.2 Audio description or media alternative (prerecorded - closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

C.11.1.2.3.2 Audio description or media alternative (prerecorded - closed functionality)

Type of assessment

Inspection

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Speech output is provided as non-visual access to non-text content displayed on closed functionality.

Procedure

1. Check that the speech output presents equivalent information for the pre-recorded video content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, or 3 is not met.

11.1.2.4 Captions (live)

Where ICT is non-web software that provides a user interface, 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".

C.11.1.2.4 Captions (live)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

11.1.2.5 Audio description (prerecorded)

Where ICT is non-web software that provides a user interface, 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.

C.11.1.2.5 Audio description (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

11.1.3 Adaptable
11.1.3.1 Info and relationships
EN 301 549 clauseDetermination of conformance

11.1.3.1.1 Info and relationships (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

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).

C.11.1.3.1.1 Info and relationships (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.1.3.1.2 Info and relationships (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

C.11.1.3.1.2 Info and relationships (closed functionality)

Clause 11.1.3.1.2 is advisory only and contains no testable requirements.

11.1.3.2 Meaningful sequence
EN 301 549 clauseDetermination of conformance

11.1.3.2.1 Meaningful sequence (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

C.11.1.3.2.1 Meaningful sequence (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.1.3.2.2 Meaningful sequence (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

C.11.1.3.2.2 Meaningful sequence (closed functionality)

Clause 11.1.3.2.2 is advisory only and contains no testable requirements.

11.1.3.3 Sensory characteristics

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

C.11.1.3.3 Sensory characteristics

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

11.1.3.4 Orientation

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

C.11.1.3.4 Orientation

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.4 Orientation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.3.4 Orientation.

11.1.3.5 Identify input purpose
EN 301 549 clauseDetermination of conformance

11.1.3.5.1 Identify input purpose (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

C.11.1.3.5.1 Identify input purpose (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

Result

Pass: Check 1 is true

Fail: Check 1 is false

11.1.3.5.2 Identify input purpose (closed functionality)

Where ICT is non-web software that provides a user interface and is closed to assistive technologies, in at least one mode of operation the ICT shall present to the user, in an audio form, the purpose of each input field collecting information about the user when the input field serves a purpose identified in the WCAG 2.1 Input Purposes for User Interface Components section.

C.11.1.3.5.2 Identify input purpose (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

2. The software does not provide support to assistive technologies for screen reading

3. Auditory output is provided as non-visual access to closed functionality.

Procedure

1. Check that the auditory output is delivered by a mechanism included in or provided with the ICT.

2. Check that the auditory output is delivered by a personal headset that can be connected through a 3,5 mm audio jack or an industry standard connection without requiring the use of vision.

3. Check that the auditory output comprises of purposes from the Input Purposes for User Interface Components section.

Result

Pass: Checks (1 or 2) is true and 3 is true

Fail: Checks (1 and 2) are false or 3 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.4 Distinguishable
EN 301 549 clauseDetermination of conformance

11.1.4.1 Use of colour

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.4.1 Use of Color.

C.11.1.4.1 Use of colour

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.1 Use of Color.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.1 Use of Color

11.1.4.2 Audio control

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.1.

Table 11.1: Software success criterion: Audio control

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.

C.11.1.4.2 Audio control

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.1.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.1.4.3 Contrast (minimum)

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

C.11.1.4.3 Contrast (minimum)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

11.1.4.4 Resize text
EN 301 549 clauseDetermination of conformance

11.1.4.4.1 Resize text (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to enlargement features of platform or assistive technology, 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.

C.11.1.4.4.1 Resize text (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.4 Resize text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.4 Resize text.

11.1.4.4.2 Resize text (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).

NOTE: Because the text rendering support in a closed environment may be more limited than the support found in user agents for the Web, meeting 11.1.4.4.2 in a closed environment may place a much heavier burden on the content author.

C.11.1.4.4.2 Resize text (closed functionality)

Type of assessment

Inspection and measurement

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to enlargement features of platform or assistive technology.

3. A viewing distance is specified by the supplier.

Procedure

1. Measure the height of a capital letter H.

2. Check that it subtends an angle of at least 0,7 degrees at the specified viewing distance.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.4.5 Images of text
EN 301 549 clauseDetermination of conformance

11.1.4.5.1 Images of text (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.

C.11.1.4.5.1 Images of text (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.5 Images of Text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.5 Images of Text.

11.1.4.5.2 Images of text (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it does not need to meet the WCAG 2.1 Success Criterion 1.4.5 Images of Text because there is no need to impose a requirement on all closed functionality that text displayed on the screen actually be represented internally as text (as defined by WCAG 2.1), given that there is no interoperability with assistive technology.

C.11.1.4.5.2 Images of text (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Non-text content is presented to users via speech output.

Procedure

1. Check that speech output is provided as an alternative for non-text content.

2. Check that the non-text content is not pure decoration.

3. Check that the non-text content is not used only for visual formatting.

4. Check that the speech output follows the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1 Non-text Content.

Result

Pass: Check (1 and 2 and 3 and 4 are true) or (1 and 2 are false) or (1 and 3 are false)

Fail: Checks (1 true and 2 false) or (1 true and 3 false) or (1 and 2 and 3 are true and 4 is false)

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.4.10 Reflow

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.2.

Table 11.2: Document success criterion: Reflow

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 1280 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 1024 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.

C.11.1.4.10 Reflow

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.2

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.1.4.11 Non-text contrast

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

C.11.1.4.11 Non-text contrast

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

11.1.4.12 Text spacing

Where ICT is non-web software that provides a user interface and that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

C.11.1.4.12 Text spacing

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion WCAG 2.1 Success Criterion 1.4.12 Text spacing.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.12 Text spacing.

11.1.4.13 Content on hover or focus

Where ICT is a non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

C.11.1.4.13 Content on hover or focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

11.2 Operable
11.2.1 Keyboard accessible
11.2.1.1 Keyboard
EN 301 549 clauseDetermination of conformance

11.2.1.1.1 Keyboard (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to keyboards or a keyboard interface, it shall satisfy the WCAG 2.1 Success Criterion 2.1.1 Keyboard.

NOTE: This does not imply that software is required to directly support a keyboard or "keyboard interface". Nor does it imply that software is required to provide a soft keyboard. Underlying platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard and would comply.

C.11.2.1.1.1 Keyboard (open functionality)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

2. The software provides support to keyboards or a keyboard interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.1.1 Keyboard.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.1.1 Keyboard.

11.2.1.1.2 Keyboard (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

C.11.2.1.1.2 Keyboard (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to keyboards or keyboard interfaces.

Procedure

1. Check that all functionality of the user interface is operable without vision.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.2.1.2 No keyboard trap

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.3.

Table 11.3: Software success criterion: No keyboard trap

If keyboard focus can be moved to a component of the software using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

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, it is necessary for all content in the software (whether or not it is used to meet other success criteria) to meet this success criterion.

NOTE 2: Standard exit methods may vary by platform. For example, on many desktop platforms, the Escape key is a standard method for exiting.

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap replacing "content", "page" and "Web page" with "software", removing "See Conformance Requirement 5: Non-Interference" and with the addition of note 2 above " and with note 1 above re-drafted to avoid the use of the word "shall".

C.11.2.1.2 No keyboard trap

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.3.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.2.1.4 Character key shortcuts
EN 301 549 clauseDetermination of conformance

11.2.1.4.1 Character key shortcuts (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

C.11.2.1.4.1 Character key shortcuts (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

11.2.1.4.2 Character key shortcuts (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

C.11.2.1.4.2 Character key shortcuts (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

2. ICT functionality is closed to keyboards or keyboard interfaces.

Procedure

1. Check that all functionality is operable without vision.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.2.2 Enough time
EN 301 549 clauseDetermination of conformance

11.2.2.1 Timing adjustable

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.4.

Table 11.4: Software success criterion: Timing adjustable

For each time limit that is set by the software, at least one of the following is true:

  • Turn off: The user is allowed to turn off the time limit before encountering it; or
  • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception: The time limit is essential and extending it would invalidate the activity; or
  • 20 Hour Exception: The time limit is longer than 20 hours.

NOTE 1: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with WCAG 2.1 Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable replacing "the content" with "software" and with the words "WCAG 2.1" added before the word "Success Criterion" in note 1 above.

C.11.2.2.1 Timing adjustable

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.4.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.2.2.2 Pause, stop, hide

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.5.

Table 11.5: Software success criterion: Pause, stop, hide

For moving, blinking, scrolling, or auto-updating information, all of the following are true:

  • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
  • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

NOTE 1: For requirements related to flickering or flashing content, refer to WCAG 2.1 Guideline 2.3.

NOTE 2: This success criteria is applicable to all content in the software (whether or not there is an alternate accessible mode of operation of the software) 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 (including a user interface element that enables the user to activate the alternate accessible mode of operation).

NOTE 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

NOTE 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

NOTE 5: This is to be applied to all content. Any content, whether informative or decorative, that is updated automatically, blinks, or moves may create an accessibility barrier.

NOTE 6: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide replacing "page" and "Web page" with "software", removing "See Conformance Requirement 5: Non-Interference" in note 2 of the success criterion, with the words "WCAG 2.1" added before the word "Guideline" in note 1 above, with note 2 above re-drafted to avoid the use of the word "must" and with the addition of note 5 above.

C.11.2.2.2 Pause, stop, hide

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.5.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.2.3 Seizures and physical reactions
EN 301 549 clauseDetermination of conformance

11.2.3.1 Three flashes or below threshold

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.6.

Table 11.6: Software success criterion: Three flashes or below threshold

Software does not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

NOTE 1: This success criteria is applicable to all content in the software (whether or not there is an alternate accessible mode of operation of the software) 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 (including a user interface element that enables the user to activate the alternate accessible mode of operation).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold replacing "Web pages" with "software", "the whole page" with "the whole software", "the Web page" with "the software" and removing "See Conformance Requirement 5: Non-Interference" and with note 1 above re-drafted to avoid the use of the word "must".

C.11.2.3.1 Three flashes or below threshold

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.6.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.2.4 Navigable
EN 301 549 clauseDetermination of conformance

11.2.4.3 Focus order

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.7.

Table 11.7: Software success criterion: Focus order

If software can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

NOTE: This success criterion is identical to the WCAG 2.1 Success Criterion 2.4.3 Focus order replacing "Web page" with "software".

C.11.2.4.3 Focus order

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.7.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.2.4.4 Link purpose (in context)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

C.11.2.4.4 Link purpose (in context)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

11.2.4.6 Headings and labels

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

NOTE: In software, headings and labels are used to describe sections of content and controls respectively. In some cases it may be unclear whether a piece of static text is a heading or a label. But whether treated as a label or a heading, the requirement is the same: that if they are present they describe the topic or purpose of the item(s) they are associated with.

C.11.2.4.6 Headings and labels

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

11.2.4.7 Focus visible

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

C.11.2.4.7 Focus visible

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

11.2.5 Input modalities
EN 301 549 clauseDetermination of conformance

11.2.5.1 Pointer gestures

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.8.

Table 11.8: Software success criterion: Pointer gestures

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

C.11.2.5.1 Pointer gestures

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.8.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.2.5.2 Pointer cancellation

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.9.

Table 11.9: Software success criterion: Pointer cancellation

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

C.11.2.5.2 Pointer cancellation

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.9.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.2.5.3 Label in name
EN 301 549 clauseDetermination of conformance

11.2.5.3.1 Label in name (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

C.11.2.5.3.1 Label in name (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.5.3 Label in Name.

Result

Pass: Check 1 is true

Fail: Check 1 is false

11.2.5.3.2 Label in name (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it should meet requirement 5.1.3.3 (Auditory output correlation).

C.11.2.5.3.2 Label in name (closed functionality)

Clause 11.2.5.3.2 is informative only and contains no requirements requiring test.

EN 301 549 clauseDetermination of conformance

11.2.5.4 Motion actuation

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

C.11.2.5.4 Motion actuation

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

11.3 Understandable
11.3.1 Readable
11.3.1.1 Language of software
EN 301 549 clauseDetermination of conformance

11.3.1.1.1 Language of software (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.10.

Table 11.10: Software success criterion: Language of software

The default human language of software can be programmatically determined.

NOTE 1: Where software platforms provide a "locale / language" setting, applications that use that setting and render their interface in that "locale / language" would comply with this success criterion. Applications that do not use the platform "locale / language" setting but instead use an accessibility-supported method for exposing the human language of the software would also comply with this success criterion. Applications implemented in technologies where assistive technologies cannot determine the human language and that do not support the platform "locale / language" setting may not be able to meet this success criterion in that locale / language.

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 3.1.1 Language of page, replacing "each web page" with "software" and with the addition of note 1 above.

C.11.3.1.1.1 Language of software (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.10.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.3.1.1.2 Language of software (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.14 (Spoken languages).

C.11.3.1.1.2 Language of software (closed functionality)

Type of assessment

Testing

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. The speech output is provided as non-visual access to closed functionality.

4. The speech output is not proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

5. The content is not generated externally and is under the control of the ICT vendor.

6. The displayed languages can be selected using non-visual access.

7. The user has not selected a speech language that is different from the language of the displayed content.

Procedure

1. Check that the speech output is in the same human language of the displayed content provided.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, 3, 4, 5, 6 or 7 is not met.

11.3.2 Predictable
EN 301 549 clauseDetermination of conformance

11.3.2.1 On focus

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 3.2.1 On Focus.

NOTE: Some compound documents and their user agents are designed to provide significantly different viewing and editing functionality depending upon what portion of the compound document is being interacted with (e.g. a presentation that contains an embedded spreadsheet, where the menus and toolbars of the user agent change depending upon whether the user is interacting with the presentation content, or the embedded spreadsheet content). If the user uses a mechanism other than putting focus on that portion of the compound document with which they mean to interact (e.g. by a menu choice or special keyboard gesture), any resulting change of context would not be subject to this success criterion because it was not caused by a change of focus.

C.11.3.2.1 On focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 3.2.1 On Focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 3.2.1 On Focus.

11.3.2.2 On input

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 3.2.2 On Input.

C.11.3.2.2 On input

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 3.2.2 On Input.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 3.2.2 On Input.

11.3.3 Input assistance
11.3.3.1 Error identification
EN 301 549 clauseDetermination of conformance

11.3.3.1.1 Error identification (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 3.3.1 Error Identification.

C.11.3.3.1.1 Error identification (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 3.3.1 Error Identification.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 3.3.1 Error Identification.

11.3.3.1.2 Error Identification (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.15 (Non-visual error identification).

C.11.3.3.1.2 Error Identification (closed functionality)

Type of assessment

Testing

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Speech output is provided as non-visual access to closed functionality.

4. An input error is automatically detected.

Procedure

1. Check that speech output identifies the item that is in error.

2. Check that the speech output describes the item that is in error.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or check 2 false

Not applicable: Pre-condition 1, 2,3 or 4 is not met.

11.3.3.2 Labels or instructions

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

C.11.3.3.2 Labels or instructions

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

11.3.3.3 Error suggestion

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

C.11.3.3.3 Error suggestion

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

11.3.3.4 Error prevention (legal, financial, data)

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.11.

Table 11.11: Software success criterion: Error prevention (legal, financial, data)

For software that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:

1. Reversible: Submissions are reversible.

2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.

3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

NOTE: This success criterion is identical to the WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data) replacing "web pages" with "software".

C.11.3.3.4 Error prevention (legal, financial, data)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.11.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.4 Robust
11.4.1 Compatible
11.4.1.1 Parsing
EN 301 549 clauseDetermination of conformance

11.4.1.1.1 Parsing (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the success criterion in Table 11.12.

Table 11.12: Software success criterion: Parsing

For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

NOTE 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.

NOTE 2: Markup is not always available to assistive technology or to user selectable user agents such as browsers. In such cases, conformance to this provision would have no impact on accessibility as it can for web content where it is exposed.

NOTE 3: Examples of markup that is separately exposed and available to assistive technologies and to user agents include but are not limited to: documents encoded in HTML, ODF, and OOXML. In these examples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may directly open the document, (b) by assistive technologies using DOM APIs of user agents for these document formats.

NOTE 4: Examples of markup used internally for persistence of the software user interface that are never exposed to assistive technology include but are not limited to: XUL, GladeXML, and FXML. In these examples assistive technology only interacts with the user interface of generated software.

NOTE 5: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.1 Parsing replacing "In content implemented using markup languages" with "For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent" with the addition of notes 2, 3 and 4 above.

C.11.4.1.1.1 Parsing (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.12.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.4.1.1.2 Parsing (closed functionality)

Not applicable.

NOTE: Where ICT is non-web software that provides a user interface which is closed to all assistive technology it shall not have to meet the "Parsing" success criterion in Table 11.10 because the intent of this success criterion is to provide consistency so that different user agents or assistive technologies will yield the same result.

C.11.4.1.1.2 Parsing (closed functionality)

Clause 11.4.1.1.2 contains no requirements requiring test.

11.4.1.2 Name, role, value
EN 301 549 clauseDetermination of conformance

11.4.1.2.1 Name, role, value (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the success criterion in Table 11.13.

Table 11.13: Software success criterion: Name, role, value

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification.

NOTE 2: For conforming to this success criterion, it is usually best practice for software user interfaces to use the accessibility services provided by platform software. These accessibility services enable interoperability between software user interfaces and both assistive technologies and accessibility features of software in standardised ways. Most platform accessibility services go beyond programmatic exposure of name and role, and programmatic setting of states, properties and values (and notification of same), and specify additional information that could or should be exposed and / or set (for instance, a list of the available actions for a given user interface component, and a means to programmatically execute one of the listed actions).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value replacing the original WCAG 2.1 note with: "This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification." and the addition of note 2 above.

C.11.4.1.2.1 Name, role, value (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.13.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.4.1.2.2 Name, role, value (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to all assistive technology it shall not have to meet the "Name, role, value" success criterion in Table 11.11 because this success criterion requires information in a programmatically determinable form.

C.11.4.1.2.2 Name, role, value (closed functionality)

Clause 11.4.1.2.2 contains no testable requirements.

11.4.1.3 Status messages
EN 301 549 clauseDetermination of conformance

11.4.1.3.1 Status messages (open functionality)

Where tWhere ICT is non-web software, it shall satisfy satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

C.11.4.1.3.1 Status messages (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 4.1.3 Status messages.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 4.1.3 Status messages.

11.4.1.3.2 Status messages (closed functionality)

Not applicable.

C.11.4.1.3.2 Status messages (closed functionality)

Clause 11.4.1.3.2 contains no testable requirements.

11.5 Interoperability with assistive technology
EN 301 549 clauseDetermination of conformance

11.5.1 Closed functionality

Where the closed functionality of software conforms to clause 5.1 (Closed functionality) it shall not be required to conform with clause 11.5.2 to clause 11.5.2.17.

C.11.5.1 Closed functionality

Type of assessment

Inspection

Pre-conditions

1. The software has closed functionality.

Procedure

1. Check that the closed functionality conforms to clause 5.1.

Result

If check 1 is true, the software is not required to conform to clauses 11.5.2 to 11.5.17

If check 1 is false the software is required to conform to clauses 11.5.2 to 11.5.17

Not applicable: Pre-condition 1 is not met.

11.5.2 Accessibility services
EN 301 549 clauseDetermination of conformance

11.5.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Platform software should support requirements 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality of software providing user interfaces when using platform services.

NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 3: User interface services that provide accessibility support by default are considered to be part of the services provided to conform to this clause (e.g. the service for creating a new user interface element provides role, state, boundary, name and description).

NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

NOTE 5: Within specific programming environments, the technical attributes associated with the user interface properties described in clauses 11.5.2.5 to 11.5.2.17 might have different names than those used within the clauses.

C.11.5.2.1 Platform accessibility service support for software that provides a user interface

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is platform software.

Procedure

1. Check that the platform software documentation includes information about platform services that may be used by software that provides a user interface to interoperate with assistive technology.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.2 Platform accessibility service support for assistive technologies

Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.

Platform software should support the requirements of clauses 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirement are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.

NOTE 2: The definition of platform in clause 3.1 applies to software that provides services to other software, including but not limited to, operating systems, web browsers, virtual machines.

NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 4: Typically these services belong to the same set of services that are described in clause 11.5.2.1.

NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

C.11.5.2.2 Platform accessibility service support for assistive technologies

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is platform software.

Procedure

1. Check that the platform software documentation includes information about platform accessibility services that enables assistive technology to interoperate with software that provides a user interface running on the platform software.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.3 Use of accessibility services

Where the software provides a user interface it shall use the applicable documented platform accessibility services. If the documented platform accessibility services do not allow the software to meet the applicable requirements of clauses 11.5.2.5 to 11.5.2.17, then software that provides a user interface shall use other documented services to interoperate with assistive technology.

NOTE: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

It is best practice to develop software using toolkits that automatically implement the underlying platform accessibility services.

C.11.5.2.3 Use of accessibility services

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

Procedure

1. Check that the software uses the applicable documented platform accessibility services.

2. Check that the software can meet the applicable requirements 11.5.2.5 to 11.5.2.17 whilst using the documented platform accessibility services.

3. Check that the software can meet requirements 11.5.2.5 to 11.5.2.17 whilst using the documented platform accessibility services and other documented services.

Result

Pass: Check 1 is true and check 2 or check 3 is true

Fail: Check 1 or check 3 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

NOTE 2: Assistive technology can also use other documented accessibility services.

C.11.5.2.4 Assistive technology

Type of assessment

Inspection

Pre-conditions

1. The ICT is assistive technology.

Procedure

1. Check that the assistive technology uses the documented platform accessibility services.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

C.11.5.2.5 Object information

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

Procedure

1. Check that the user interface element's role is programmatically determinable by assistive technologies.

2. Check that the user interface element's state(s) is programmatically determinable by assistive technologies.

3. Check that the user interface element's boundary is programmatically determinable by assistive technologies.

4. Check that the user interface element's name is programmatically determinable by assistive technologies.

5. Check that the user interface element's description is programmatically determinable by assistive technologies.

Result

Pass: Checks 1, 2, 3, 4 and 5 are true

Fail: Check 1 or 2 or 3 or 4 or 5 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

C.11.5.2.6 Row, column, and headers

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are data tables in the user interface.

Procedure

1. Select a data table in which the tests are to be performed.

2. Check that each cell's row is programmatically determinable by assistive technologies.

3. Check that each cell's column is programmatically determinable by assistive technologies.

4. Check that each cell's row header, if the row header exists, is programmatically determinable by assistive technologies.

5. Check that each cell's column header, if the column header exists, is programmatically determinable by assistive technologies.

Result

Pass: Checks 2, 3, 4 and 5 are true

Fail: Check 2 or 3 or 4 or 5 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.5.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

C.11.5.2.7 Values

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that can have values.

Procedure

1. Select a user interface element that can have a value.

2. Check that the current value is programmatically determinable by assistive technologies.

3. If the user interface element conveys information about a range of values, check that the minimum value is programmatically determinable by assistive technologies.

4. If the user interface element conveys information about a range of values, check that the maximum value is programmatically determinable by assistive technologies.

Result

Pass: Checks 2, 3 and 4 are true

Fail: Check 2 or 3 or 4 is false

Not applicable: Pre-condition 1 or 2 is not met

11.5.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.

C.11.5.2.8 Label relationships

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that are labels of other user interface elements.

Procedure

1. Obtain the information of each user interface element.

2. Check that the user interface element's information includes the relationship with the user interface element that is its label, if the current user interface element has a label, and that this relationship is programmatically determinable by assistive technologies.

3. Check that the user interface element's information includes the relationship with the user interface element that it is labelling, if the current user interface element is a label, and that this relationship is programmatically determinable by assistive technologies.

Result

Pass: Checks 2 or 3 are true

Fail: Check 2 and 3 are false

Not applicable: Pre-condition 1 or 2 is not met.

11.5.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

C.11.5.2.9 Parent-child relationships

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that are parents of other user interface elements in a hierarchical structure.

Procedure

1. For user interface elements that have a parent, check that the user interface element's information includes the relationship with the user interface element that is its parent.

2. Check that the user interface elements that are parents of the user interface element selected in check 1, include the relationship with the user interface elements that are its children in their information, and that this relationship is programmatically determinable by assistive technologies.

3. For user interface elements that are a parent of other user interface elements, check that the user interface element's information includes the relationship with the user interface elements that are its children, and that this relationship is programmatically determinable by assistive technologies.

4. Check that the user interface elements that are a child of the user interface element selected in check 3, include the relationship with the user interface elements that are its parents in their information, and that this relationship is programmatically determinable by assistive technologies.

Result

Pass: Checks 1 or 2 is true and check 3 or 4 is true

Fail: Checks 1 and 2 are false or check 3 and 4 are false

Not applicable: Pre-condition 1 or 2 is not met.

NOTE: For this requirement it is enough that one of the two directions of a parent-child relationship is programmatically determinable. This is the reason why the requirement checks are in pairs and why the requirement is met if one member of each pair is true.

11.5.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

C.11.5.2.10 Text

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There is text rendered to the screen.

Procedure

1. For instances of text rendered to the screen, check that the text's information includes its text content, and that this information is programmatically determinable by assistive technologies.

2. For instances of text rendered to the screen, check that the text's information includes its attributes, and that this information is programmatically determinable by assistive technologies.

3. For instances of text rendered to the screen, check that the text's information includes its boundary, and that this information is programmatically determinable by assistive technologies.

Result

Pass: Checks 1, 2 and 3 are true

Fail: Check 1 or 2 or 3 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.5.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

C.11.5.2.11 List of available actions

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that have actions that can be executed by the user.

Procedure

1. Check that the user interface element's information includes the list of actions that can be executed.

2. Check that this list is programmatically determinable by assistive technologies.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.5.2.12 Execution of available actions

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

C.11.5.2.12 Execution of available actions

Type of assessment

Inspection and testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that have actions that can be executed by the user.

3. The security requirements permit assistive technology to programmatically execute user actions.

Procedure

1. Check that the user interface element's information includes the list of actions that can be executed by assistive technologies according to 11.5.2.11.

2. Check that all the actions in the list can successfully be executed by assistive technologies.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.5.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

C.11.5.2.13 Tracking of focus and selection attributes

Type of assessment

Inspection and testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that enable text editing.

Procedure

1. Check that the user interface element's information includes mechanisms to track focus, text insertion point and selection attributes.

2. Check that this information is programmatically determinable by assistive technologies.

3. Activate those tracking mechanisms.

4. As a user, use the text editing functionality in the evaluated software product.

5. Check that the tracking of focus, text insertion point and selection attributes work.

Result

Pass: Checks 2 and 5 are true

Fail: Check 1 or 5 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.5.2.14 Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

C.11.5.2.14 Modification of focus and selection attributes

Type of assessment

Testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that can receive focus or that enable text editing.

3. The security requirements permit platform software to programmatically modify focus, text insertion point and selection attributes of user interface elements.

Procedure

1. For user interface elements that can receive focus and where the focus can be modified by a user without the use of assistive technology, check that the focus can be programmatically modified by assistive technologies.

2. For user interface elements that enable text editing by a user without the use of assistive technology, check that the position of the text insertion point can be programmatically modified by assistive technologies.

3. For user interface elements that enable text editing, check that the selection attributes can be programmatically modified by assistive technologies where they can be modified by user without the use of assistive technology.

Result

Pass: All checks are true

Fail: Any check is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.5.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

C.11.5.2.15 Change notification

Type of assessment

Inspection and testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

Procedure

1. Activate notifications of changes in the user interface elements.

2. Check that notifications about changes in object information (role, state, boundary, name and description) are sent to assistive technologies, if this information changes in the software user interface.

3. Check that notifications about changes in row, column and headers of data tables are sent to assistive technologies, if this information changes in the software.

4. Check that notifications about changes in values (current value, minimum value and maximum value) are sent, if this information changes in the software.

5. Check that notifications about changes in label relationships are sent to assistive technologies, if this information changes in the software.

6. Check that notifications about changes in parent-child relationships are sent to assistive technologies, if this information changes in the software.

7. Check notifications about changes in text (text contents, text attributes and the boundary of text rendered to the screen) are sent to assistive technologies, if this information changes in the software.

8. Check that notifications about changes in the list of available actions are sent to assistive technologies, if this information changes in the software.

9. Check that notifications about changes in focus, text insertion point and selection attributes are sent to assistive technologies, if this information changes in the software.

Result

Pass: Checks 2, 3, 4, 5, 6, 7, 8 and 9 are true

Fail: Check 2, 3, 4, 5, 6, 7, 8 or 9 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.16 Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

C.11.5.2.16 Modifications of states and properties

Type of assessment

Testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements whose state or properties can be modified by a user without the use of assistive technology.

3. The security requirements permit assistive technology to programmatically modify states and properties of user interface elements.

Procedure

1. Check that the state of user interface elements, whose state can be modified by a user without the use of assistive technology, can be programmatically modified by assistive technologies.

2. Check the properties of user interface elements, whose properties can be modified by a user without the use of assistive technologies, can be programmatically modified by assistive technologies.

Result

Pass: All checks are true

Fail: Any check is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

C.11.5.2.17 Modifications of values and text

Type of assessment

Testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements whose values or text can be modified by a user without the use of assistive technology.

3. The security requirements permit assistive technology to programmatically modify values and text of user interface elements.

Procedure

1. Check that the values of user interface elements, whose values can be modified by a user without the use of assistive technology, can be modified by assistive technologies using the input methods of the platform.

2. Check that the text of user interface elements, whose text can be modified by a user without the use of assistive technology, can be modified by assistive technologies using the input methods of the platform.

Result

Pass: all checks are true

Fail: any check is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.6 Documented accessibility usage
EN 301 549 clauseDetermination of conformance

11.6.1 User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

C.11.6.1 User control of accessibility features

Type of assessment

Testing

Pre-conditions

1. There are platform features that are defined in the platform documentation as accessibility features intended for users.

Procedure

1. Check that sufficient modes of operation exist where user control over platform features, that are defined in the platform documentation as accessibility features intended for users, is possible.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.6.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

C.11.6.2 No disruption of accessibility features

Type of assessment

Testing

Pre-conditions

1. There are platform features that are defined in the platform documentation as accessibility features.

Procedure

1. Check if software that provides a user interface disrupts normal operation of platform accessibility features.

2. Check if the disruption was specifically requested or confirmed by the user.

Result

Pass: Check 1 is false or both checks are true

Fail: Check 1 is true and check 2 is false

Not applicable: Pre-condition 1 is not met.

11.7 User preferences

Where software is not designed to be isolated from its platform, and provides a user interface, that user interface shall follow the values of the user preferences for platform settings for: units of measurement, colour, contrast, font type, font size, and focus cursor except where they are overridden by the user.

NOTE 1: Software that is isolated from its underlying platform has no access to user settings in the platform and thus cannot adhere to them.

NOTE 2: For web content, the underlying platform is the user agent.

NOTE 3: This does not preclude the software from having additional values for a setting as long as there is one mode where the application will follow the system settings even if more restricted.

C.11.7 User preferences

Type of assessment

Inspection and Testing

Pre-conditions

1. The software is software that provides a user interface.

Procedure

1. Check if the software provides sufficient modes of operation that uses user preferences for platform settings for colour, contrast, font type, font size, and focus cursor.

2. Check that the software documentation indicates that the software is designed to be isolated from its underlying platform.

Result

Pass: Check 1 is true or Check 1 is false and check 2 is true

Fail: Check 1 is false and check 2 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.8 Authoring tools
EN 301 549 clauseDetermination of conformance

11.8.1 Content technology

Authoring tools shall conform to clauses 11.8.2 to 11.8.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.

C.11.8.1 Content technology

Type of assessment

Inspection and Testing

Pre-conditions

1. The software is an authoring tool.

2. The output format of the authoring tool supports information required for accessibility.

Procedure

1. Check if the authoring tool conforms to 11.8.2 to 11.8.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

NOTE: Where the output format of the authoring tool does not support certain types of information required for accessibility, con with requirements that relate to that type of information is not required.

11.8.2 Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

NOTE: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

C.11.8.2 Accessible content creation

Type of assessment

Inspection and Testing

Pre-conditions

1. The software is an authoring tool.

Procedure

1. Check if the authoring tool has features that enable and guide the production of content that conforms to clauses 9 (Web) and 10 (Non-web documents).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.8.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

C.11.8.3 Preservation of accessibility information in transformations

Type of assessment

Inspection and Testing

Pre-conditions

1. The software is an authoring tool.

2. The authoring tool provides restructuring transformations or re-coding transformations.

Procedure

1. For a restructuring transformation, check if the accessibility information is preserved in the output.

2. For a restructuring transformation, check if the content technology supports accessibility information for the restructured form of the information.

3. For a re-coding transformation, check if the accessibility information is preserved in the output.

4. For a re-coding transformation, check if the accessibility information is supported by the technology of the re-coded output.

Result

Pass: Check 1 is true or checks 1 and 2 are false or check 3 is true or checks 3 and 4 are false

Fail: Check 1 is false and check 2 is true

Not applicable: Pre-condition 1 or 2 is not met.

11.8.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

NOTE: This does not preclude automated and semi-automated repair which is possible (and encouraged) for many types of content accessibility problems.

C.11.8.4 Repair assistance

Type of assessment

Inspection

Pre-conditions

1. The software is an authoring tool.

2. The accessibility checking functionality of the authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable.

Procedure

1. The authoring tool provides repair suggestions when content does not meet a requirement of clauses 9 or 10 (as applicable).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.8.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.

C.11.8.5 Templates

Type of assessment

Inspection

Pre-conditions

1. The software is an authoring tool.

2. The authoring tool provides templates.

Procedure

1. Check that the authoring tool provides at least one template that supports the creation of content that conforms to requirements of clauses 9 (Web content) or 10 (Documents) as applicable.

2. Check that at least one template identified in step 1 is available and is identified as conforming to clauses 9 or 10 (as applicable).

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-condition 1 or 2 is not met.

NOTE: The identification as conforming to the requirements of clauses 9 or 10 (as applicable) described in check 2 may be described in terms such as "Conformant to WCAG 2.1". Where the identification does not explicitly state that all of the requirements identified in clauses 9 or 10 (as appropriate) are covered, it may be necessary to use the template to create a web site or document and then test that web site or document according to the requirements of clauses 9 or 10 to provide full assurance that the template behaves as required.

12 Documentation and support services

12.1 Product documentation
EN 301 549 clauseDetermination of conformance

12.1.1 Accessibility and compatibility features

Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.

NOTE 1: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

NOTE 2: It is best practice to use WebSchemas/Accessibility 2.0 [i.38] to provide meta data on the accessibility of the ICT.

NOTE 3: The accessibility statement and help pages are both examples of the provision of product information.

C.12.1.1 Accessibility and compatibility features

Type of assessment

Inspection

Pre-conditions

1. Product documentation is supplied with the ICT.

Procedure

1. Check that product documentation provided with the ICT lists and explains how to use the accessibility and compatibility features of the ICT.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

1. a Web format that conforms to the requirements of clause 9, or

2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which is accessible.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

C.12.1.2 Accessible documentation

Type of assessment

Inspection

Pre-conditions

1. Product documentation in electronic format is supplied with the ICT.

Procedure

1. Check that product documentation in electronic format provided with the ICT conforms to the requirements of clauses 9 or 10 as appropriate.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

12.2 Support services
EN 301 549 clauseDetermination of conformance

12.2.1 General (informative)

ICT support services include, but are not limited to: help desks, call centres, technical support, relay services and training services.

C.12.2.1 General (informative)

Clause 12.2.1 is informative only and contains no requirements requiring test.

12.2.2 Information on accessibility and compatibility features

ICT support services shall provide information on the accessibility and compatibility features that are included in the product documentation.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

C.12.2.2 Information on accessibility and compatibility features

Type of assessment

Inspection

Pre-conditions

1. ICT support services are provided.

Procedure

1. Check that the ICT support services provide information on the accessibility and compatibility features that are included in the product documentation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

12.2.3 Effective communication

ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.

C.12.2.3 Effective communication

Type of assessment

Inspection

Pre-conditions

1. ICT support services are provided.

Procedure

1. Check that the ICT support services accommodate the communication needs of individuals with disabilities either directly or through a referral point.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

NOTE: The provision of any level of support for the communication needs of individuals with disabilities constitutes a pass of this requirement. Suppliers may wish to provide further information about the level of support that is provided to enable the adequacy and quality of the support to be judged.

12.2.4 Accessible documentation

Documentation provided by support services shall be made available in at least one of the following electronic formats:

1. a Web format that conforms to clause 9; or

2. a non-web format that conforms to clause 10.

NOTE 1: This does not preclude the possibility of also providing the documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

C.12.2.4 Accessible documentation

Type of assessment

Inspection

Pre-conditions

1. Documentation is provided by the ICT support services.

Procedure

1. Check that documentation in electronic format provided by the ICT support services conforms to the requirements of clauses 9 or 10 as appropriate.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13 ICT providing relay or emergency service access

13.1 Relay services requirements
EN 301 549 clauseDetermination of conformance

13.1.1 General (informative)

Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.

It is best practice to meet the applicable relay service requirements of ETSI ES 202 975 [i.5].

C.13.1.1 General (informative)

Clause 13.1.1 is informative only and contains no requirements requiring test.

13.1.2 Text relay services

Where ICT is intended to provide a text relay service, the text relay service shall enable text users and speech users to interact by providing conversion between the two modes of communication.

C.13.1.2 Text relay services

Type of assessment

Inspection

Pre-conditions

1. The service is a text relay service.

Procedure

1. Check that the service enables text users and speech users to interact by providing conversion between the two modes of communication.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13.1.3 Sign relay services

Where ICT is intended to provide a sign relay service, the sign relay service shall enable sign language users and speech users to interact by providing conversion between the two modes of communication.

NOTE: Sign relay services are also sometimes referred to as sign language relay services or video relay services.

C.13.1.3 Sign relay services

Type of assessment

Inspection

Pre-conditions

1. The service is a sign relay service.

Procedure

1. Check that the service enables sign language users and speech users to interact by providing conversion between the two modes of communication.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13.1.4 Lip-reading relay services

Where ICT is intended to provide a lip-reading relay service, the lip-reading service shall enable lip-readers and voice telephone users to interact by providing conversion between the two modes of communication.

C.13.1.4 Lip-reading relay services

Type of assessment

Inspection

Pre-conditions

1. The service is a lip-reading relay service.

Procedure

1. Check that the service enables lip-readers and voice telephone users to interact by providing conversion between the two modes of communication.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13.1.5 Captioned telephony services

Where ICT is intended to provide a captioned telephony service, the captioned telephony service shall assist a deaf or hard of hearing user in a spoken dialogue by providing text captions translating the incoming part of the conversation.

C.13.1.5 Captioned telephony services

Type of assessment

Inspection

Pre-conditions

1. The service is a captioned telephony service.

Procedure

1. Check that the service assists a deaf or hard of hearing user in a spoken dialogue by providing text captions translating the incoming part of the conversation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13.1.6 Speech to speech relay services

Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable speech or cognitively impaired telephone users and any other user to communicate by providing assistance between them.

C.13.1.6 Speech to speech relay services

Type of assessment

Inspection

Pre-conditions

1. The service is a speech to speech relay service.

Procedure

1. Check that the service enables enable speech or cognitively impaired telephone users and any other user to communicate by providing assistance between them.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13.2 Access to relay services

Where ICT systems support two-way communication, and the system is specified for use with relay services, access to those relay services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the relay service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access by persons with disabilities.

NOTE 2: The system may be specified as needing to work with relay services by, for example: procurers, regulators, or product specifications.

C.13.2 Access to relay services

Type of assessment

Inspection

Pre-conditions

1. The ICT system supports two-way communication.

2. A set of relay services for two-way communication is specified.

Procedure

1. Check that the system does not prevent access to those relay services for incoming and outgoing calls.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

13.3 Access to emergency services

Where ICT systems support two-way communication, and the system is specified for use with emergency services, access to those emergency services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the emergency service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access to the emergency service by persons with disabilities.

NOTE 2: The system may be specified as needing to work with emergency services by, for example: procurers, regulators, or product specifications.

C.13.3 Access to emergency services

Type of assessment

Inspection

Pre-conditions

1. The ICT system supports two-way communication.

2. A set of emergency services for two-way communication is specified.

Procedure

1. Check that the system does not prevent access to those emergency services for outgoing and incoming calls.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

Annex - Tables and figures (from EN 301 549)

The below tables and figures are copied from the EN 301 549 (2021) clauses without alteration. For each table or figure a link has been created to reference the associated clause, which doesn’t exist in the official EN 301 549 (2021) PDF as the official PDF includes these tables and figures inline with the clause.

Table 5.1: Relationship between maximum design viewing distance and minimum character height at 0,7 degrees minimum subtended angle

Maximum design viewing distanceMinimum character height

100 mm

1,2 mm

200 mm

2,4 mm

250 mm

3,1 mm

300 mm

3,7 mm

350 mm

4,3 mm

400 mm

4,9 mm

450 mm

5,5 mm

500 mm

6,1 mm

550 mm

6,7 mm

600 mm

7,3 mm

Figure 1: Relationship between minimum character height and maximum design viewing distance
Diagram illustrating the linear relationship of the text 5.1.4 Functionality closed to text enlargement

Related content:

Figure 2: Unobstructed forward reach
A diagram illustrating the content of the text 8.3.2.2 Unobstructed low forward reach. Person in a wheelchair reaching forward.

Related content:

Figure 3: Obstructed forward reach
A diagram illustrating the content of the text 8.3.2.3.3 Obstructed (< 635 mm) forward reach. Person in wheelchair reaching over a desk demonstrating unobstructed and obstructed high reach.

Related content:

Figure 4: Toe clearance
A diagram illustrating the content of the text 8.3.2.5 Toe clearance.

Related content:

Figure 5: Knee clearance
A diagram illustrating the content of the text 8.3.2.6 Knee clearance.

Related content:

Figure 6: Unobstructed side reach
A diagram illustrating the content of the text 8.3.3.2 Unobstructed low side reach. Person in a wheelchair reaching to the side.

Related content:

Figure 7: Obstructed high side reach
A diagram illustrating the content of the text 8.3.3.3.2 Obstructed (≤ 610 mm) side reach. Person in a wheelchair reaching to the side demonstrating unobstructed and obstructed high side reach.

Related content:

Figure 8: Vertical change in level
Diagram illustrating the content of the text 8.3.4.1 Change in level

Related content:

Figure 9: Bevelled change in level
Diagram illustrating the content of 8.3.4.1 Change in level

Related content:

Figure 10: Clear floor or ground space
Diagram illustrating the content of the text 8.3.4.2 Clear floor or ground space. Person in a wheelchair demonstrating minimum clearance.

Related content:

Figure 11: Manoeuvring Clearance in an Alcove, Forward Approach
A diagram illustrating the content of the text 8.3.4.3.2 Forward approach. Person in a wheelchair in an alcove.

Related content:

Figure 12: Manoeuvring Clearance in an Alcove, Parallel Approach
A diagram illustrating the content of the text 8.3.4.3.3 Parallel approach. person in a wheelchair in an alcove.

Related content:

Table 9.1: WCAG 2.1 Level AAA Success Criteria
No.GuidelineSuccess Criterion NumberSuccess Criteria Name
1Time-based media1.2.6Sign Language (Prerecorded)
2Time-based media1.2.7Extended Audio Description (Prerecorded)
3Time-based media1.2.8Media Alternative (Prerecorded)
4Time-based media1.2.9Audio-only (Live)
5Adaptable1.3.6Identify Purpose
6Distinguishable1.4.6Contrast (Enhanced)
7Distinguishable1.4.7Low or No Background Audio
8Distinguishable1.4.8Visual Presentation
9Distinguishable1.4.9Images of Text (No Exception)
10Keyboard Accessible2.1.3Keyboard (No Exception)
11Enough time2.2.3No Timing
12Enough time2.2.4Interruptions
13Enough time2.2.5Re-authenticating
14Enough time2.2.6Timeouts
15Seizures and physical reactions2.3.2Three Flashes
16Seizures and physical reactions2.3.3Animation form Interactions
17Navigable2.4.8Location
18Navigable2.4.9Link Purpose (Link Only)
19Navigable2.4.10Section Headings
20Input modalities2.5.5Target Size
21Input modalities2.5.6Concurrent Input Mechanisms
22Readable3.1.3Unusual Words
23Readable3.1.4Abbreviations
24Readable3.1.5Reading Level
25Readable3.1.6Pronunciation
26Predictable3.2.5Change on Request
27Input assistance3.3.5Help
28Input assistance3.3.6Error Prevention (All)

Annex – Chapter 14 Conformance

Conformance to the present document is achieved by meeting all the applicable requirements, these are clauses containing the word "shall". Those clauses containing the word "should" are recommendations and are not required for conformance.

All clauses except those in clause 12 are self-scoping. This means they are introduced with the phrase 'Where ICT'. A requirement is met when the pre-condition is true and the corresponding test (in Annex C) is passed. When one of the pre-conditions is false the requirement is not applicable. Consequently, the result of the tests in Annex C can be: not applicable, pass, fail, or (in exceptional circumstances) not testable.

ICT is often comprised of an assembly of two or more items of ICT. In some cases, two or more interoperable items of ICT may together meet more requirements of the standard when one item complements the functionality of the other and the sum together meets more of the accessibility requirements. However, combining two items of ICT, both of which fail to meet any particular requirement, will not lead to a combined ICT system that meets that requirement.

The present document does not prioritize requirements.

NOTE 1: Conformance with the accessibility requirements could be affected by subsequent implementation or maintenance.

NOTE 2: Sampling is frequently required on complex ICT when there are too many instances of the object to be tested. The present document cannot recommend specific ICT evaluation sampling techniques as these are context specific.

The inherent nature of certain situations makes it impossible to make reliable and definitive statements that accessibility requirements have been met. In those situations therefore, the requirements in the present document are not applicable:

NOTE 3: Even in the above situations, it is best practice to apply requirements in the present document wherever it is feasible and safe to do so.

Annex - References (from EN 301 549)

2.1 Normative references 

References are specific, identified by date of publication and/or edition number or version number. Only the cited version applies. 

Referenced documents which are not found to be publicly available in the expected location might be found at ETSI References in docbox. 

The following referenced documents are necessary for the application of the present document. 

[1] ETSI ETS 300 381 (Edition 1) (December 1994): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids". 

[2] ETSI ES 200 381-1 (V1.2.1) (October 2012): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids Part 1: Fixed-line speech terminals". 

[3] ETSI ES 200 381-2 (V1.1.1) (October 2012): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids; Part 2: Cellular speech terminals".

[4] W3C Recommendation (December 2008) /ISO/IEC 40500:2012: "Web Content Accessibility Guidelines (WCAG) 2.0". 

[5] W3C Proposed Recommendation (June 2018): "Web Content Accessibility Guidelines (WCAG) 2.1". 

2.2 Informative references 

References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. 

The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. 

[i.1] ANSI/IEEE C63.19 (2011): "American National Standard Method of Measurement of Compatibility between Wireless Communication Devices and Hearing Aids". 

[i.2] ANSI/TIA-4965: "Receive volume control requirements for digital and analogue wireline terminals". 

[i.3] European Commission M 376-EN: "Standardization Mandate to CEN, CENELEC and ETSI in support of European accessibility requirements for public procurement of products and services in the ICT domain". 

[i.4] ETSI EG 201 013: "Human Factors (HF); Definitions, abbreviations and symbols". 

[i.5] ETSI ES 202 975: "Human Factors (HF); Requirements for relay services". 

[i.6] ETSI ETS 300 767: "Human Factors (HF); Telephone Prepayment Cards; Tactile Identifier". 

[i.7] ETSI CEN/CENELEC/ETSI TR 101 550: "Documents relevant to EN 301 549 "Accessibility requirements suitable for public procurement of ICT products and services in Europe"". 

[i.8] ETSI CEN/CENELEC/ETSI TR 101 551: "Guidelines on the use of accessibility award criteria suitable for publicly procured ICT products and services in Europe". 

[i.9] ETSI TR 102 612: "Human Factors (HF); European accessibility requirements for public procurement of products and services in the ICT domain (European Commission Mandate M 376, Phase 1)". 

[i.10] ETSI TS 126 114: "Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction (3GPP TS 26.114)". 

[i.11] ETSI TS 122 173: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 (3GPP TS 22.173)". 

[i.12] ETSI TS 134 229: "Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification (3GPP TS 34.229)". 

[i.13] IETF RFC 4103 (2005): "RTP Payload for Text Conversation".

[i.14] ISO/IEC 17007:2009: "Conformity assessment - Guidance for drafting normative documents suitable for use for conformity assessment". 

[i.15] ISO 9241-11:2018:"Ergonomics of human-system interaction - Part 11: Usability: Definitions and concepts". 

[i.16] ISO 9241-110:2006: "Ergonomics of human-system interaction -- Part 110: Dialogue principles". 

[i.17] ISO 9241-171:2008: "Ergonomics of human-system interaction-Part 171: Guidance on software accessibility". 

[i.18] void

[i.19] ISO/IEC 13066-1:2011: "Information technology - Interoperability with assistive technology (AT) - Part 1: Requirements and recommendations for interoperability". 

[i.20] Recommendation ITU-T E.161 (2001): "Arrangement of digits, letters and symbols on telephones and other devices that can be used for gaining access to a telephone network". 

[i.21] Recommendation ITU-T G.722 (1988): "7 kHz audio-coding within 64 kbit/s". 

[i.22] Recommendation ITU-T G.722.2 (2003): "Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB)". 

[i.23] Recommendation ITU-T V.18 (2000): "Operational and interworking requirements for DCEs operating in the text telephone mode". 

[i.24] TIA-1083-A (2010): "Telecommunications; Telephone Terminal equipment; Handset magnetic measurement procedures and performance requirements". 

[i.25] Section 508 of the United States Rehabilitation Act of 1973, revised 2017. NOTE: Available at https://www.section508.gov/manage/laws-and-policies . 

[i.26] W3C Working Group Note 5 September 2013: "Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT)". 

[i.27] M 554 Commission Implementing Decision C(2017)2585 of 27.4.2017 on a standardisation request to the European standardisation organisations in support of Directive (EU) 2016/2102 of the European Parliament and of the Council on the accessibility of the websites and mobile applications of public sector bodies. 

[i.28] Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies. 

[i.29]ETSI/CEN/CENELEC EN 301 549 (V2.1.2) (August 2018): "Accessibility requirements for ICT products and services". 

[i.30] ETSI/CEN/CENELEC TR 101 552: "Guidance for the application of conformity assessment to accessibility requirements for public procurement of ICT products and services in Europe".

[i.31] ISO/IEC TS 20071-25:2017: "Information technology - User interface component accessibility - Part 25: Guidance on the audio presentation of text in videos, including captions, subtitles and other on-screen text".

[i.32] W3C Recommendation (September 2015): "Authoring Tool Accessibility Guidelines (ATAG) 2.0". NOTE: Available at http://www.w3.org/TR/ATAG20/.

[i.33] W3C Recommendation (September 2015): "User Agent Accessibility Guidelines (UAAG) 2.0". NOTE: Available at http://www.w3.org/TR/UAAG20/.

[i.34]ISO 21542:2011: "Building construction - Accessibility and usability of the built environment".

[i.35]ISO/IEC Guide 71:2014: "Guide for addressing accessibility in standards".

[i.36]Recommendation ITU-T T.140 (1988): "Protocol for multimedia application text conversation".

[i.37]Recommendation ITU-T F.703 (2000): "Multimedia conversational services".

[i.38] W3C WebSchemas/Accessibility 2.0. NOTE: Available at https://www.w3.org/wiki/WebSchemas/Accessibility.

[i.39]Void

[i.40]Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on public procurement and repealing Directive 2004/18/EC.

Annex – Definition of terms, symbols and abbreviations (from EN 301 549)

3.1 Terms

For the purposes of the present document, the terms given in ETSI EG 201 013 [i.4] and the following apply:

accessibility:

extent to which products, systems, services, environments and facilities can be used by people from a population with the widest range of user needs, characteristics and capabilities, to achieve identified goals in identified contexts of use (from ISO 9241-11:2018 [i.15])

  • NOTE 1: Context of use includes direct use or use supported by assistive technologies.
  • NOTE 2: The context in which the ICT is used may affect its overall accessibility. This context could include other products and services with which the ICT may interact.
access space:

space intended to be occupied by the person, including their Assistive Technology, while they are using the product

Assistive Listening Devices (ALDs):

devices that help separate the sounds, particularly speech, that a person wants to hear from background noise by bringing sound directly into the ear

  • NOTE: These are often found in meetings and public venues such as plays, concerts and places of worship. They can also be used at home with televisions and other products with auditory output.
Assistive Technology (AT):

equipment, product system, hardware, software or service that is used to increase, maintain or improve capabilities of individuals (from ISO/IEC Guide 71:2014 [i.35])

  • NOTE 1: Assistive technology is an umbrella term that is broader than assistive products.
  • NOTE 2: Assistive technology can include assistive services, and professional services needed for assessment, recommendation and provision.
  • NOTE 3: Where ICT does not support directly connected assistive technology, but which can be operated by a system connected over a network or other remote connection, such a separate system (with any included assistive technology) can also be considered assistive technology. This is an additional note, not included in ISO/IEC Guide 71:2014 [i.35].
audio description

additional audible narrative, interleaved with the dialogue, which describes the significant aspects of the visual content of audio-visual media that cannot be understood from the main soundtrack alone

  • NOTE: This is also variously described using terms such as "video description" or variants such as "descriptive narration".
authoring tool

software that can be used to create or modify content

  • NOTE 1: An authoring tool may be used by a single user or multiple users working collaboratively.
  • NOTE 2: An authoring tool may be a single stand-alone application or be comprised of collections of applications.
  • NOTE 3: An authoring tool may produce content that is intended for further modification or for use by end-users.
caption

synchronized visual and/or text alternative for both speech and non-speech audio information needed to understand the media content (after WCAG 2.1 [5])

  • NOTE: This is also variously described using terms such as "subtitles" or variants such as "subtitles for the deaf and hard-of-hearing".
closed functionality

functionality that is limited by characteristics that prevent a user from attaching, installing or using assistive technology

content

information and sensory experience to be communicated to the user by means of software, including code or mark-up that defines the content's structure, presentation, and interactions (after WCAG2ICT [i.26])

  • NOTE: Content occurs in three places: web pages, documents and software. When content occurs in a web page or a document, a user agent is needed in order to communicate the content's information and sensory experience to the user. When content occurs in software, a separate user agent is not needed in order to communicate the content's information and sensory experience to the user - the software itself performs that function.
context of use

combination of users, goals and tasks, resources, and environment. (from ISO 9241-11:2018 [i.15])

  • NOTE: The "environment" in a context of use includes the technical, physical, social, cultural and organizational environments.
document

logically distinct assembly of content (such as a file, set of files, or streamed media) that functions as a single entity rather than a collection, that is not part of software and that does not include its own user agent (after WCAG2ICT [i.26])

  • NOTE 1: A document always requires a user agent to present its content to the user.
  • NOTE 2: Letters, e-mail messages, spreadsheets, books, pictures, presentations, and movies are examples of documents.
  • NOTE 3: Software configuration and storage files such as databases and virus definitions, as well as computer instruction files such as source code, batch/script files, and firmware, are examples of files that function as part of software and thus are not examples of documents. If and where software retrieves "information and sensory experience to be communicated to the user" from such files, it is just another part of the content that occurs in software and is covered by WCAG2ICT like any other parts of the software. Where such files contain one or more embedded documents, the embedded documents remain documents under this definition.
  • NOTE 4: A collection of files zipped together into an archive, stored within a single virtual hard drive file, or stored in a single encrypted file system file, do not constitute a single document when so collected together. The software that archives/encrypts those files or manages the contents of the virtual hard drive does not function as a user agent for the individually collected files in that collection because that software is not providing a fully functioning presentation of that content.
  • NOTE 5: Anything that can present its own content without involving a user agent, such as a self-playing book, is not a document but is software.
  • NOTE 6: A single document may be composed of multiple files such as the video content and closed caption text. This fact is not usually apparent to the end-user consuming the document/content.
  • NOTE 7: An assembly of files that represented the video, audio, captions and timing files for a movie is an example of a document.
  • NOTE 8: A binder file used to bind together the various exhibits for a legal case would not be a document.
  • NOTE 9: Documents may contain sub-documents.
embedded:

directly included in the content that is downloaded to the user agent and its extension, and is intended to be used in rendering the web page

  • NOTE: Something that is downloaded using a mechanism on the web page but is not used in rendering the page is not "embedded" in the page.
ICT network:

technology and resources supporting the connection and operation of interconnected ICT

Information and Communication Technology (ICT):

technology, equipment, or interconnected system or subsystem of equipment for which the principal function is the creation, conversion, duplication, automatic acquisition, storage, analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission, reception, or broadcast of data or information

  • NOTE: Examples of ICT are web pages, electronic content, telecommunications products, computers and ancillary equipment, software including mobile applications, information kiosks and transaction machines, videos, IT services, and multifunction office machines which copy, scan, and fax documents.
mechanically operable part:

operable part that has a mechanical interface to activate, deactivate, or adjust the ICT

  • NOTE: Examples of mechanically operable parts include scanner covers, notebook docking stations and lids as well as physical switches and latches.
mechanism for private listening:

auditory output designed so that only the current user can receive the sound

  • NOTE: Personal headsets, directional speakers and audio hoods are examples of mechanisms for private listening.
non-text content:

content that is not a sequence of characters that can be programmatically determined or where the sequence is not expressing something in human language (after WCAG 2.1 [5])

non-web document:

document that is not a web page, not embedded in web pages nor used in the rendering or functioning of the page

non-web software:

software that is not a web page, not embedded in web pages nor used in the rendering or functioning of the page

open functionality

functionality that supports access by assistive technology

  • NOTE: This is the opposite of Closed Functionality.
operable part

component of ICT used to activate, deactivate, or adjust the ICT

  • NOTE 1: Operable parts can be provided in either hardware (see mechanically operable parts, above) or software. An on-screen button is an example of an operable part provided by software.
  • NOTE 2: Operable parts do not include parts involved only in maintenance or repair or other actions that are not expected of a typical user if the product is not malfunctioning. These actions include: clearing paper jams internal to the machine, replacing items or parts internal to the machine that may expose the end user to sharp or hot surfaces, replacing or repairing items designated by manufacturers as service or maintenance items in user documentation.
platform software

collection of software components that runs on an underlying software or hardware layer, and that provides a set of software services to other software components that allows those applications to be isolated from the underlying software or hardware layer (after ISO/IEC 13066-1 [i.19])

  • NOTE: A particular software component might play the role of a platform in some situations and a client in others.
programmatically determinable

able to be read by software from developer-supplied data in a way that other software, including assistive technologies, can extract and present this information to users in different modalities

  • NOTE: WCAG 2.1 uses "determined" where this definition uses "able to be read" (to avoid ambiguity with the word "determined").
Real-Time Text (RTT):

form of a text conversation in point to point situations or in multipoint conferencing where the text being entered is sent in such a way that the communication is perceived by the user as being continuous

  • NOTE 1: Users will perceive communication as continuous if the delay between text being created by the sender and received by the recipient is less than 500 ms. However, the actual delay will be dependent on the communication network.
  • NOTE 2: The creation of text will differ between systems where text is entered on a word-by-word basis (e.g. speech to text and predictive-text based systems) and systems where each character is separately generated (e.g. typing on a physical keyboard).
satisfies a success criterion

success criterion does not evaluate to "false" when applied to the ICT (after WCAG 2.1 [5])

single user connection:

connection that consists of sound, RTT or video (or a combination of two or three of those media) that is established by a single user action

  • NOTE: Even though the different media may travel over different channels, and more than one piece of hardware may be involved, it appears to the user like a single connection, and is treated by any intermediate technologies (e.g. network, auto-reception) as a single connection for purposes such as transfer.
spoken captions/subtitles audio captions/subtitles:

captions/subtitles that are voiced over the audiovisual content (from ISO/IEC TS 20071-25 [i.31])

stationary ICT:

ICT that stands on the floor, or is mounted on a wall or other immovable structure, and is not intended to be moved by its user

  • NOTE 1: Typically, stationary ICT rests on the ground (such as an information kiosk) or is installed in a wall (such as a machine that dispenses cash or performs other banking services).
  • NOTE 2: A manufacturer cannot control the height of ICT that is put on a table by someone else, but they are able to control the reach dimensions of self-contained ICT that rests on the ground and can specify the heights for installation in walls.
terminal

combination of hardware and/or software with which the end user directly interacts and that provides the user interface

  • NOTE 1: The hardware may consist of more than one device working together e.g. a mobile device and a computer.
  • NOTE 2: For some systems, the software that provides the user interface may reside on more than one device such as a telephone and a server.
turn-taking:

type of organization in conversation and discourse where participants speak one at a time in alternating turns

user agent

software that retrieves and presents content for users (after WCAG 2.1 [5])

  • NOTE 1: Software that only displays the content contained within it is treated as software and not considered to be a user agent.
  • NOTE 2: An example of software that is not a user agent is a calculator application that does not retrieve the calculations from outside the software to present it to a user. In this case, the calculator software is not a user agent, it is simply software with a user interface.
  • NOTE 3: Software that only shows a preview of content such as a thumbnail or other non-fully functioning presentation is not providing user agent functionality.
user interface

all components of an interactive system (software or hardware) that provide information and/or controls for the user to accomplish specific tasks with the interactive system (from ISO 9241-110 [i.16])

user interface element

entity of the user interface that is presented to the user by the software (after ISO 9241-171 [i.17])

  • NOTE 1: This term is also known as "user interface component".
  • NOTE 2: User-interface elements can be interactive or not.
web content

content that belongs to a web page, and that is used in the rendering or that is intended to be used in the rendering of the web page

web page

non-embedted resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent (after WCAG 2.1 [5])

3.2 Symbols

void

3.3 Abbreviations

For the purposes of the present document, the following abbreviations apply:

ANSI
American National Standards Institute
AT
Assistive Technology
ATAG
Authoring Tool Accessibility Guidelines (of W3C)
CEN
Comité Européen de Normalisation (no English Term)
CSS
Cascading Style Sheets
DOM
Document Object Model
EU
European Union
FPS
Frames Per Second
FXML
XML-based user interface markup language
HTML
HyperText Markup Language
HTTP
HyperText Transfer Protocol
ICT
Information and Communication Technology
IETF
Internet Engineering Task Force
IMS
IP Multimedia System
IP
Internet Protocol
JWG
Joint Working Group (of CEN/CENELEC/ETSI)
ODF
Open Document Format
OOXML
Office Open eXtensible Markup Language
PSTN
Public Switched Telephone Network
RFC
Request For Comment
RTT
Real-Time Text
SIP
Session Initiation Protocol
URI
Uniform Resource Identifier
USB
Universal Serial Bus
VoIP
Voice over IP
W3C
World Wide Web Consortium
WCAG
Web Content Accessibility Guidelines (of W3C)
XML
eXtensible Markup Language
XUL
XML User interface Language
ISO
International Organization for Standardization
ITU-T
International Telecommunication Union - Telecommunication standardization sector
LED
Light Emitting Device
QVGA
Quarter Video Graphics Array
UAAG
User Agent Accessibility Guidelines (of W3C)
VGA
Video Graphics Array
WAI
Web Accessibility Initiative
WLAN
Wireless Local Access Network

Annex - Practical guidance for accessible non-web documentation

In WCAG “success criteria” are all technology agnostic. The requirements for non-web documents are based on the WCAG 2.1 level AA requirements, which means all level A and AA criteria relevant to documents must be met.

The W3C publishes sufficient techniques to meet WCAG success criteria, including techniques for non-web document formats such as PDF. Using a given technique is considered “sufficient” to meet the criteria relevant to the technique, but you can also meet the criteria in other ways.

Shared Services Canada has created a set of guides for producing accessible documents in Microsoft Office:

Various software vendors and organizations offer supplementary material that provides instructions for making documents accessible:

NOTE: Following the guidance given in the links above does not guarantee compliance with WCAG 2.1. Links are provided for reference only.

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Information and Communication Technology (ICT) Accessibility Requirements

This page is to share some of the work that Shared Services Canada (SSC) has done for the piloting of the EN 301 549 (2021) harmonized Information and Communications Technology (ICT) accessibility standards. This is not a full copy / paste / translation of either the EN 301 549 (2021) or Web Content Accessibility Guidelines (WCAG) 2.1.

Information and Communication Technology (ICT) Accessibility Requirements ( Word, 88 KB)

What is ICT?

Information and Communications Technology (ICT) includes hardware, software, voice communication, video capabilities and digital content (including web and non-web-based information).

What is ICT accessibility and why is it important?

"ICT accessibility ensures that people with and without disabilities can access the same information, perform the same tasks, and receive the same services using information technology. It is the digital equivalent to accessibility in the physical environment —the curb cuts, ramps, railings, etc., of the digital age. While ICT accessibility can provide usability benefits to everyone who uses ICT, it is a vital necessity to many people with disabilities." - NASCIO - Accessibility in IT Procurement

About this document and Copyright Notice

This document reproduces relevant ICT accessibility requirements from the EN 301 549 v3.2.1 (2021-03) Harmonised European Standard – Accessibility requirements for ICT products and services (© used under license from European Telecommunications Standards Institute 2021. © Comité Européen de Normalisation 2021. © Comité Européen de Normalisation Électrotechnique 2021. All rights reserved.), which includes the Web Content Accessibility Guidelines (WCAG) 2.1 level AA. Note, where the EN 301 549 references VOID criteria, for the purposes of this document, we have excluded the technical explanation as to why the WCAG criteria no longer apply. Refer to the EN 301 549 (hyperlink below) for this information if necessary.

Intellectual Property Rights (IPRs) essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https://ipr.etsi.org/). Please visit ETSI IPR database to search for any IPRs.

At first glance, some requirements may appear to be unrelated to this product or service. They have been included for consideration since the full feature set of a Vendor’s product or service may not be known. For example, a video may be embedded into product documentation, so accessibility requirements for video and audio may become relevant.

Appendices include definitions, references, and practical guidance on creating accessible documentation.

Internal to this document references are included but not always linked (footnotes or otherwise).

Sources used to compile this document

On this page:

You can find here partial information and present it in two languages for informational purposes. Specific procurements will have the appropriate ICT requirements within the tender package.

Part A - Functional performance statements

These are explanatory (non-testable) statements that introduce the core aspects that the offered product or service must provide to be considered accessible.

4.2.1. Usage without vision: Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that does not require vision. This is essential for users without vision and benefits many more users in different situations.

4.2.2. Usage with limited vision: Where ICT provides visual modes of operation, the ICT provides features that enable users to make better use of their limited vision. This is essential for users with limited vision and benefits many more users in different situations.

4.2.3. Usage without perception of colour: Where ICT provides visual modes of operation, the ICT provides a visual mode of operation that does not require user perception of colour. This is essential for users with limited colour perception and benefits many more users in different situations.

4.2.4. Usage without hearing: Where ICT provides auditory modes of operation, the ICT provides at least one mode of operation that does not require hearing. This is essential for users without hearing and benefits many more users in different situations.

4.2.5. Usage with limited hearing: Where ICT provides auditory modes of operation, the ICT provides enhanced audio features. This is essential for users with limited hearing and benefits many more users in different situations.

4.2.6. Usage with no or limited vocal capability: Where ICT requires vocal input from users, the ICT provides at least one mode of operation that does not require them to generate vocal output. This is essential users with no or limited vocal capability and benefits many more users in different situations.

4.2.7. Usage with limited manipulation or strength: Where ICT requires manual actions, the ICT provides features that enable users to make use of the ICT through alternative actions not requiring manipulation, simultaneous action or hand strength. This is essential for users with limited manipulation or strength and benefits many more users in different situations.

4.2.8. Usage with limited reach: : Where ICT products are free-standing or installed, all the elements required for operation will need to be within reach of all users. This is essential for users with limited reach and benefits many more users in different situations.

4.2.9. Minimize photosensitive seizure triggers: Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that minimizes the potential for triggering photosensitive seizures. This is essential for users with photosensitive seizure triggers.

4.2.10. Usage with limited cognition, language or learning: The ICT provides features and/or presentation that makes it simpler and easier to understand, operate and use. This is essential for users with limited cognition, language or learning, and benefits many more users in different situations.

4.2.11. privacy: Where ICT provides features for accessibility, the ICT maintains the privacy of users of these features at the same level as other users.

Part B - Functional accessibility requirements

Explanation of the table columns

Scope

The following Functional Accessibility Requirements are applicable to the Functional Performance Statements in Part A. If a solution meets all of these it is considered to have met the Functional Performance Statements and is therefore deemed to conform with EN 301 549 v3.2.1.

Clauses deemed relevant to this ICT

Clauses deemed relevant to this ICT

  • 5
  • 5.1
  • 5.1.1
  • 5.1.2
  • 5.1.2.1
  • 5.1.2.2
  • 5.1.3
  • 5.1.3.1
  • 5.1.3.2
  • 5.1.3.3
  • 5.1.3.4
  • 5.1.3.5
  • 5.1.3.6
  • 5.1.3.7
  • 5.1.3.8
  • 5.1.3.9
  • 5.1.3.10
  • 5.1.3.11
  • 5.1.3.12
  • 5.1.3.13
  • 5.1.3.14
  • 5.1.3.15
  • 5.1.3.16
  • 5.1.4
  • 5.1.5
  • 5.1.6
  • 5.1.6.1
  • 5.1.6.2
  • 5.1.7
  • 5.2
  • 5.3
  • 5.4
  • 5.5
  • 5.5.1
  • 5.5.2
  • 5.6
  • 5.6.1
  • 5.6.2
  • 5.7
  • 5.8
  • 5.9
  • 6
  • 6.1
  • 6.2
  • 6.2.1
  • 6.2.1.1
  • 6.2.1.2
  • 6.2.2
  • 6.2.2.1
  • 6.2.2.2
  • 6.2.2.3
  • 6.2.2.4
  • 6.2.3
  • 6.2.4
  • 6.5.5
  • 6.5.6
  • 6.6
  • 7
  • 7.1
  • 7.1.1
  • 7.1.2
  • 7.1.3
  • 7.1.4
  • 7.1.5
  • 7.2
  • 7.2.1
  • 7.2.2
  • 7.2.3
  • 7.3
  • 8
  • 8.1
  • 8.1.1
  • 8.1.2
  • 8.1.3
  • 8.2
  • 8.2.1
  • 8.2.1.1
  • 8.2.1.2
  • 8.2.2
  • 8.2.2.1
  • 8.2.2.2
  • 8.3
  • 8.3.0
  • 8.3.1
  • 8.3.2
  • 8.3.2.1
  • 8.3.2.2
  • 8.3.2.3
  • 8.3.2.3.1
  • 8.3.2.3.2
  • 8.3.2.3.3
  • 8.3.2.4
  • 8.3.2.5
  • 8.3.2.6
  • 8.3.3
  • 8.3.3.1
  • 8.3.3.2
  • 8.3.3.3
  • 8.3.3.3.1
  • 8.3.3.3.2
  • 8.3.4
  • 8.3.4.1
  • 8.3.4.2
  • 8.3.4.3
  • 8.3.4.3.1
  • 8.3.4.3.2
  • 8.3.4.3.3
  • 8.3.5
  • 8.3.6
  • 8.4
  • 8.4.1
  • 8.4.2
  • 8.3.4.3
  • 8.3.4.3.1
  • 8.3.4.3.2
  • 8.3.4.3.3
  • 8.3.5
  • 8.3.6
  • 8.4
  • 8.4.1
  • 8.4.2
  • 8.4.2.1
  • 8.4.2.2
  • 8.4.3
  • 8.5
  • 9
  • 9.0
  • 9.1
  • 9.1.1
  • 9.1.1.1
  • 9.1.2
  • 9.1.2.1
  • 9.1.2.2
  • 9.1.2.3
  • 9.1.2.4
  • 9.1.2.5
  • 9.1.3
  • 9.1.3.1
  • 9.1.3.2
  • 9.1.3.3
  • 9.1.3.4
  • 9.1.3.5
  • 9.1.4
  • 9.1.4.1
  • 9.1.4.2
  • 9.1.4.3
  • 9.1.4.4
  • 9.1.4.5
  • 9.1.4.10
  • 9.1.4.11
  • 9.1.4.12
  • 9.1.4.13
  • 9.2
  • 9.2.1
  • 9.2.1.1
  • 9.2.1.2
  • 9.2.1.4
  • 9.2.2
  • 9.2.2.1
  • 9.2.2.2
  • 9.2.3
  • 9.2.3.1
  • 9.2.4
  • 9.2.4.1
  • 9.2.4.2
  • 9.2.4.3
  • 9.2.4.4
  • 9.2.4.5
  • 9.2.4.6
  • 9.2.4.7
  • 9.2.5
  • 9.2.5.1
  • 9.2.5.2
  • 9.2.5.3
  • 9.2.5.4
  • 9.3
  • 9.3.1
  • 9.3.1.1
  • 9.3.1.2
  • 9.3.2
  • 9.3.2.1
  • 9.3.2.2
  • 9.3.2.3
  • 9.3.2.4
  • 9.3.3
  • 9.3.3.1
  • 9.3.3.2
  • 9.3.3.3
  • 9.3.3.4
  • 9.4
  • 9.4.1
  • 9.4.1.1
  • 9.4.1.2
  • 9.4.1.3
  • 9.5
  • 9.6
  • 10
  • 10.0
  • 10.1
  • 10.1.1
  • 10.1.1.1
  • 10.1.2
  • 10.1.2.1
  • 10.1.2.2
  • 10.1.2.3
  • 10.1.2.4
  • 10.1.2.5
  • 10.1.3
  • 10.1.3.1
  • 10.1.3.2
  • 10.1.3.3
  • 10.1.3.4
  • 10.1.3.5
  • 10.1.4
  • 10.1.4.1
  • 10.1.4.2
  • 10.1.4.3
  • 10.1.4.4
  • 10.1.4.5
  • 10.1.4.10
  • 10.1.4.11
  • 10.1.4.12
  • 10.1.4.13
  • 10.2
  • 10.2.1
  • 10.2.1.1
  • 10.2.1.2
  • 10.2.1.4
  • 10.2.2
  • 10.2.2.1
  • 10.2.2.2
  • 10.2.3
  • 10.2.3.1
  • 10.2.4
  • 10.2.4.2
  • 10.2.4.3
  • 10.2.4.4
  • 10.2.4.6
  • 10.2.4.7
  • 10.2.5
  • 10.2.5.1
  • 10.2.5.2
  • 10.2.5.3
  • 10.2.5.4
  • 10.3
  • 10.3.1
  • 10.3.1.1
  • 10.3.1.2
  • 10.3.2
  • 10.3.2.1
  • 10.3.2.2
  • 10.3.3
  • 10.3.3.1
  • 10.3.3.2
  • 10.3.3.3
  • 10.3.3.4
  • 10.4
  • 10.4.1
  • 10.4.1.1
  • 10.4.1.2
  • 10.4.1.3
  • 10.5
  • 10.6
  • 11
  • 11.0
  • 11.1
  • 11.1.1
  • 11.1.1.1
  • 11.1.1.1.1
  • 11.1.1.1.2
  • 11.1.2
  • 11.1.2.1
  • 11.1.2.1.1
  • 11.1.2.1.2
  • 11.1.2.1.2.1
  • 11.1.2.1.2.2
  • 11.1.2.2
  • 11.1.2.3
  • 11.1.2.3.1
  • 11.1.2.3.2
  • 11.1.2.4
  • 11.1.2.5
  • 11.1.3
  • 11.1.3.1
  • 11.1.3.1.1
  • 11.1.3.1.2
  • 11.1.3.2
  • 11.1.3.2.1
  • 11.1.3.2.2
  • 11.1.3.3
  • 11.1.3.4
  • 11.1.3.5
  • 11.1.3.5.1
  • 11.1.3.5.2
  • 11.1.4.1
  • 11.1.4.2
  • 11.1.4.3
  • 11.1.4.4
  • 11.1.4.4.1
  • 11.1.4.4.2
  • 11.1.4.5
  • 11.1.4.5.1
  • 11.1.4.5.2
  • 11.1.4.10
  • 11.1.4.11
  • 11.1.4.12
  • 11.1.4.13
  • 11.2
  • 11.2.1
  • 11.2.1.1
  • 11.2.1.1.1
  • 11.2.1.1.2
  • 11.2.1.2
  • 11.2.1.4
  • 11.2.1.4.1
  • 11.2.1.4.2
  • 11.2.2
  • 11.2.2.1
  • 11.2.2.2
  • 11.2.3
  • 11.2.3.1
  • 11.2.4
  • 11.2.4.3
  • 11.2.4.4
  • 11.2.4.6
  • 11.2.4.7
  • 11.2.5
  • 11.2.5.1
  • 11.2.5.2
  • 11.2.5.3
  • 11.2.5.3.1
  • 11.2.5.3.2
  • 11.2.5.4
  • 11.3
  • 11.3.1
  • 11.3.1.1
  • 11.3.1.1.1
  • 11.3.1.1.2
  • 11.3.2
  • 11.3.2.1
  • 11.3.2.2
  • 11.3.3
  • 11.3.3.1
  • 11.3.3.1.1
  • 11.3.3.1.2
  • 11.3.3.2
  • 11.3.3.3
  • 11.3.3.4
  • 11.4
  • 11.4.1
  • 11.4.1.1
  • 11.4.1.1.1
  • 11.4.1.1.2
  • 11.4.1.2
  • 11.4.1.2.1
  • 11.4.1.2.2
  • 11.4.1.3
  • 11.4.1.3.1
  • 11.4.1.3.2
  • 11.5
  • 11.5.1
  • 11.5.2
  • 11.5.2.1
  • 11.5.2.2
  • 11.5.2.3
  • 11.5.2.4
  • 11.5.2.5
  • 11.5.2.6
  • 11.5.2.7
  • 11.5.2.8
  • 11.5.2.9
  • 11.5.2.10
  • 11.5.2.11
  • 11.5.2.12
  • 11.5.2.13
  • 11.5.2.14
  • 11.5.2.15
  • 11.5.2.16
  • 11.5.2.17
  • 11.6
  • 11.6.1
  • 11.6.2
  • 11.7
  • 11.8
  • 11.8.1
  • 11.8.2
  • 11.8.3
  • 11.8.4
  • 11.8.5
  • 12
  • 12.1
  • 12.1.1
  • 12.1.2
  • 12.2
  • 12.2.1
  • 12.2.2
  • 12.2.3
  • 12.2.4
  • 13
  • 13.1
  • 13.1.1
  • 13.1.2
  • 13.1.3
  • 13.1.4
  • 13.1.5
  • 13.1.6
  • 13.2
  • 13.3

Found in this section

5 Generic requirements

5.1 Closed functionality
EN 301 549 clauseDetermination of conformance

5.1.1 Introduction (informative)

ICT has closed functionality for many reasons, including design or policy. Some of the functionality of products can be closed because the product is self-contained and users are precluded from adding peripherals or software in order to access that functionality.

ICT may have closed functionality in practice even though the ICT was not designed, developed or supplied to be closed.

Computers that do not allow end-users to adjust settings or install software are functionally closed.

C.5.1.1 Introduction (informative)

Clause 5.1.1 is informative and does not contain requirements that require testing.

5.1.2 General
EN 301 549 clauseDetermination of conformance

5.1.2.1 Closed functionality

Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.

NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to the requirements of clause 5.1.

NOTE 2: The requirements within this clause replace those in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. This may be because they relate to compatibility with assistive technology or to the ability for the user to adjust system accessibility settings in products with closed functionality (e.g. products that prevent access to the system settings control panel).

C.5.1.2.1 Closed functionality

See clauses C.5.2 to C.13, as applicable.

5.1.2.2 Assistive technology

Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.6 as applicable. Personal headsets and induction loops shall not be classed as assistive technology for the purpose of this clause.

C.5.1.2.2 Assistive technology

Type of assessment

Testing

Pre-conditions

1. The ICT has closed functionality.

Procedure

1. Determine the closed functions of the ICT.

2. Check that the tests C.5.1.3 to C.5.1.6 can be carried out without the attachment or installation of any assistive technology except personal headsets or inductive loops.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1 is not met

5.1.3 Non-visual access
EN 301 549 clauseDetermination of conformance

5.1.3.1 Audio output of visual information

Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.

NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form.

NOTE 2: The visual information needed to enable use of some functions may include operating instructions and orientation, transaction prompts, user input verification, error messages and non-text content.

C.5.1.3.1 Audio output of visual information

Type of assessment

Testing

Pre-conditions

1. Visual information is needed to enable the use of those functions of the ICT that are closed to assistive technology for screen reading.

Procedure

1. Determine the functions of the ICT closed to screen reading.

2. Check that they are all operable using non-visual access.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1 is not met.

5.1.3.2 Auditory output delivery including speech

Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:

1. either directly by a mechanism included in or provided with the ICT; or

2. by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision.

NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in handset/headset, or other industry standard coupled peripheral.

NOTE 2: An industry standard connection could be a wireless connection.

NOTE 3: Some users may benefit from the provision of an inductive loop.

C.5.1.3.2 Auditory output delivery including speech

Type of assessment

Inspection

Pre-conditions

1. Auditory output is provided as non-visual access to closed functionality.

Procedure

1. Check that the auditory output is delivered by a mechanism included in or provided with the ICT.

2. Check that the auditory output is delivered by a personal headset that can be connected through a 3,5 mm audio jack or an industry standard connection without requiring the use of vision.

Result

Pass: Check 1 or 2 is true

Fail: Checks 1 and 2 are false

Not applicable: Pre-condition 1 is not met

5.1.3.3 Auditory output correlation

Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

C.5.1.3.3 Auditory output correlation

Clause 5.1.3.3 is informative only and contains no requirements requiring test.

5.1.3.4 Speech output user control

Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.

NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.

NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to start from the beginning.

C.5.1.3.4 Speech output user control

Type of assessment

Inspection

Pre-condition

1. Speech output is provided as non-visual access to closed functionality.

Procedure

1. Check that the speech output is capable of being interrupted when requested by the user.

2. Check that the speech output is capable of being repeated when requested by the user.

Result

Pass: All checks are true

Fail: Any check is false

Not applicable: Pre-condition 1 is not met

5.1.3.5 Speech output automatic interruption

Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.

NOTE: Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT may need to block all user action so that speech is not interrupted.

C.5.1.3.5 Speech output automatic interruption

Type of assessment

Inspection

Pre-conditions

1. Speech output is provided as non-visual access to closed functionality.

Procedure

1. Determine the closed functions of the ICT.

2. Check that the speech output for each single function is interrupted on a user action.

3. Check that the speech output for each single function is interrupted when new speech output begins.

Result

Pass: Check 2 and 3 are true

Fail: Check 2 or 3 are false

Not applicable: Pre-condition 1 is not met

5.1.3.6 Speech output for non-text content

Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1 Non-text content.

C.5.1.3.6 Speech output for non-text content

Type of assessment

Testing

Pre-conditions

1. Non-text content is presented to users via speech output.

Procedure

1. Check that speech output is provided as an alternative for non-text content.

2. Check that the non-text content is not pure decoration.

3. Check that the non-text content is not used only for visual formatting.

4. Check that the speech output follows the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1 Non-text content.

Result

Pass: Checks 1 and 2 and 3 and 4 are true; or 1 and 2 are false; or 1 and 3 are false

Fail: Checks 1 is true and 2 false; or 1 is true and 3 false; or 1 and 2 and 3 are true and 4 is false

Not applicable: Pre-condition 1 is not met

5.1.3.7 Speech output for video information

Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content.

NOTE: This speech output can take the form of an audio description or an auditory transcript of the video content.

C.5.1.3.7 Speech output for video information

Type of assessment

Testing

Pre-conditions

1. Pre-recorded video content is needed to enable the use of closed functions of ICT.

2. Speech output is provided as non-visual access to non-text content displayed on closed functionality.

Procedure

1. Check that the speech output presents equivalent information for the pre-recorded video content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

C.5.1.3.8 Masked entry

Type of assessment

Testing

Pre-conditions

1. Auditory output is provided as non-visual access to closed functionality.

2. The characters displayed are masking characters.

3. Any option to allow non-private auditory output has not been activated.

Procedure

1. Check that the auditory output is not a spoken version of the characters entered.

2. Check that the auditory output is known to be delivered only to a mechanism for private listening.

Result

Pass: Any check is true

Fail: All checks are false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.9 Private access to personal data

Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.

NOTE 1: This requirement does not apply in cases where data is not defined as being private according to the applicable privacy policy or where there is no applicable privacy policy.

NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

C.5.1.3.9 Private access to personal data

Type of assessment

Testing

Pre-conditions

1. Auditory output is provided as non-visual access to closed functionality.

2. The output contains data.

3. There is an applicable privacy policy which considers that data to be private.

Procedure

1. Check that the auditory output is only delivered through a mechanism for private listening.

2. Check that the mechanism for private listening can be connected without requiring the use of vision.

3. Check that the auditory output is delivered through all user-selectable mechanisms.

Result

Pass: Checks 1 and 2 or 3 are true

Fail: Checks 1 or 2 and 3 are false

Not applicable: Pre-conditions 1 or 3 are not met

5.1.3.10 Non-interfering audio output

Where auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.

C.5.1.3.10 Non-interfering audio output

Type of assessment

Testing

Pre-conditions

1. Auditory output is provided as non-visual access to closed functionality.

2. The ICT automatically plays interfering audible output.

Procedure

1. Check that the interfering audible output lasts no longer than three seconds.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.11 Private listening volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.

C.5.1.3.11 Private listening volume

Type of assessment

Inspection

Pre-conditions

1. The auditory output is provided as non-visual access to closed functionality.

2. The auditory output is delivered through a mechanism for private listening.

Procedure

1. Check that there is at least one non-visual mode of operation for controlling the volume.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.12 Speaker volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).

NOTE: For noisy environments, 65 dBA may not be sufficient.

C.5.1.3.12 Speaker volume

Type of assessment

Inspection and measurement

Pre-conditions

1. The auditory output is provided as non-visual access to closed functionality.

2. The auditory output is delivered through speakers.

Procedure

1. Check that a non-visual incremental volume control is provided.

2. Check that output amplification up to a level of at least 65 dBA (-29 dBPaA) is available.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.13 Volume reset

Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.

NOTE: A feature to disable the volume reset function may be provided in order to enable the single-user exception to be met.

C.5.1.3.13 Volume reset

Type of assessment

Inspection and measurement

Pre-conditions

1. The auditory output is provided as non-visual access to closed functionality.

2. The ICT is not dedicated to a single user.

Procedure

1. Check that a function that automatically resets the volume to be at a level of 65 dBA or less after every use is provided.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.14 Spoken languages

Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:

1. for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text;

2. where the content is generated externally and not under the control of the ICT vendor, the present clause shall not be required to apply for languages not supported by the ICT's speech synthesizer;

3. for displayed languages that cannot be selected using non-visual access;

4. where the user explicitly selects a speech language that is different from the language of the displayed content.

C.5.1.3.14 Spoken languages

Type of assessment

Testing

Pre-conditions

1. The speech output is provided as non-visual access to closed functionality.

2. The speech output is not proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

3. The content is not generated externally and is under the control of the ICT vendor.

4. The displayed languages can be selected using non-visual access.

5. The user has not selected a speech language that is different from the language of the displayed content.

Procedure

1. Check that the speech output is in the same human language of the displayed content provided.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1 or 3 are not met

5.1.3.15 Non-visual error identification

Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.

C.5.1.3.15 Non-visual error identification

Type of assessment

Testing

Pre-conditions

1. Speech output is provided as non-visual access to closed functionality.

2. An input error is automatically detected.

Procedure

1. Check that speech output identifies the item that is in error.

2. Check that the speech output describes the item that is in error.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or check 2 false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.3.16 Receipts, tickets, and transactional outputs

Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.

NOTE: The speech output may be provided by any element of the total ICT system.

C.5.1.3.16 Receipts, tickets, and transactional outputs

Type of assessment

Testing

Pre-conditions

1. The ICT is closed to visual access.

2. The ICT provides receipts, tickets, or other outputs as a result of a self-service transaction.

3. The information being checked is not printed copies of itineraries and maps.

Procedure

1. Check that speech output is provided which includes all information necessary to complete or verify the transaction.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-conditions 1, 2 or 3 are not met

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE 1: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

NOTE 2: Table 5.1 and Figure 1 illustrate the relationship between the maximum viewing distance and minimum character height at the specified minimum subtended angle.

(See Table 5.1 and Figure 1)

C.5.1.4 Functionality closed to text enlargement

Type of assessment

Inspection and measurement

Pre-conditions

1. A functionality of the ICT is closed to enlargement features of platform or assistive technology.

2. A viewing distance is specified by the supplier.

Procedure

1. Measure the height of a capital letter H.

2. Check that it subtends an angle of at least 0,7 degrees at the specified viewing distance.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-conditions 1 or 2 are not met

5.1.5 Visual output for auditory information

Where auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the auditory output.

NOTE: This visual information can take the form of captions or text transcripts

C.5.1.5 Visual output for auditory information

Type of assessment

Inspection

Pre-conditions

1. Pre-recorded auditory information is needed to enable the use of closed functions of ICT.

Procedure

1. Check that the visual information is equivalent to the pre-recorded auditory output.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.1.6 Operation without keyboard interface
EN 301 549 clauseDetermination of conformance

5.1.6.1 Closed functionality

Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.

C.5.1.6.1 Closed functionality

Type of assessment

Inspection

Pre-conditions

1. ICT functionality is closed to keyboards or keyboard interfaces.

Procedure

1. Check that all functionality is operable without vision.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.1.6.2 Input focus

Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.

C.5.1.6.2 Input focus

Type of assessment

Inspection

Pre-conditions

1. ICT functionality is closed to keyboards or keyboard interfaces.

2. Input focus can be moved to a user interface element.

Procedure

1. Check that it is possible to move the input focus away from that element using the same mechanism.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

5.1.7 Access without speech

Where speech is needed to operate closed functions of ICT, the ICT shall provide at least one mode of operation using an alternative input mechanism that does not require speech.

C.5.1.7 Access without speech

Type of assessment

Inspection

Pre-conditions

1. Speech is needed to enable the use of closed functions of ICT.

Procedure

1. Check that the closed functions can be enabled by an alternative input mechanism that does not require speech.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.2 Activation of accessibility features

Where ICT has documented accessibility features, it shall be possible to activate those documented accessibility features that are required to meet a specific need without relying on a method that does not support that need.

C.5.2 Activation of accessibility features

Type of assessment

Inspection

Pre-conditions

1. The ICT has documented accessibility features to meet a specific need.

Procedure

1. Check that it is possible to activate those accessibility features without relying on a method that does not support that need.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.3 Biometrics

Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.

NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.

NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals with disabilities possess at least one of the specified biological characteristics. Examples of dissimilar biological characteristics are fingerprints, eye retinal patterns, voice, and face.

C.5.3 Biometrics

Type of assessment

Test 1

Pre-conditions

1. The ICT uses biological characteristic for user identification.

Procedure

1. Check that more than one means can be used for user identification.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Type of assessment

Test 2

Pre-conditions

1. The ICT uses biological characteristic for control of ICT.

Procedure

1. Check that more than one means can be used for control of ICT.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

C.5.4 Preservation of accessibility information during conversion

Type of assessment

Inspection

Pre-conditions

1. The non-proprietary information provided for accessibility is documented.

2. The ICT converts information or communication.

3. The non-proprietary information provided for accessibility can be contained in the destination format.

4. The non-proprietary information provided for accessibility can be supported by the destination format.

Procedure

1. Check that the non-proprietary information provided for accessibility is preserved when the ICT converts information or communication.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, 3 or 4 is not met

5.5 Operable parts
EN 301 549 clauseDetermination of conformance

5.5.1 Means of operation

Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.

C.5.5.1 Means of operation

Type of assessment

Testing

Pre-conditions

The ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate.

Procedure

1. Check that there is an accessible alternative means of operation that does not require these actions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

C.5.5.2 Operable parts discernibility

Type of assessment

Testing

Pre-conditions

The ICT has operable parts.

Procedure

1. Identify that there is a means to discern each operable part without vision.

2. Check that the action associated with the operable part has not been performed when using the means to discern each operable part of step 1.

Result

Pass: Checks 1 and 2 are true

Fail: Checks 1 or 2 are false

Not applicable: Pre-condition 1 is not met

5.6 Locking or toggle controls
EN 301 549 clauseDetermination of conformance

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

C.5.6.1 Tactile or auditory status

Type of assessment

Inspection

Pre-conditions

1. The ICT has a locking or toggle control.

2. The locking or toggle control is visually presented to the user.

Procedure

1. Check that there is at least one mode of operation where the status of all locking or toggle controls can be determined through touch without operating the control.

2. Check that there is at least one mode of operation where the status of all locking or toggle controls can be determined through sound without operating the control.

Result

Pass: Check 1 or 2 is true

Fail: Checks 1 and 2 are false

Not applicable: Pre-condition 1 or 2 is not met

5.6.2 Visual status

Where ICT has a locking or toggle control and the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example of making the status of a control determinable is a visual status indicator on a keyboard.

C.5.6.2 Visual status

Type of assessment

Inspection

Pre-conditions

1. The ICT has a locking or toggle control.

2. The locking or toggle control is presented to the user.

Procedure

1. Check that there is at least one mode of operation where the status of all locking or toggle controls can be visually determined when the control is presented.

Result: Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

1. the delay before the key repeat shall be adjustable to at least 2 seconds; and

2. the key repeat rate shall be adjustable down to one character per 2 seconds.

C.5.7 Key repeat

Type of assessment

Testing

Pre-conditions

1. The ICT has a key repeat function A keyboard or keypad with key repeat is provided.

2. The key repeat cannot be turned off.

Procedure

1. Check that the delay before key repeat can be adjusted to at least 2 seconds.

2. Check that the key repeat rate can be adjusted to 2 seconds per character.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-condition 1 or 2 is not met

5.8 Double-strike key acceptance

Where ICT has a keyboard or keypad, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.

C.5.8 Double-strike key acceptance

Type of assessment

Testing

Pre-conditions

1. The ICT has a keyboard or keypad

Procedure

1. Check that there is a mechanism that allows adjustment of the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke.

2. Adjust that mechanism to its maximum setting.

3. Press any key.

4. After a delay of 0,5 seconds press the same key as that pressed in step 3.

5. Check whether the keystroke of step 4 has been accepted.

Result

Pass: Check 1 is true and check 5 is false

Fail: Check 1 is false or check 5 is true

Not applicable: Pre-condition 1 is not met

5.9 Simultaneous user actions

Where ICT uses simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.

NOTE: Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or having to touch a surface with more than one finger are examples of simultaneous user actions.

C.5.9 Simultaneous user actions

Type of assessment

Inspection

Pre-conditions

1. ICT has a mode of operation requiring simultaneous user actions.

Procedure

1. Check that there is a mode of operation that does not require simultaneous user actions.

2. Determine all the user controllable functions of the ICT.

3. Check that each user controllable function can be operated with a single user action.

Result

Pass: Check 3 is true

Fail: Check 3 is false for all modes of operation.

Not applicable: Pre-condition 1 is not met

6 ICT with two-way voice communication

EN 301 549 clauseDetermination of conformance

6.1 Audio bandwidth for speech

Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT shall be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7000 Hz.

NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 [i.21] is widely used.

NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation ITU-T G.722.2 [i.22] are sometimes used so as to avoid transcoding.

C.6.1 Audio bandwidth for speech

Type of assessment

Measurement

Pre-conditions

1. The ICT under test provides two-way voice communication.

Procedure

1. Check that the ICT can encode and decode audio with a frequency range with an upper limit of at least 7000 Hz.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

6.2 Real-time text (RTT) functionality
6.2.1 RTT provision
EN 301 549 clauseDetermination of conformance

6.2.1.1 RTT communication

Where ICT is in a mode that provides a means for two-way voice communication, the ICT shall provide a means for two-way RTT communication, except where this would require design changes to add input or output hardware to the ICT.

NOTE 1: This requirement includes those products which do not have physical display or text entry capabilities but have the capability to connect to devices that do have such capabilities. It also includes intermediate ICT between the endpoints of the communication.

NOTE 2: There is no requirement to add: a hardware display, a hardware keyboard, or hardware to support the ability to connect to a display or keyboard, wired or wirelessly, if this hardware would not normally be provided.

NOTE 3: For the purposes of interoperability, support of Recommendation ITU-T T.140 [i.36] is widely used.

C.6.2.1.1 RTT communication

Type of assessment

Inspection

Pre-conditions

1. The ICT under test has a mode that provides a means for two-way voice communication.

2. The ICT is in the mode that provides a means for two-way voice communication.

3. An "RTT reference terminal" is available.

Procedure

1. Check that the ICT allows two-way RTT communication with the "reference" ICT.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

Not testable: Pre-condition 3 is not met

NOTE: An "RTT reference terminal" is a terminal specifically designed for testing RTT capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent "RTT reference terminal".

6.2.1.2 Concurrent voice and text

Where ICT provides a means for two-way voice communication and for users to communicate by RTT, it shall allow concurrent voice and text through a single user connection.

NOTE 1: With many-party communication, as in a conference system, it is allowed (but not required or necessarily recommended) that RTT be handled in a single display field and that "turn-taking" be necessary to avoid confusion (in the same way that turn-taking is required for those presenting/talking with voice).

NOTE 2: With many-party communication, best practice is for hand-raising for voice users and RTT users to be handled in the same way, so that voice and RTT users are in the same queue

NOTE 3: With a many-party conference system that has chat as one of its features - the RTT (like the voice) would typically be separate from the chat so that RTT use does not interfere with chat (i.e. people can be messaging in the chat field while the person is presenting/talking with RTT - in the same manner that people message using the chat feature while people are talking with voice). RTT users would then use RTT for presenting and use the Chat feature to message while others are presenting (via Voice or RTT).

NOTE 4: The availability of voice and RTT running concurrently (and separately from chat) can also allow the RTT field to support text captioning when someone is speaking (and it is therefore not being used for RTT since it is not the RTT user's turn to speak).

NOTE 5: Where both server-side software and local hardware and software are required to provide voice communication, where neither part can support voice communication without the other and are sold as a unit for the voice communication function, the local and server-side components are considered a single product.

C.6.2.1.2 Concurrent voice and text

Type of assessment

Inspection

Pre-conditions

1. The ICT supports two-way voice communication.

2. The ICT provides a means for two-way RTT communication.

Procedure

1. Check that ICT allows the concurrent use of voice and RTT through a single user connection.

Result

Pass: Checks 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

6.2.2 Display of RTT (Real-time Text)
EN 301 549 clauseDetermination of conformance

6.2.2.1 Visually distinguishable display

Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from and separated from received text.

NOTE: The ability of the user to choose between having the send and receive text be displayed in-line or separately, and with options to select, allows users to display RTT in a form that works best for them. This would allow Braille users to use a single field and take turns and have text appear in the sequential way that they may need or prefer.

C.6.2.2.1 Visually distinguishable display

Type of assessment

Inspection

Pre-conditions

1. The ICT under test has RTT send and receive capabilities.

2. The ICT supports RTT mechanism(s).

3. A "reference" RTT-capable terminal using mechanisms supported by the ICT system is connected at the other end of the system to the ICT under test.

Procedure

1. The ICT under test is connected to the ICT system terminated by the "reference" terminal.

2. The different elements of the ICT are in an operational status (the connection is active and the terminals are in the relevant RTT mode) and the two terminals are communicating to each other.

3. A Short text sequence is sent by the ICT under test.

4. A Short text sequence is sent by the "reference" terminal.

5. Check, on the ICT under test, that displayed sent text is visually differentiated from and separated from received text.

Result

Pass: Check 5 is true

Fail: Check 5 is false

NOTE: A "reference" terminal is a terminal having RTT send and receive capabilities that uses the RTT mechanisms supported by the ICT system. This "reference" terminal is the responsibility of the test laboratory.

6.2.2.2 Programmatically determinable send and receive direction

Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted/received text shall be programmatically determinable, unless the RTT is implemented as closed functionality.

NOTE: This enables screen readers to distinguish between incoming text and outgoing text when used with RTT functionality.

C.6.2.2.2 Programmatically determinable send and receive direction

Type of assessment

Inspection

Pre-conditions

1. The ICT under test has RTT send and receive capabilities.

2. The RTT is open functionality.

3. A “RTT reference terminal” is available.

Procedure

1. The ICT under test is connected to the "RTT reference terminal".

2. The different elements of the ICT are in an operational status (the connection is active and the terminals are in the relevant RTT mode) and the two terminals are communicating with each other

3. A Short text sequence is sent by the ICT under test.

4. A Short text sequence is sent by the "RTT reference terminal".

5. Check that the send/receive direction of transmitted text is programmatically determinable.

Result

Pass: Check 5 is true

Fail: Check 5 is false

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

NOTE: An "RTT reference terminal" is a terminal specifically designed for testing RTT capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent "RTT reference terminal".

6.2.2.3 Speaker identification

Where ICT has RTT capabilities, and provides speaker identification for voice, the ICT shall provide speaker identification for RTT.

NOTE: This is necessary to enable both voice and RTT participants to know who is currently communicating, whether it be in RTT or voice.

C.6.2.2.3 Speaker identification

Type of assessment

Inspection

Pre-conditions

1. The ICT has RTT capabilities.

2. The ICT provides speaker identification for voice.

3. An "RTT reference terminal" is available.

Procedure

1. The ICT under test is connected to the "RTT reference terminal".

2. RTT is sent from the "RTT reference terminal".

3. Check by observation whether the ICT under test provides speaker identification for RTT incoming text.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

NOTE: An "RTT reference terminal" is a terminal specifically designed for testing RTT capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent "RTT reference terminal".

6.2.2.4 Visual indicator of audio with RTT

Where ICT provides two-way voice communication, and has RTT capabilities, the ICT shall provide a real-time visual indicator of audio activity on the display.

NOTE 1: The visual indicator may be a simple character position on the display that flickers on and off to reflect audio activity, or presentation of the information in another way that can be both visible to sighted users and passed on to deaf-blind users who are using a braille display.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

C.6.2.2.4 Visual indicator of audio with RTT

Type of assessment

Inspection

Pre-conditions

1. ICT provides two-way voice communication.

2. ICT has RTT capabilities.

Procedure

1. ICT under test is connected to another ICT providing two-way voice communication that is compatible with the voice communication on the ICT under test.

2. A person speaks into the other ICT.

3. Check by observation whether there is a real-time visual indicator of audio activity.

Result

Pass: Check 3 is true

Fail: Check 3 is false

Not applicable: Pre-condition 1 or 2 is not met

NOTE: The indicator should flicker in real time in a way that reflects the audio activity.

6.2.3 Interoperability

Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by clause 6.2.1.1) shall support the applicable RTT interoperability mechanisms described below:

1. ICT interoperating with other ICT directly connected over the Public Switched Telephone Network (PSTN) using Recommendation ITU-T V.18 [i.23] or any of its annexes for text telephony signals at the PSTN interface;

2. ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using RTT that conforms to IETF RFC 4103 [i.13]. For ICT interoperating with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, the set of protocols specified in ETSI TS 126 114 [i.10], ETSI TS 122 173 [i.11] and ETSI TS 134 229 [i.12] describe how IETF RFC 4103 [i.13] would apply;

3. ICT interoperating with other ICT using technologies other than a or b, above, using a relevant and applicable common specification for RTT exchange that is published and available for the environments in which they will be operating. This common specification shall include a method for indicating loss or corruption of characters;

4. ICT interoperating with other ICT using a standard for RTT that has been introduced for use in any of the above environments, and is supported by all of the other active ICT that support voice and RTT in that environment.

NOTE 1: In practice, new standards are introduced as an alternative codec/protocol that is supported alongside the existing common standard and used when all end-to-end components support it while technology development, combined with other reasons including societal development and cost efficiency, may make others become obsolete.

NOTE 2: Where multiple technologies are used to provide voice communication, multiple interoperability mechanisms may be needed to ensure that all users are able to use RTT.

EXAMPLE: A conferencing system that supports voice communication through an internet connection might provide RTT over an internet connection using a proprietary RTT method (option c). However, regardless of whether the RTT method is proprietary or non-proprietary, if the conferencing system also offers telephony communication it will also need to support options a or b to ensure that RTT is supported over the telephony connection.

C.6.2.3 Interoperability

a)

Type of assessment

Test

Pre-conditions

1. The ICT provides a means for two-way voice communication over the Public Switched Telephone Network (PSTN).

2. The ICT provides a means for two-way RTT communication.

3. A "V.18 reference terminal" is available.

Procedure

1. Check that the ICT interoperates over the Public Switched Telephone Network (PSTN), with the V.18 reference terminal connected to the PSTN as described in Recommendation ITU-T V.18 [i.23] or any of its annexes for text telephony signals at the PSTN interface

Result

Pass: Check 1 is true

Fail: Checks 1 is false

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

NOTE: A "V.18 reference terminal" is a terminal specifically designed for testing V.18 capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent reference terminal.

b)

Type of assessment

Test

Pre-conditions

1. The ICT provides a means for two-way voice communication using VOIP with Session Initiation Protocol (SIP).

2. The ICT provides a means for two-way RTT communication.

3. An "RTT reference terminal" is available.

Procedure

1. Check that the ICT interoperates with the "RTT reference terminal" using VOIP with Session Initiation Protocol (SIP) and using RTT that conforms to IETF RFC 4103 [i.13].

2. If the ICT interoperates with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, check that it follows the set of protocols in ETSI TS 126 114 [i.10], ETSI TS 122 173 [i.11] and ETSI TS 134 229 [i.12] that specify how IETF RFC 4103 [i.13] applies.

Result

Pass: Check 1 is true and, if the ICT interoperates with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, check 2 is true.

Fail: Check 1 is false or, if the ICT interoperates with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, check 2 is false.

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

NOTE: An "RTT reference terminal" is a terminal specifically designed for testing RTT capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent "RTT reference terminal".

c)

Type of assessment

Test

Pre-conditions

1. The ICT provides a means for two-way voice communication using technologies other than PSTN or VOIP with Session Initiation Protocol (SIP).

2. The ICT provides a means for two-way RTT communication.

3. An "RTT reference terminal" is available for that mode of RTT communication.

Procedure

1. Check that the ICT interoperates with the "RTT reference terminal" using a relevant and applicable common specification for RTT exchange that is published and available for the environment in which the ICT will be operating.

2. Check that the common specification in check 1 includes a method for indicating loss or corruption of characters.

Result

Pass: Check 1 and 2 are true

Fail: Checks 1 or 2 are false

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

NOTE: An "RTT reference terminal" is a terminal specifically designed for testing RTT capable devices in a manner that would confirm their functionality and interoperability. These are generally created by a national or international standards entity so that all testing is done with a consistent "RTT reference terminal".

d)

Type of assessment

Test

Pre-conditions

1. The ICT provides a means for two-way voice communication.

2. The ICT provides a means for two-way RTT communication.

3. An "RTT reference terminal" is available using the new RTT Standard.

Procedure

1. Check that the ICT under test interoperates with the "RTT reference terminal" for the new RTT standard that has been introduced for use.

2. Check that the new RTT standard is supported by all of the other active ICT that support voice and RTT in the same environment.

Result

Pass: Check 1 and 2 are true

Fail: Checks 1 or 2 are false

Not applicable: Pre-condition 1 or 2 is not met

Not testable: Pre-condition 3 is not met

RTT (Real-time text) responsiveness

Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network or platform on which the ICT runs within 500 ms of the time that the smallest reliably composed unit of text entry is available to the ICT for transmission. Delays due to platform or network performance shall not be included in the 500 ms limit.

NOTE 1: For character by character input, the "smallest reliably composed unit of text entry" would be a character. For word prediction it would be a word. For some voice recognition systems - the text may not exit the recognition software until an entire word (or phrase) has been spoken. In this case, the smallest reliably composed unit of text entry available to the ICT would be the word (or phrase).

NOTE 2: The 500 ms limit allows buffering of characters for this period before transmission so character by character transmission is not required unless the characters are generated more slowly than 1 per 500 ms.

NOTE 3: A delay of 300 ms, or less, produces a better impression of flow to the user.

C.6.2.4 RTT (Real-time text) responsiveness

Type of assessment

Inspection of Measurement data or Test

Pre-conditions

1. The ICT under test utilises RTT input.

2. The ICT under test is connected to a device or software that can determine when characters are transmitted by the ICT under test.

Procedure

1. Enter single characters to the terminal under test.

2. Check the time at which input entry has occurred (e.g. characters appear up on the local screen).

3. Check the period between input entry to the ICT under test and the time when the text is transmitted to the ICT network or platform.

Result

Pass: Check 3 is less than or equal to 500 ms.

Fail: Check 3 is greater than 500 ms.

Not applicable: Pre-condition 1 is not met

Not testable: Pre-condition 2 is not met

NOTE: As described in the notes to clause 6.2.4, the identification of when input entry has occurred may vary according to the type of RTT system under test.

6.3 Caller ID

Where ICT provides caller identification or similar telecommunications functions are provided, the caller identification and similar telecommunications functions shall be available in text form as well as being programmatically determinable, unless the functionality is closed.

C.6.3 Caller ID

Type of assessment

Inspection

Pre-conditions

1. The ICT provides caller identification, or similar telecommunications functions are provided.

Procedure

1. Check that the information delivered by each function is available in text form.

2. Check that the information delivered by each function is programmatically determinable.

Result

Pass: Check 1 is true and either check 2 is true or the functionality is closed

Fail: Check 1 is false or check 2 is false when the functionality is not closed

Not applicable: Pre-condition 1 is not met.

6.4 Alternatives to voice-based services

Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT shall offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.

NOTE 1: Tasks that involve both operating the interface and perceiving the information would require that both the interface and information be accessible without use of speech or hearing.

NOTE 2: Solutions capable of handling audio, RTT and video media could satisfy the above requirement.

C.6.4 Alternatives to voice-based services

Type of assessment

Inspection

Pre-conditions

1. The ICT provides real-time voice-based communication.

2. The ICT provides voice mail, auto-attendant, or interactive voice response facilities.

Procedure

1. Check that the ICT offers users a means to access the information without the use of hearing or speech.

2. Check that a user can carry out the tasks provided by the system without the use of hearing or speech.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-condition 1 or 2 is not met

6.5 Video communication
EN 301 549 clauseDetermination of conformance

6.5.1 General (informative)

Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with a resolution of at least Quarter Video Graphics Array (QVGA, 320 x 240), a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.

Increasing the resolution and frame rate further improves both sign language (especially finger spelling) and lipreading, with frame rate being more important than resolution.

Time differences between audio and video (asynchronicity) can have a great impact on lip-reading - with video that lags behind audio having greater negative effect.

End-to-end latency can be a problem in video (sign) communication. Overall delay values below 400 ms are preferred, with an increase in preference down to 100 ms. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.

NOTE: Recommendation ITU-T F.703 [i.37] defines and gives requirements for Total Conversation that relate to the integration of audio, RTT and video in a single user connection.

C.6.5.1 General (informative)

Clause 6.5.1 is informative only and contains no requirements requiring test.

6.5.2 Resolution

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

1. shall support at least QVGA resolution;

2. should preferably support at least VGA resolution.

C.6.5.2 Resolution

Type of assessment

Inspection

Pre-conditions

1. The ICT provides 2 way voice communication.

2. The ICT includes real-time video functionality.

Procedure

1. Check that the video communication resolution is QVGA resolution or better.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

6.5.3 Frame rate

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

1. shall support a frame rate of at least 20 frames per second (FPS);

2. should preferably support a frame rate of at least 30 frames per second (FPS) with or without sign language in the video stream.

C.6.5.3 Frame rate

Type of assessment

Inspection

Pre-conditions

1. The ICT provides 2 way voice communication.

2. The ICT includes real-time video functionality.

Procedure

1. Check that the video communication frame rate is equal to or higher than 20 frames per second.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

6.5.4 Synchronization between audio and video

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT shall ensure a maximum time difference of 100 ms between the speech and video presented to the user.

NOTE: Recent research shows that, if audio leads the video, the intelligibility suffers much more than the reverse.

C.6.5.4 Synchronization between audio and video

Type of assessment

Measurement

Pre-conditions

1. The ICT provides 2 way voice communication.

2. The ICT includes real-time video functionality.

Procedure

1. Check that the time difference between the speech and video presented to the user is equal to or less than 100 ms.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

6.5.5 Visual indicator of audio with video

Where ICT provides two-way voice communication, and includes real-time video functionality, the ICT shall provide a real-time visual indicator of audio activity.

NOTE 1: The visual indicator may be a simple visual dot or LED, or other type of on/off indicator, that flickers to reflect audio activity.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

C.6.5.5 Visual indicator of audio with video

Type of assessment

Measurement

Pre-conditions

1. ICT provides two-way voice communication.

2. ICT has real-time video capabilities.

Procedure

1. ICT under test is connected to another ICT providing two-way voice communication that is compatible with the voice communication on the ICT under test.

2. A person speaks into the other ICT.

3. Check by observation whether there is a real-time visual indicator of audio activity

Result

Pass: Check 3 is true

Fail: Check 3 is false

Not applicable: Pre-condition 1 or 2 is not met

NOTE: The indicator should flicker in real time in a way that reflects the audio activity.

6.5.6 Speaker identification with video (sign language) communication

Where ICT provides speaker identification for voice users, it shall provide a means for speaker identification for real-time signing and sign language users once the start of signing has been indicated.

NOTE 1: The speaker ID can be in the same location as for voice users for multiparty calls.

NOTE 2: This mechanism might be triggered manually by a user, or automatically where this is technically achievable.

C.6.5.6 Speaker identification with video (sign language) communication

Type of assessment

Measurement

Pre-conditions

1. The ICT provides 2 way voice communication.

2. The ICT includes real-time video.

Procedure

1. The ICT under test is connected to a compatible ICT that supports video and a person communicates in sign language.

2. Check by observation whether the ICT under test provides a means for speaker identification for the sign language users.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1 or 2 is not met

Where ICT provides speaker identification for voice users, it shall provide a means for speaker identification for real-time signing and sign language users once the start of signing has been indicated.

NOTE 1: The speaker ID can be in the same location as for voice users for multiparty calls.

NOTE 2: This mechanism might be triggered manually by a user, or automatically where this is technically achievable.

6.6 Alternatives to video-based services

Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:

1. for audible information, without the use of hearing;

2. for spoken commands, without the use of speech;

3. for visual information, without the use of vision.

NOTE: Solutions capable of generating real-time captions or handling RTT (real-time text) could satisfy the above requirement.

C.6.6 Alternatives to video-based services

Clause 6.6 is advisory only and contains no testable requirements.

7 ICT with video capabilities

7.1 Caption processing technology
EN 301 549 clauseDetermination of conformance

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

NOTE 3: Clause 7.1.1 refers to the ability of the player to display captions. Clauses 9.1.2.2, 10.1.2.2 and 11.1.2.2 refer to the provision of captions for the content (the video).

C.7.1.1 Captioning playback

Type of assessment

Test 1

Pre-conditions

1. The ICT displays or processes video with synchronized audio.

2. Captions are provided in the video.

Procedure

1. Check that there is a mechanism to display the captions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Type of assessment

Test 2

Pre-conditions

1. The ICT displays or processes video with synchronized audio.

2. Closed captions are provided by the content.

Procedure

1. Check that there is a mechanism to choose to display the captions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions as follows:

  • Captions in recorded material: within 100 ms of the time stamp of the caption.
  • Live captions: within 100 ms of the availability of the caption to the player.

C.7.1.2 Captioning synchronization

Type of assessment

Inspection

Pre-conditions

1. The ICT has a mechanism to display captions.

Procedure

1. Check that the mechanism to display the captions preserves the synchronization between the audio and corresponding captions within a tenth of a second of the time stamp of the caption, or the availability of the caption to the player if a live caption.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

C.7.1.3 Preservation of captioning

Type of assessment

Inspection

Pre-conditions

1. The ICT transmits converts or records video with synchronized audio.

Procedure

1. Check that the ICT preserves caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

7.1.4 Captions characteristics

Where ICT displays captions, it shall provide a way for the user to adapt the displayed characteristics of captions to their individual requirements, except where the captions are displayed as unmodifiable characters.

NOTE 1: Defining the background and foreground colour of subtitles, font type, size opacity of the background box of subtitles, and the contour or border of the fonts can contribute to meeting this requirement.

NOTE 2: Subtitles that are bitmap images are examples of unmodifiable characters.

C.7.1.4 Captions characteristics

Type of assessment

Inspection

Pre-conditions

1. The ICT displays captions.

2. The captions under test are displayed as modifiable characters.

Procedure

1. Check that the ICT provides a way for the user to adapt the displayed characteristics of captions to their individual requirements.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

7.1.5 Spoken subtitles

Where ICT displays video with synchronized audio, it shall have a mode of operation to provide a spoken output of the available captions, except where the content of the displayed captions is not programmatically determinable.

NOTE 1: Being able to manage speech output range for spoken subtitles independently from general ICT speech is preferable for most users. That is possible when the audio file with spoken subtitle is delivered in a separate audio track and mixed in the end user’s device.

NOTE 2: Presenting the separate audio track with spoken subtitles in synchronization with the displayed subtitles/captions improves understandability of the subtitles.

NOTE 3: Providing subtitles/captions as separate text-streams, facilitates converting the respective texts into audio.

NOTE 4: Subtitles that are bitmap images are examples where the content of the displayed captions will not be programmatically determinable.

C.7.1.5 Spoken subtitles

Type of assessment

Inspection

Pre-conditions

1. The ICT displays video with synchronized audio.

2. The content of the captions under test are programmatically determinable.

Procedure

1. Check that there is a mode of operation to provide a spoken output of the available captions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

7.2 Audio description technology
EN 301 549 clauseDetermination of conformance

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks

NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.

NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

C.7.2.1 Audio description playback

Type of assessment

Inspection

Pre-conditions

1. The ICT displays video with synchronized audio.

Procedure

1. Check that there is an explicit and separate mechanism for audio description.

2. Check that there is a mechanism to select and play the audio description to the default audio channel.

3. Check that the ICT enables the user to select and play several audio tracks.

Result

Pass: Check 1 and 2 are true or 1 is false and 3 is true

Fail: Check 1 is true and 2 is false or 1 is false and 3 is false

Not applicable: Pre-condition 1 is not met.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

C.7.2.2 Audio description synchronization

Type of assessment

Inspection

Pre-conditions

1. The ICT has a mechanism to play audio description.

Procedure

1. Check that the synchronization between the audio/visual content and the corresponding audio description is preserved.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

C.7.2.3 Preservation of audio description

Type of assessment

Inspection

Pre-conditions

1. The ICT transmits converts or records video with synchronized audio.

Procedure

1. Check that the ICT preserves audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

C.7.3 User controls for captions and audio description

Type of assessment

Inspection

Pre-conditions

1. The ICT primarily display materials containing video with associated audio content.

Procedure

1. Check that user controls to activate subtitling and audio descriptions are provided to the user at the same level of interaction as the primary media controls.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8 Hardware

8.1 General
EN 301 549 clauseDetermination of conformance

8.1.1 Generic requirements

The "generic requirements" of clause 5 also apply to ICT that is hardware.

C.8.1.1 Generic requirements

Clause 8.1.1 is advisory only and contains no testable requirements.

8.1.2 Standard connections

Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.

NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the use of standard connections on ICT.

NOTE 2: The word connection applies to both physical and wireless connections.

NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.

C.8.1.2 Standard connections

Type of assessment

Inspection

Pre-conditions

1. The ICT provides user input or output device connection points.

Procedure

1. Check that one type of connection conforms to an industry standard non-proprietary format.

2. Check that one type of connection conforms to an industry standard non-proprietary format through the use of commercially available adapters.

Result

Pass: Check 1 or 2 is true

Fail: Checks 1 and 2 are false

Not applicable: Pre-condition 1 is not met.

NOTE: The connections may be physical or wireless connections.

8.1.3 Colour

Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

C.8.1.3 Colour

Type of assessment

Inspection

Pre-conditions

1. The hardware aspects of the ICT conveys visual information using colour coding as a means to indicate an action, to prompt a response, or to distinguish a visual element.

Procedure

1. Check that an alternative form of visual coding is provided.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8.2 Hardware products with speech output
8.2.1 Speech volume gain
EN 301 549 clauseDetermination of conformance

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 [i.2] are deemed to comply with this requirement.

C.8.2.1.1 Speech volume range

Type of assessment

Inspection based on measurement data

Pre-conditions

1. The ICT hardware has speech output.

Procedure

1. Check that the ICT is certified to meet ANSI/TIA-4965 [i.2].

2. Measure the level (in dB) of the speech output at the lowest volume setting.

3. Measure the level (in dB) of the speech output at the highest volume setting.

4. Check that the range between 1 and 2 is greater than or equal to 18 dB.

Result

Pass: Check 1 or 4 is true

Fail: Check 1 and 4 are false

Not applicable: Pre-condition 1 is not met.

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

C.8.2.1.2 Incremental volume control

Type of assessment

Inspection based on measurement data

Pre-conditions

1. The ICT hardware has speech output.

2. The volume control is incremental.

Procedure

1. Measure the level (in dB) of the speech output at the lowest volume setting.

2. Check if one intermediate step provides a level 12 dB above the lowest volume level measured in step 1.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1 or 2 is not met.

8.2.2 Magnetic coupling
EN 301 549 clauseDetermination of conformance

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETSI ETS 300 381 [1], it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1 [2].

NOTE 1: ICT fulfilling the requirements of TIA-1083-A [i.24] is deemed to comply with the requirements of this clause.

NOTE 2: Magnetic coupling is also known as inductive coupling for T-coil.

C.8.2.2.1 Fixed-line devices

Type of assessment

Inspection based on measurement data

Pre-conditions

1. The ICT hardware is a fixed line communication device with an audio output that is normally held to the ear.

Procedure

1. Check that the ICT is certified to meet TIA-1083-A [i.24].

2. Measurements are made according to ETSI ES 200 381-1 [2] which prove that the requirements defined in that standard are fulfilled.

3. The ICT carries the "T" symbol specified in ETSI ETS 300 381 [1].

Result

Pass: Check 1 or 2 is true and check 3 is true

Fail: Checks 1 and 2 are false or check 3 is false

Not applicable: Pre-condition 1 is not met.

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2 [3].

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 [i.1] is deemed to comply with the requirements of this clause.

C.8.2.2.2 Wireless communication devices

Type of assessment

Inspection based on measurement data

Pre-conditions

1. The ICT hardware is a wireless communication device which is normally held to the ear.

Procedure

1. Check that the ICT is certified to meet ANSI/IEEE C63.19 [i.1].

2. Check that the ICT provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2 [3].

Result

Pass: Check 1 or 2 is true

Fail: Checks 1 and 2 are false

Not applicable: Pre-condition 1 is not met.

8.3 Stationary ICT
EN 301 549 clauseDetermination of conformance

8.3.0 General (informative)

The present document defines the dimensions for accessing stationary ICT that can be placed in a built environment, but does not define the dimensions of the built environment in general.

The scope includes stationary ICT, of which floors and circulation spaces are "an integral part" (typically kiosks and cabins), and where there are external reach ranges relevant for operating the stationary ICT.

Clauses 8.3.2 to 8.3.4 specify mandatory limits for the maximum and minimum height of operable parts and displays. Based on dimensions shown in Figure 53 of ISO 21542:2011 [i.34], it is recommended that the possible height range is reduced to:

  • minimum and maximum heights of operable parts: 800 mm and 1100 mm respectively, and
  • minimum and maximum heights of displays: 1200 mm and 1400 mm respectively.

C.8.3.0 General Finformative)

Clause 8.3.0 is advisory only and contains no testable requirements.

8.3.1 Forward or side reach

Stationary ICT shall conform to either clause 8.3.2 or clause 8.3.3

NOTE 1: This does not preclude conforming to both clauses.

NOTE 2: The dimensions set out in clauses 407.8.3 and 407.8.2 of Section 508 of the Rehabilitation Act, as published in January 2017 [i.25], are identical to those given in clauses 8.3.2 and 8.3.3 of the present document

NOTE 3: Physical access to stationary ICT is dependent on the dimensions of both the ICT and the environment in which it is installed and operated. Clause 8.3 does not apply to the accessibility of the physical environment external to the ICT.

C.8.3.1 Forward or side reach

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT.

Procedure

1. Check whether the ICT conforms to clause 8.3.2.2.

2. Check whether the ICT conforms to clause 8.3.2.3.

Result

Pass: Check 1 or 2 is true

Fail: Checks 1 and 2 are false

Not applicable: Pre-condition 1 is not met.

8.3.2 Forward reach
EN 301 549 clauseDetermination of conformance

8.3.2.1 Unobstructed high forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no higher than 1220 mm (48 inches) above the floor of the access space. This is shown in Figure 2.

C.8.3.2.1 Unobstructed high forward reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. No part of the stationary ICT obstructs the forward reach.

Procedure

1. Check that at least one of each type of operable part is located no higher than 1200 mm (48 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.2.2 Unobstructed low forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no lower than 380 mm (15 inches) above the floor of the access space. This is shown in Figure 2

C.8.3.2.2 Unobstructed low forward reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. No part of the stationary ICT obstructs the forward reach.

Procedure

1. Check that at least one of each type of operable part is located no lower than 380 mm (15 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

8.3.2.3 Obstructed forward reach
EN 301 549 clauseDetermination of conformance

8.3.2.3.1 Clear space

Where an obstruction is an integral part of the stationary ICT and hinders the access to any type of operable part, the ICT shall provide a clear space which extends beneath the obstructing element for a distance not less than the required reach depth over the obstruction.

NOTE: Ensuring that there will be unhindered "access to any type of operable part" guarantees that a user will be able access at least one of each type of operable part.

C.8.3.2.3.1 Clear space

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT.

2. An integral part of the stationary ICT forms an obstruction which hinders to any type of operable part.

Procedure

1. Check that the ICT provides a clear space which extends beneath the obstructing element for a distance not less than the required reach depth over the obstruction.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

8.3.2.3.2 Obstructed (<510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1220 mm (48 inches) above the floor contact of the ICT. This is shown in Figure 3 (a).

C.8.3.2.3.2 Obstructed (<510 mm) forward reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. An integral part of the stationary ICT forms an obstruction which is less than 510 mm (20 inches) deep.

Procedure

1. Check that the forward reach to at least one of each type of operable part is no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Result

Pass: Check 1 is true.

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

8.3.2.3.3 Obstructed (<635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1120 mm (44 inches) above the floor contact of the ICT. This is shown in Figure 3 (b).

8.3.2.3.3 Obstructed (<635 mm) forward reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. An integral part of the stationary ICT forms an obstruction which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) deep.

Procedure

1. Check that the forward reach to at least one of each type of operable part is no higher than 1120 mm (44 inches) above the floor contact of the ICT.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not meted.

8.3.2.4 Knee and toe clearance width

Where the space under an obstacle that is integral to the ICT is part of access space, the clearance shall be at least 760 mm (30 inches) wide.

C.8.3.2.4 Knee and toe clearance width

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. The space under an obstacle that is an integral part of the ICT is part of an access space.

Procedure

1. Check that the width of the knee clearance is greater than 760 mm (30 inches).

2. Check that the width of the toe clearance is greater than 760 mm (30 inches).

Result

Pass: Checks 1 and 2 are true

Fail: Checks 1 or 2 are false

Not applicable: Pre-condition 1 or 2 is not met

8.3.2.5 Toe clearance

Where an obstacle is integral to the ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and shall:

1. extend 635 mm (25 inches) maximum under the whole obstacle;

2. provide a space at least 430 mm (17 inches) deep and 230 mm (9 inches) above the floor under the obstacle;

3. extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

This is shown in Figure 4.

C.8.3.2.5 Toe clearance

a)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. The space under an obstacle that is an integral part of the ICT is part of an access space.

Procedure

1. Check that the width of the knee clearance is greater than 760 mm (30 inches).

2. Check that the width of the toe clearance is greater than 760 mm (30 inches).

Result

Pass: Checks 1 and 2 are true

Fail: Checks 1 or 2 are false

Not applicable: Pre-condition 1 or 2 is not met.

b)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a toe clearance space under any obstacle that is an integral part of the ICT that is less than 230 mm (9 inches) above the floor.

Procedure

1. Check that the toe clearance is at least 430 mm (17 inches) deep and 230 mm (9 inches) above the floor under the obstacle.

Result

Pass: Checks 1 is true

Fail: Checks 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

c)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a toe clearance space under any obstacle that is an integral part of the ICT that is less than 230 mm (9 inches) above the floor.

Procedure

1. Check that the toe clearance extends no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

Result

Pass: Checks 1 is true

Fail: Checks 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

8.3.2.6 Knee clearance

Where an obstacle is integral to the ICT, the space under the obstacle that is between 230 mm (9 inches) and 685 mm (27 inches) above the floor is considered knee clearance and shall:

1. extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;

2. extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;

3. extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;

4. be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.

This is shown in Figure 5.

C.8.3.2.6 Knee clearance

a)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a knee clearance space under the obstacle between 230 mm (9 inches) and 685 mm (25 inches) above the floor.

Procedure

1. Check that there is a knee clearance that extends less than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

b)

Type of assessment

Inspection and measurement

Pre-conditions

1.The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a knee clearance space under the obstacle between 230 mm (9 inches) and 685 mm (25 inches) above the floor.

Procedure

1. Check that there is a knee clearance that extends at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

c)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a knee clearance space under the obstacle between 230 mm (9 inches) and 685 mm (25 inches) above the floor.

Procedure

1. Check that there is a knee clearance that extends more than 205 mm (9 inches) under the obstruction at a height of 685 mm (25 inches) above the floor.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

d)

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstacle that is an integral part of the ICT.

3. There is a knee clearance space under the obstacle between 230 mm (9 inches) and 685 mm (25 inches) above the floor.

Procedure

1. Check that the reduction in depth of the knee clearance is no greater than 25 mm (1 inch) for each 150 mm (6 inches) in height.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met

8.3.3 Side reach
EN 301 549 clauseDetermination of conformance

8.3.3.1 Unobstructed high side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space. This is shown in Figure 6.

C.8.3.3.1 Unobstructed high side reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. Side reach is unobstructed or is obstructed by an element that is an integral part of the stationary ICT which is less than 510 mm (20 inches).

Procedure

1. Check that the high side reach to at least one of each type of operable part is no higher than 1 220 mm (48 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.3.2 Unobstructed low side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space. This is shown in Figure 6.

C.8.3.3.2 Unobstructed low side reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. Side reach is unobstructed or is obstructed by an element that is an integral part of the stationary ICT which is less than 510 mm (20 inches).

Procedure

1. Check that the low side reach to at least one of each type of operable part is greater than or equal to 380 mm (15 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.3.3 Obstructed side reach
EN 301 549 clauseDetermination of conformance

8.3.3.3.1 Obstructed (≤ 255 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is less than or equal to 255 mm (10 inches), the high side reach to at least one of each type of operable part shall be no higher than 1220 mm (48 inches) above the floor of the access space. This is shown in Figure 7 (a).

C.8.3.3.3.1 Obstructed (≤ 255 mm) side reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstruction, less than or equal to 255 mm (10 inches) in depth, that is an integral part of the ICT.

Procedure

1. Check that the high side reach to at least one of each type of operable part is no higher than 1 220 mm (48 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.3.3.2 Obstructed (≤ 610 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is greater than 255 mm (10 inches) with a maximum depth of 610 mm (24 inches), the high side reach to at least one of each type of operable part shall be no higher than 1170 mm (46 inches) above the floor of the access space. This is shown in Figure 7 (b)

C.8.3.3.3.2 Obstructed (≤ 610 mm) side reach

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an obstruction, greater than 255 mm (10 inches) and no more than 610 mm (24 inches) in depth, that is an integral part of the ICT.

Procedure

1. Check that the high side reach to at least one of each type of operable part is no higher than 1 170 mm (46 inches) above the floor of the access space.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.4 Clear floor or ground space
EN 301 549 clauseDetermination of conformance

8.3.4.1 Change in level

Where stationary ICT has a floor within it, then any change of floor level within it or entering it shall be ramped with a slope no steeper than 1:48. Exceptions:

1. If the change in floor level is less than or equal to 6,4 mm (¼ inch) the change may be vertical as shown in Figure 8.

2. If the change in floor level is less than or equal to 13 mm (½ inch) the change may have a slope not steeper than 1:2 as shown in Figure 9.

C.8.3.4.1 Change in level

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is a floor within the ICT.

3. The floor has a change in level.

Procedure

1. If the change in level is ramped, check that it has a slope less than 1:48.

2. If there is a vertical change of floor level, check that it is less than or equal to 6,4 mm.

3. If there is a vertical or sloped change in floor level, check that the slope is not greater than 1:2.

Result

Pass: Check 1 or 2 or 3 is true.

Fail: Checks 1 and 2 and 3 are false

Not applicable: Pre-condition 1 or 2 or 3 is not met

8.3.4.2 Clear floor or ground space

Where stationary ICT has an operating area within it, it shall provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1220 mm (48 inches) from which to operate the ICT. This is shown in Figure 10.

C.8.3.4.2 Clear floor or ground space

Type of assessment

Inspection and measurement

Pre-conditions

1. The ICT is stationary ICT.

2. There is an operating area within it.

Procedure

1. Check that there is a clear floor area with minimum rectangular dimensions of 760 mm on one edge and 1220 mm on the other edge.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.4.3 Approach
EN 301 549 clauseDetermination of conformance

8.3.4.3.1 General

Where stationary ICT has an access space inside it, at least one full side of the space shall be unobstructed.

C.8.3.4.3.1 General

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT.

2. There is an access space inside it.

Procedure

1. Check that one full side of the space is unobstructed.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

8.3.4.3.2 Forward approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space shall be a minimum of 915 mm (36 inches) wide. This is shown in Figure 11.

C.8.3.4.3.2 Forward approach

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT containing an alcove.

2. The operating area is within the alcove.

3. The depth of the alcove is greater than 610 mm

4. A forward approach is necessary.

Procedure

1. Check that the width of the alcove is greater than 915 mm.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, 3 or 4 is not met

8.3.4.3.3 Parallel approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space shall be a minimum of 1525 mm (60 inches) wide. This is shown in Figure 12.

C.8.3.4.3.3 Parallel approach

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT containing an alcove.

2. The operating area is within the alcove.

3. The depth of the alcove is greater than 380 mm.

4. A parallel approach is possible.

Procedure

1. Check that the width of the access space is greater than 1 525 mm.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, 3 or 4 is not met

8.3.5 Visibility

Where stationary ICT provides one or more display screens, at least one of each type of display screen shall be positioned such that the information on the screen is legible from a point located 1015 mm (40 inches) above the centre of the floor of the operating area.

NOTE: The intent of this requirement is that the information on the screen can be read by users with normal vision and appropriate language skills, when seated in a wheelchair.

C.8.3.5 Visibility

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT.

2. One or more display screens are provided.

Procedure

1. Check that at least one of each type of display screen is positioned such that the information on the screen is legible from a point located 1015 mm (40 inches) above the centre of the floor of the operating area.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

8.3.6 Installation instructions

Installation instructions shall be made available for all stationary ICT. These instructions shall give guidance on how to install the ICT in a manner that takes into account applicable requirements for accessibility of the built environment as they apply to the installation of the ICT. Where there are no such requirements the instructions should require that the dimensions of the installed ICT conform to clauses 8.3.2 to 8.3.5 of the present document.

C.8.3.6 Installation instructions

Type of assessment

Inspection

Pre-conditions

1. The ICT is stationary ICT.

Procedure

1. Check that installation instructions are made available.

2. Check that the instructions give guidance on how to install the ICT in a manner that ensures that the dimensions of the installed ICT conform to clauses 8.3.2 to 8.3.4.

3. Check that the instructions say that the installers should also take into account applicable requirements for accessibility of the built environment as they apply to the installation of the ICT.

Result

Pass: Checks 1, 2 and 3 are true

Fail: Checks 1 or 2 or 3 are false

Not applicable: Pre-condition 1 is not met.

8.4 Mechanically operable parts
EN 301 549 clauseDetermination of conformance

8.4.1 Numeric keys

Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.

NOTE: Recommendation ITU-T E.161 [i.20] describes the 12-key telephone keypad layout and provides further details of the form of tactile markers.

C.8.4.1 Numeric keys

Type of assessment

Inspection

Pre-conditions

1. The ICT has physical numeric keys arranged in a 12-key telephone keypad layout.

Procedure

1. Check that the number five key is tactilely distinct from the other keys of the keypad.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8.4.2 Operation of mechanical parts
EN 301 549 clauseDetermination of conformance

8.4.2.1 Means of operation of mechanical parts

Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.

C.8.4.2.1 Means of operation of mechanical parts

Type of assessment

Inspection

Pre-conditions

1. The ICT has operable parts that requires grasping, pinching, or twisting of the wrist to operate.

Procedure

1. Check that there is an accessible alternative means of operation that does not require these actions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8.4.2.2 Force of operation of mechanical parts

Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.

NOTE: ISO 21542:2011 [i.34]: Building Construction - Accessibility and Usability of the Built Environment recommends a value between 2,5 and 5 Newtons.

C.8.4.2.2 Force of operation of mechanical parts

Type of assessment

Inspection

Pre-conditions

1. The ICT has a control which requires a force greater than 22,2 N to operate it.

Procedure

1. Check that an accessible alternative means of operation is provided that requires a force less than or equal to 22,2 N.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8.4.3 Keys, tickets and fare cards

Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.

NOTE: ETSI ETS 300 767 [i.6] defines suitable tactile indications for plastic cards.

C.8.4.3 Keys, tickets and fare cards

Type of assessment

Inspection

Pre-conditions

1. ICT provides keys, tickets or fare cards, and their orientation is important for further use.

Procedure

1. Check that keys, tickets or fare cards have an orientation that is tactilely discernible

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

8.5 Tactile indication of speech mode

Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.

NOTE: The tactile indication could include Braille instructions.

C.8.5 Tactile indication of speech mode

Type of assessment

Inspection

Pre-conditions

1. The ICT is designed for shared use.

2. Speech output is available.

Procedure

1. Check that a tactile indication of the means to initiate the speech mode of operation is provided.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

9 Web

EN 301 549 clauseDetermination of conformance

9.0 General (informative)

Requirements in clause 9 apply to web pages (as defined in clause 3.1) including:

  • Conformance with W3C Web Content Accessibility Guidelines (WCAG 2.0) Level AA is equivalent to conforming with clauses 9.1.1, 9.1.2, 9.1.3.1 to 9.1.3.3, 9.1.4.1 to 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.2, 9.2.3, 9.2.4, 9.3, 9.4.1.1, 9.4.1.2 and the conformance requirements of clause 9.6 of the present document.
  • Conformance with W3C Web Content Accessibility Guidelines (WCAG 2.1) [5] Level AA is equivalent to conforming with all of clauses 9.1 to 9.4 and the conformance requirements of clause 9.6 of the present document.
  • Requirements for non-web documents and non-web software are given in clauses 10 and 11 respectively.

NOTE 1: When evaluating websites they are evaluated as individual web pages. Web applications, including mobile web applications, are covered under the definition of web page which is quite broad and covers all web content types.

NOTE 2: WCAG 2.0 is identical to ISO/IEC 40500:2012: "Information technology - W3C Web Content Accessibility Guidelines (WCAG) 2.0" [4].

The requirements in clauses 9.1 to 9.4 are written using the concept of satisfying success criteria (defined in clause 3.1). A web page satisfies a WCAG success criterion when the success criterion does not evaluate to false when applied to the web page. This implies that if the success criterion puts conditions on a specific feature and that specific feature does not occur in the web page, then the web page satisfies the success criterion.

NOTE 3: For example, a web page that does not contain pre-recorded audio content in synchronized media will automatically satisfy WCAG success criterion 1.2.2 (captions - pre-recorded) and, in consequence, will also conform to clause 9.1.2.2.

In addition to Level AA success criteria, the Web Content Accessibility Guidelines also include success criteria for Level AAA. These are listed in clause 9.5 of the present document. Web authors and procurement accessibility specialists are encouraged to consider whether any of the WCAG Level AAA success criteria offer suggestions that may be applicable and relevant to their project, as well as potentially beneficial to some users.

NOTE 4: The W3C states that "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content".

NOTE 5: "Void" clauses have been inserted in order to maintain alignment with the numbering of WCAG 2.1 Level A and Level AA Success Criteria.

C.9.0 General (informative)

Clause 9.0 is informative only and contains no requirements requiring test.

9.1 Perceivable
9.1.1 Text alternatives
EN 301 549 clauseDetermination of conformance

9.1.1.1 Non-text content

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.1.1 Non-text content.

C.9.1.1.1 Non-text content

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.1.1 Non-text content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.1.1 Non-text content.

9.1.2 Time-based media
EN 301 549 clauseDetermination of conformance

9.1.2.1 Audio-only and video-only (prerecorded)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

C.9.1.2.1 Audio-only and video-only (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

9.1.2.2 Captions (prerecorded)

Where ICT is a web page, it shall satisfy the WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

C.9.1.2.2 Captions (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

9.1.2.3 Audio description or media alternative (prerecorded)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

C.9.1.2.3 Audio description or media alternative (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

9.1.2.4 Captions (live)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

C.9.1.2.4 Captions (live)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

9.1.2.5 Audio description (prerecorded)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

C.9.1.2.5 Audio description (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

9.1.3 Adaptable
EN 301 549 clauseDetermination of conformance

9.1.3.1 Info and relationships

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

C.9.1.3.1 Info and relationships

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

9.1.3.2 Meaningful sequence

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

C.9.1.3.2 Meaningful sequence

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

9.1.3.3 Sensory characteristics

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

C.9.1.3.3 Sensory characteristics

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

9.1.3.4 Orientation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.4 Orientation.

C.9.1.3.4 Orientation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.4 Orientation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.3.4 Orientation.

9.1.3.5 Identify input purpose

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

C.9.1.3.5 Identify input purpose

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

9.1.4 Distinguishable
EN 301 549 clauseDetermination of conformance

9.1.4.1 Use of colour

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.1 Use of Color.

C.9.1.4.1 Use of colour

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.1 Use of Color.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.1 Use of Color.

9.1.4.2 Audio control

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.2 Audio Control.

C.9.1.4.2 Audio control

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.2 Audio Control.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.2 Audio Control.

9.1.4.3 Contrast (minimum)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

C.9.1.4.3 Contrast (minimum)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

9.1.4.4 Resize text

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.4 Resize text.

C.9.1.4.4 Resize text

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.4 Resize text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.4 Resize text.

9.1.4.5 Images of text

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.5 Images of Text.

C.9.1.4.5 Images of text

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.5 Images of Text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.5 Images of Text.

9.1.4.10 Reflow

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.10 Reflow.

C.9.1.4.10 Reflow

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.10 Reflow.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.10 Reflow.

9.1.4.11 Non-text contrast

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

C.9.1.4.11 Non-text contrast

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

9.1.4.12 Text spacing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

C.9.1.4.12 Text spacing

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.12 Text spacing.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.12 Text spacing.

9.1.4.13 Content on hover or focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

C.9.1.4.13 Content on hover or focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

9.2 Operable
9.2.1 Keyboard accessible
EN 301 549 clauseDetermination of conformance

9.2.1.1 Keyboard

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.1 Keyboard.

C.9.2.1.1 Keyboard

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.1.1 Keyboard.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.1.1 Keyboard.

9.2.1.2 No keyboard trap

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap.

C.9.2.1.2 No keyboard trap

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap.

9.2.1.4 Character key shortcuts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

C.9.2.1.4 Character key shortcuts

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts

9.2.2 Enough time
EN 301 549 clauseDetermination of conformance

9.2.2.1 Timing adjustable

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable.

C.9.2.2.1 Timing adjustable

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable.

9.2.2.2 Pause, stop, hide

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide.

C.9.2.2.2 Pause, stop, hide

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide.

9.2.3 Seizures and physical reactions
EN 301 549 clauseDetermination of conformance

9.2.3.1 Three flashes or below threshold

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold.

C.9.2.3.1 Three flashes or below threshold

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold.

9.2.4 Navigable
EN 301 549 clauseDetermination of conformance

9.2.4.1 Bypass blocks

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.1 Bypass Blocks.

C.9.2.4.1 Bypass blocks

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.1 Bypass Blocks.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.1 Bypass Blocks.

9.2.4.2 Page titled

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.2 Page Titled.

C.9.2.4.2 Page titled

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.2 Page Titled.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.2 Page Titled.

9.2.4.3 Focus Order

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.3 Focus Order.

C.9.2.4.3 Focus Order

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.3 Focus Order.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.3 Focus Order

9.2.4.4 Link purpose (in context)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context)-

C.9.2.4.4 Link purpose (in context)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

9.2.4.5 Multiple ways

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.5 Multiple Ways.

C.9.2.4.5 Multiple ways

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.5 Multiple Ways.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.5 Multiple Ways.

9.2.4.6 Headings and labels

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

C.9.2.4.6 Headings and labels

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

9.2.4.7 Focus visible

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

C.9.2.4.7 Focus visible

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

9.2.5 Input modalities
EN 301 549 clauseDetermination of conformance

9.2.5.1 Pointer gestures

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

C.9.2.5.1 Pointer gestures

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

9.2.5.2 Pointer cancellation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

C.9.2.5.2 Pointer cancellation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

9.2.5.3 Label in name

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

C.9.2.5.3 Label in name

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.3 Label in Name.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.5.3 Label in Name.

9.2.5.4 Motion actuation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

C.9.2.5.4 Motion actuation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

9.3 Understandable
9.3.1 Readable
EN 301 549 clauseDetermination of conformance

9.3.1.1 Language of page

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.1.1 Language of Page.

C.9.3.1.1 Language of page

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.1.1 Language of Page.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.1.1 Language of Page.

9.3.1.2 Language of parts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.1.2 Language of Parts.

C.9.3.1.2 Language of parts

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.1.2 Language of Parts.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.1.2 Language of Parts.

9.3.2 Predictable
EN 301 549 clauseDetermination of conformance

9.3.2.1 On focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.1 On Focus.

C.9.3.2.1 On focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.1 On Focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.2.1 On Focus.

9.3.2.2 On input

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.2 On Input.

C.9.3.2.2 On input

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.2 On Input.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.2.2 On Input.

9.3.2.3 Consistent navigation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.3 Consistent Navigation.

C.9.3.2.3 Consistent navigation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.3 Consistent Navigation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.2.3 Consistent Navigation.

9.3.2.4 Consistent identification

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.4 Consistent Identification.

C.9.3.2.4 Consistent identification

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.4 Consistent Identification.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.2.4 Consistent Identification.

9.3.3 Input assistance
EN 301 549 clauseDetermination of conformance

9.3.3.1 Error identification

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.1 Error Identification.

C.9.3.3.1 Error identification

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.1 Error Identification.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.3.1 Error Identification.

9.3.3.2 Labels or instructions

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

C.9.3.3.2 Labels or instructions

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

9.3.3.3 Error suggestion

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

C.9.3.3.3 Error suggestion

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

9.3.3.4 Error prevention (legal, financial, data)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data).

C.9.3.3.4 Error prevention (legal, financial, data)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data) .

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data).

9.4 Robust
9.4.1 Compatible
EN 301 549 clauseDetermination of conformance

9.4.1.1 Parsing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.1 Parsing.

C.9.4.1.1 Parsing

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 4.1.1 Parsing.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 4.1.1 Parsing.

9.4.1.2 Name, role, value

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value.

C.9.4.1.2 Name, role, value

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value.

9.4.1.3 Status messages

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

C.9.4.1.3 Status messages

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page does not fail WCAG 2.1 Success Criterion 4.1.3 Status Messages.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the web page does not contain content relevant to WCAG 2.1 Success Criterion 4.1.3 Status Messages.

9.5 WCAG 2.1 AAA Success Criteria

In addition to the Level AA success criteria, included in clauses 9.1 to 9.4, the Web Content Accessibility Guidelines include success criteria for Level AAA. These are listed in Annex - Table 9.1. Web authors and procurement accessibility specialists are encouraged to consider the WCAG 2.1 Level AAA success criteria that, when it is possible to apply them, may provide access beyond that required in the present document.

NOTE: The W3C states that "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content". Refer to Table 9.1: WCAG 2.1 Level AAA Success Criteria in Annex – Tables and figures (from EN 301 549).

C.9.5 WCAG 2.1 AAA Success Criteria

Clause 9.5 is informative only and contains no requirements requiring test.

9.6 WCAG conformance requirements

Where ICT is a web page, it shall satisfy all the following five WCAG 2.1 conformance requirements at Level AA [5].

1. Conformance level

2. Full pages

3. Complete processes

4. Only Accessibility-Supported Ways of Using Technologies

5. Non-interference

NOTE 1: A Web page that meets all of requirements 9.1 to 9.4, or where a Level AA conforming alternate version (as defined in WCAG 2.1 [5]) is provided, will meet conformance requirement 1.

NOTE 2: According to W3C: "WCAG 2.1 extends Web Content Accessibility Guidelines 2.0 [4], which was published as a W3C Recommendation December 2008. Content that conforms to WCAG 2.1 also conforms to WCAG 2.0, and therefore to policies that reference WCAG 2.0" [4].

NOTE 3: Conformance requirement 5 states that all content on the page, including content that is not otherwise relied upon to meet conformance, meets clauses 9.1.4.2, 9.2.1.2, 9.2.2.2 and 9.2.3.1.

C.9.6 WCAG conformance requirements

Type of assessment

Inspection

Pre-conditions

1. The ICT is a web page.

Procedure

1. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "1: Conformance level" at Level AA.

2. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "2: Full pages".

3. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "3: Complete processes".

4. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "4: Only Accessibility-Supported Ways of Using Technologies".

5. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "5: Non-interference".

Result

Pass: All checks are true

Fail: Any check is false

Not applicable: Pre-condition 1 is not met.

10 Non-web documents

EN 301 549 clauseDetermination of conformance

10.0 General (informative)

Requirements in clause 10 apply to documents:

  • documents that are not web pages;
  • documents that are not embedded in web pages; and
  • documents that are provided with web pages but are neither embedded nor rendered together with the web page from which they are provided (i.e. the present clause applies to downloadable documents).

Clause 9 provides requirements for documents that are in web pages or that are embedded in web pages and that are used in the rendering or that are intended to be rendered together with the web page in which they are embedded.

NOTE 1: Some examples of documents are letters, spreadsheets, emails, books, pictures, presentations, and movies that have an associated user agent such as a document reader, editor or media player.

NOTE 2: A single document may be composed of multiple files such as the video content, closed caption text, etc. This fact is not usually apparent to the end-user consuming the document/content.

NOTE 3: Documents require a user agent in order for the content to be presented to users. The requirements for user agents can be found in clause 11.

NOTE 4: The requirements for content that is part of software, can be found in clause 11.

NOTE 5: The success criteria set out in clause 10 are intended to harmonize with the Working Group Note [i.26] produced by the W3C's WCAG2ICT Task Force.

NOTE 6: "Void" clauses have been inserted in order to maintain alignment of the numbering in clauses 9, 10 and 11.

NOTE 7: Requirements in clause 10 also apply to documents that are protected using mechanisms such as digital signatures, encryption, password protection, and watermarks when they are presented to the user.

NOTE 8: It is best practice to provide meta data on the accessibility of the document within or separate to the document using WebSchemas/Accessibility 2.0 [i.38].

C.10.0 General (informative)

Clause 10.0 is advisory only and contains no requirements requiring test.

10.1 Perceivable
10.1.1 Text alternatives
EN 301 549 clauseDetermination of conformance

10.1.1.1 Non-text content

Where ICT is a non-web document, it shall satisfy the 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.

C.10.1.1.1 Non-text content

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.1.1 Non-text content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.1.1 Non-text content.

10.1.2 Time-based media
EN 301 549 clauseDetermination of conformance

10.1.2.1 Audio-only and video-only (prerecorded)

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

NOTE: The alternative can be provided directly in the document - or provided in an alternate version that meets the success criterion.

C.10.1.2.1 Audio-only and video-only (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

10.1.2.2 Captions (prerecorded)

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

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".

C.10.1.2.2 Captions (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

10.1.2.3 Audio description or media alternative (prerecorded)

Where ICT is a non-web document, 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.

C.10.1.2.3 Audio description or media alternative (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

10.1.2.4 Captions (live)

Where ICT is a non-web document, 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".

C.10.1.2.4 Captions (live)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

10.1.2.5 Audio description (prerecorded)

Where ICT is a non-web document, 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.

C.10.1.2.5 Audio description (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

10.1.3 Adaptable
EN 301 549 clauseDetermination of conformance

10.1.3.1 Info and relationships

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

NOTE: Where documents contain non-standard structure types (roles), it is best practice to map them to a standard structure type as a fall-back solution for the reader.

C.10.1.3.1 Info and relationships

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

10.1.3.2 Meaningful sequence

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

C.10.1.3.2 Meaningful sequence

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

10.1.3.3 Sensory characteristics

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

C.10.1.3.3 Sensory characteristics

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

10.1.3.4 Orientation

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

C.10.1.3.4 Orientation

Type of assessment

Inspection

Pre-conditions:

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.4 Orientation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.3.4 Orientation.

10.1.3.5 Identify input purpose

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

C.10.1.3.5 Identify input purpose

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

10.1.4 Distinguishable
EN 301 549 clauseDetermination of conformance

10.1.4.1 Use of colour

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.4.1 Use of Color.

C.10.1.4.1 Use of colour

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.1 Use of Color.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.1 Use of Color.

10.1.4.2 Audio control

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.1.

Table 10.1: Document success criterion: Audio control

If any audio in a document plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanismis available to control audio volume independently from the overall system volume level.

NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, all content in the document (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 document" "any content" with "any part of a document", "whole page" with "whole document", "on the Web page" with "in the document", removing "See Conformance Requirement 5: Non-Interference" and adding note 1.

C.10.1.4.2 Audio control

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.1.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met

10.1.4.3 Contrast (minimum)

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

C.10.1.4.3 Contrast (minimum)

Type of assessment: Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

10.1.4.4 Resize text

Where ICT is a non-web document, 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.

NOTE 3: It is best practice to use only fonts that allow for scaling without loss of quality (e.g. pixelized presentation). This applies in particular to embedded fonts.

C.10.1.4.4 Resize text

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.4 Resize text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.4 Resize text.

10.1.4.5 Images of text

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.

C.10.1.4.5 Images of text

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.5 Images of Text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.5 Images of Text.

10.1.4.10 Reflow

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.2.

Table 10.2: Document success criterion: Reflow

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 1280 CSS pixels wide at 400% zoom. For documents which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024px 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.

C.10.1.4.10 Reflow

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.2.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.1.4.11 Non-text contrast

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

C.10.1.4.11 Non-text contrast

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document that does not have a fixed size content layout area that is essential to the information being conveyed.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

10.1.4.12 Text spacing

Where ICT is a non-web document that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

C.10.1.4.12 Text spacing

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.12 Text spacing.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.12 Text spacing.

10.1.4.13 Content on hover or focus

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

C.10.1.4.13 Content on hover or focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

10.2 Operable
10.2.1 Keyboard accessible
EN 301 549 clauseDetermination of conformance

10.2.1.1 Keyboard

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 2.1.1 Keyboard.

C.10.2.1.1 Keyboard

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.1.1 Keyboard.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.1.1 Keyboard.

10.2.1.2 No keyboard trap

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.3.

Table 10.3: Document success criterion: No keyboard trap

If keyboard focus can be moved to a component of the document using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, it is necessary for all content in the document (whether or not it is used to meet other success criteria) to meet this success criterion.

NOTE 2: Standard exit methods may vary by platform. For example, on many desktop platforms, the Escape key is a standard method for exiting.

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap replacing "page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference" and with the addition of note 2 above and with note 1 above re-drafted to avoid the use of the word "must".

C.10.2.1.2 No keyboard trap

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.3.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.1.4 Character key shortcuts

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

C.10.2.1.4 Character key shortcuts

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure:

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

10.2.2 Enough time
EN 301 549 clauseDetermination of conformance

10.2.2.1 Timing adjustable

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.4.

Table 10.4: Document success criterion: Timing adjustable

For each time limit that is set by the document, at least one of the following is true:

  • Turn off: The user is allowed to turn off the time limit before encountering it; or
  • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception: The time limit is essential and extending it would invalidate the activity; or
  • 20 Hour Exception: The time limit is longer than 20 hours.

NOTE 1: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with WCAG 2.1 Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable replacing "the content" with "documents" and with the words "WCAG 2.1" added before the word "Success Criterion" in note 1 above.

C.10.2.2.1 Timing adjustable

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.4.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.2.2 Pause, stop, hide

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.5.

Table 10.5: Document success criterion: Pause, stop, hide

For moving, blinking, scrolling, or auto-updating information, all of the following are true:

  • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
  • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

NOTE 1: For requirements related to flickering or flashing content, refer to WCAG 2.1 Guideline 2.3.

NOTE 2: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, it is necessary for all content in the document (whether it is used to meet other success criteria or not) to meet this success criterion.

NOTE 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

NOTE 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

NOTE 5: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide replacing "page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference" in note 2 of the success criterion, with the words "WCAG 2.1" added before the word "Guideline" in note 1 above and with note 2 above re-drafted to avoid the use of the word "must".

C.10.2.2.2 Pause, stop, hide

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.5.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.2.2 Pause, stop, hide.

10.2.3 Seizures and physical reactions
EN 301 549 clauseDetermination of conformance

10.2.3.1 Three flashes or below threshold

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.6.

Table 10.6: Document success criterion: Three flashes or below threshold

Documents do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, it is necessary for all content in the document (whether it is used to meet other success criteria or not) to meet this success criterion.

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold replacing "Web pages" with "documents", "the whole page" with "the whole document", "the Web page" with "the document" and removing "See Conformance Requirement 5: Non-Interference" and with note 1 above re-drafted to avoid the use of the word "must".

C.10.2.3.1 Three flashes or below threshold

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.6.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.4 Navigable
EN 301 549 clauseDetermination of conformance

10.2.4.2 Document titled

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.7.

Table 10.7: Document success criterion: Document titled

Documents have titles that describe topic or purpose.

NOTE 1: The name of a document (e.g. document, media file) is a sufficient title if it describes the topic or purpose.

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.4.2 Page Titled replacing "Web pages" with "documents" and with the addition of note 1 above.

C.10.2.4.2 Document titled

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.7.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.4.3 Focus Order

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.8.

Table 10.8: Document success criterion: Focus order

If a document can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

NOTE: This success criterion is identical to the WCAG 2.1 Success Criterion 2.4.3 Focus Order replacing "Web page" with "document".

C.10.2.4.3 Focus Order

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.8.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.4.4 Link purpose (in context)

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

C.10.2.4.4 Link purpose (in context)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

10.2.4.6 Headings and labels

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

C.10.2.4.6 Headings and labels

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

10.2.4.7 Focus visible

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

C.10.2.4.7 Focus visible

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

10.2.5 Input modalities
EN 301 549 clauseDetermination of conformance

10.2.5.1 Pointer gestures

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.9.

Table 10.9: Document success criterion: Pointer gestures

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to documents that interpret pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

C.10.2.5.1 Pointer gestures

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.9

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.5.2 Pointer cancellation

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.10.

Table 10.10: Document success criterion: Pointer cancellation

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to a document that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

C.10.2.5.2 Pointer cancellation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the success criterion in Table 10.10

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.2.5.3 Label in name

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

C.10.2.5.3 Label in name

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.5.3 Label in Name.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.5.3 Label in Name.

10.2.5.4 Motion actuation

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

C.10.2.5.4 Motion actuation

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

10.3 Understandable
10.3.1 Readable
EN 301 549 clauseDetermination of conformance

10.3.1.1 Language of page

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.11.

Table 10.11: Document success criterion: Language of page

The default human language of each document can be programmatically determined.

NOTE: This success criterion is identical to the WCAG 2.1 Success Criterion 3.1.1 Language of Page replacing "web page" with "document".

C.10.3.1.1 Language of page

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.11.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.3.1.2 Language of parts

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.12.

Table 10.12: Document success criterion: Language of parts

The human language of each passage or phrase in the document can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

NOTE 1: There are some document technologies where there is no assistive technology supported method for marking the language for the different passages or phrases in the document, and it would not be possible to meet this success criterion with those technologies.

NOTE 2: Inheritance is one common method. For example a document provides the language that it is using and it can be assumed that all of the text or user interface elements within that document will be using the same language unless it is indicated.

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 3.1.2 Language of Parts replacing "content" with "document" and with the addition of notes 1 and 2 above.

C.10.3.1.2 Language of parts

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.12.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.3.2 Predictable
EN 301 549 clauseDetermination of conformance

10.3.2.1 On focus

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.2.1 On Focus.

NOTE: Some compound documents and their user agents are designed to provide significantly different viewing and editing functionality depending upon what portion of the compound document is being interacted with (e.g. a presentation that contains an embedded spreadsheet, where the menus and toolbars of the user agent change depending upon whether the user is interacting with the presentation content, or the embedded spreadsheet content). If the user uses a mechanism other than putting focus on that portion of the compound document with which they mean to interact (e.g. by a menu choice or special keyboard gesture), any resulting change of context would not be subject to this success criterion because it was not caused by a change of focus.

C.10.3.2.1 On focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 3.2.1 On Focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 3.2.1 On Focus.

10.3.2.2 On input

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.2.2 On Input.

C.10.3.2.2 On input

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 3.2.2 On Input.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 3.2.2 On Input.

10.3.3 Input assistance
EN 301 549 clauseDetermination of conformance

10.3.3.1 Error identification

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.3.1 Error Identification.

C.10.3.3.1 Error identification

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 3.3.1 Error Identification.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 3.3.1 Error Identification.

10.3.3.2 Labels or instructions

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

C.10.3.3.2 Labels or instructions

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

10.3.3.3 Error suggestion

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

C.10.3.3.3 Error suggestion

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 3.3.3 Error Suggestion">.

Result:

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 3.3.3 Error Suggestion

10.3.3.4 Error prevention (legal, financial, data)

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.13.

Table 10.13: Document success criterion: Error prevention (legal, financial, data)

For documents that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:

  • Reversible: Submissions are reversible.
  • Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
  • Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

NOTE: This success criterion is identical to the WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data) replacing "web pages" with "documents".

C.10.3.3.4 Error prevention (legal, financial, data)

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.13.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.4 Robust
10.4.1 Compatible
EN 301 549 clauseDetermination of conformance

10.4.1.1 Parsing

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.14.

Table 10.14: Document success criterion: Parsing

For documents that use markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

NOTE 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.

NOTE 2: Markup is not always available to assistive technology or to user selectable user agents such as browsers. In such cases, conformance to this provision would have no impact on accessibility as it can for web content where it is exposed.

NOTE 3: Examples of markup that is separately exposed and available to assistive technologies and to user agents include but are not limited to: documents encoded in HTML, ODF, and OOXML. In these examples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may directly open the document, (b) by assistive technologies using DOM APIs of user agents for these document formats.

NOTE 4: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.1 Parsing replacing "In content implemented using markup languages" with "For documents that use markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent" with the addition of notes 2 and 3 above.

C.10.4.1.1 Parsing

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.14.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.4.1.2 Name, role, value

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.15.

Table 10.15: Document success criterion: Name, role, value

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification.

NOTE 2: For document formats that support interoperability with assistive technology, standard user interface components often meet this success criterion when used according to the general design and accessibility guidance for the document format.

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value replacing the original WCAG 2.1 note with note 1 and with the addition of note 2 above.

C.10.4.1.2 Name, role, value

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the document does not fail the Success Criterion in Table 10.15.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

10.4.1.3 Status messages

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

C.10.4.1.3 Status messages

Type of assessment

Inspection

Pre-conditions

1. The ICT is a non-web document.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 4.1.3 Status Messages.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web document does not contain content relevant to WCAG 2.1 Success Criterion 4.1.3 Status Messages.

10.5 Caption positioning

Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.

C.10.5 Caption positioning

Clause 10.5 contains no requirements requiring test.

10.6 Audio description timing

Where ICT is a non-web document that contains synchronized media with audio description, the audio description should not interfere with relevant audio information in the synchronized media.

C.10.6 Audio description timing

Clause 10.6 contains no requirements requiring test.

11 Software

EN 301 549 clauseDetermination of conformance

11.0 General (informative)

This clause provides requirements for:

  • platform software;
  • software that provides a user interface including content that is in the software;
  • authoring tools;
  • software that operates as assistive technology.
  • mobile applications.

NOTE 1: User agents are examples of software that provide a user interface.

NOTE 2: The requirements for Web content, including software that is Web content, can be found in clause 9.

NOTE 3: The requirements for documents, that may be presented by user agents, can be found in clause 10.

NOTE 4: Although the accessibility of command line interfaces is not dealt with in the present document, accessibility may be achieved by context specific requirements, some of which may be found in clauses 5 or 11.

Requirements in clauses 11.1 to 11.5 apply to software:

  • that is not a web page;
  • not embedded in web pages nor used in the rendering or functioning of the page.

Clause 9 provides requirements for software that is in web pages or that is embedded in web pages and that is used in the rendering or that is intended to be rendered together with the web page in which it is embedded.

Some requirements in clauses 11.1 to 11.5 have different versions for open or closed functionality. In those cases, the corresponding clause will be divided into two subclauses.

The success criteria set out in clauses 11.1 to 11.5 are intended to harmonize with the W3C Working Group Note [i.26] produced by the W3C's WCAG2ICT Task Force.

NOTE 5: Software that provides a user interface includes its own content. Some examples of content in software include: the controls and text displayed in a menu bar of a graphical user interface application, images that appear in a toolbar, prompts spoken in an auditory user interface, other user interaction controls, and other text, graphics or material that is not loaded from outside the software.

C.11.0 General (informative)

Clause 11.0 is advisory only and contains no requirements requiring test.

11.1 Perceivable
11.1.1 Text alternatives
11.1.1.1 Non-text content
EN 301 549 clauseDetermination of conformance

11.1.1.1.1 Non-text content (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, 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.

C.11.1.1.1.1 Non-text content (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.1.1 Non-text Content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.1.1.1.2 Non-text content (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.6 (Speech output for non-text content).

C.11.1.1.1.2 Non-text content (closed functionality)

Type of assessment

Testing

Pre-conditions

1. The ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Non-text content is presented to users via speech output.

Procedure

1. Check that speech output is provided as an alternative for non-text content.

2. Check that the non-text content is not pure decoration.

3. Check that the non-text content is not used only for visual formatting.

4. Check that the speech output follows the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1 Non-text Content.

Result

Pass: Check (1 and 2 and 3 and 4 are true) or (1 and 2 are false) or (1 and 3 are false)

Fail: Checks (1 true and 2 false) or (1 true and 3 false) or (1 and 2 and 3 are true and 4 is false)

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.2 Time-based media
11.1.2.1 Audio-only and video-only (prerecorded)
EN 301 549 clauseDetermination of conformance

11.1.2.1.1 Audio-only and video-only (prerecorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading and where pre-recorded auditory information is not needed to enable the use of closed functions of ICT, 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.

Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)

Understanding Audio-only and Video-only (Prerecorded)

How to Meet 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-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
  • Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content

C.11.1.2.1.1 Audio-only and video-only (prerecorded - open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.2.1.2 Audio-only and video-only (prerecorded - closed functionality)
EN 301 549 clauseDetermination of conformance

11.1.2.1.2.1 Prerecorded audio-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the functionality of software that provides a user interface shall meet requirement 5.1.5 (Visual output for auditory information).

C.11.1.2.1.2.1 Prerecorded audio-only (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Pre-recorded auditory information is needed to enable the use of closed functions of ICT.

Procedure

1. Check that the visual information is equivalent to the pre-recorded auditory output.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.2.1.2.2 Prerecorded video-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

C.11.1.2.1.2.2 Prerecorded video-only (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Pre-recorded video content is needed to enable the use of closed functions of ICT.

4. Speech output is provided as non-visual access to non-text content displayed on closed functionality.

Procedure

1. Check that the speech output presents equivalent information for the pre-recorded video content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, 3 or 4 is not met.

11.1.2.2 Captions (prerecorded)

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

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".

C.11.1.2.2 Captions (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

11.1.2.3 Audio description or media alternative (prerecorded)
EN 301 549 clauseDetermination of conformance

11.1.2.3.1 Audio description or media alternative (prerecorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, 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.

C.11.1.2.3.1 Audio description or media alternative (prerecorded - open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

11.1.2.3.2 Audio description or media alternative (prerecorded - closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

C.11.1.2.3.2 Audio description or media alternative (prerecorded - closed functionality)

Type of assessment

Inspection

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Speech output is provided as non-visual access to non-text content displayed on closed functionality.

Procedure

1. Check that the speech output presents equivalent information for the pre-recorded video content.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, or 3 is not met.

11.1.2.4 Captions (live)

Where ICT is non-web software that provides a user interface, 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".

C.11.1.2.4 Captions (live)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

11.1.2.5 Audio description (prerecorded)

Where ICT is non-web software that provides a user interface, 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.

C.11.1.2.5 Audio description (prerecorded)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

11.1.3 Adaptable
11.1.3.1 Info and relationships
EN 301 549 clauseDetermination of conformance

11.1.3.1.1 Info and relationships (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

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).

C.11.1.3.1.1 Info and relationships (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.1.3.1.2 Info and relationships (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

C.11.1.3.1.2 Info and relationships (closed functionality)

Clause 11.1.3.1.2 is advisory only and contains no testable requirements.

11.1.3.2 Meaningful sequence
EN 301 549 clauseDetermination of conformance

11.1.3.2.1 Meaningful sequence (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

C.11.1.3.2.1 Meaningful sequence (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.1.3.2.2 Meaningful sequence (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

C.11.1.3.2.2 Meaningful sequence (closed functionality)

Clause 11.1.3.2.2 is advisory only and contains no testable requirements.

11.1.3.3 Sensory characteristics

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

C.11.1.3.3 Sensory characteristics

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

11.1.3.4 Orientation

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

C.11.1.3.4 Orientation

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.4 Orientation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.3.4 Orientation.

11.1.3.5 Identify input purpose
EN 301 549 clauseDetermination of conformance

11.1.3.5.1 Identify input purpose (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

C.11.1.3.5.1 Identify input purpose (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

Result

Pass: Check 1 is true

Fail: Check 1 is false

11.1.3.5.2 Identify input purpose (closed functionality)

Where ICT is non-web software that provides a user interface and is closed to assistive technologies, in at least one mode of operation the ICT shall present to the user, in an audio form, the purpose of each input field collecting information about the user when the input field serves a purpose identified in the WCAG 2.1 Input Purposes for User Interface Components section.

C.11.1.3.5.2 Identify input purpose (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

2. The software does not provide support to assistive technologies for screen reading

3. Auditory output is provided as non-visual access to closed functionality.

Procedure

1. Check that the auditory output is delivered by a mechanism included in or provided with the ICT.

2. Check that the auditory output is delivered by a personal headset that can be connected through a 3,5 mm audio jack or an industry standard connection without requiring the use of vision.

3. Check that the auditory output comprises of purposes from the Input Purposes for User Interface Components section.

Result

Pass: Checks (1 or 2) is true and 3 is true

Fail: Checks (1 and 2) are false or 3 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.4 Distinguishable
EN 301 549 clauseDetermination of conformance

11.1.4.1 Use of colour

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.4.1 Use of Color.

C.11.1.4.1 Use of colour

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.1 Use of Color.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.1 Use of Color

11.1.4.2 Audio control

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.1.

Table 11.1: Software success criterion: Audio control

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.

C.11.1.4.2 Audio control

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.1.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.1.4.3 Contrast (minimum)

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

C.11.1.4.3 Contrast (minimum)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

11.1.4.4 Resize text
EN 301 549 clauseDetermination of conformance

11.1.4.4.1 Resize text (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to enlargement features of platform or assistive technology, 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.

C.11.1.4.4.1 Resize text (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.4 Resize text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.4 Resize text.

11.1.4.4.2 Resize text (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).

NOTE: Because the text rendering support in a closed environment may be more limited than the support found in user agents for the Web, meeting 11.1.4.4.2 in a closed environment may place a much heavier burden on the content author.

C.11.1.4.4.2 Resize text (closed functionality)

Type of assessment

Inspection and measurement

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to enlargement features of platform or assistive technology.

3. A viewing distance is specified by the supplier.

Procedure

1. Measure the height of a capital letter H.

2. Check that it subtends an angle of at least 0,7 degrees at the specified viewing distance.

Result

Pass: Check 2 is true

Fail: Check 2 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.4.5 Images of text
EN 301 549 clauseDetermination of conformance

11.1.4.5.1 Images of text (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.

C.11.1.4.5.1 Images of text (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.5 Images of Text.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.5 Images of Text.

11.1.4.5.2 Images of text (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it does not need to meet the WCAG 2.1 Success Criterion 1.4.5 Images of Text because there is no need to impose a requirement on all closed functionality that text displayed on the screen actually be represented internally as text (as defined by WCAG 2.1), given that there is no interoperability with assistive technology.

C.11.1.4.5.2 Images of text (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Non-text content is presented to users via speech output.

Procedure

1. Check that speech output is provided as an alternative for non-text content.

2. Check that the non-text content is not pure decoration.

3. Check that the non-text content is not used only for visual formatting.

4. Check that the speech output follows the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1 Non-text Content.

Result

Pass: Check (1 and 2 and 3 and 4 are true) or (1 and 2 are false) or (1 and 3 are false)

Fail: Checks (1 true and 2 false) or (1 true and 3 false) or (1 and 2 and 3 are true and 4 is false)

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.1.4.10 Reflow

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.2.

Table 11.2: Document success criterion: Reflow

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 1280 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 1024 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.

C.11.1.4.10 Reflow

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.2

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.1.4.11 Non-text contrast

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

C.11.1.4.11 Non-text contrast

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

11.1.4.12 Text spacing

Where ICT is non-web software that provides a user interface and that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

C.11.1.4.12 Text spacing

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion WCAG 2.1 Success Criterion 1.4.12 Text spacing.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.12 Text spacing.

11.1.4.13 Content on hover or focus

Where ICT is a non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

C.11.1.4.13 Content on hover or focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

11.2 Operable
11.2.1 Keyboard accessible
11.2.1.1 Keyboard
EN 301 549 clauseDetermination of conformance

11.2.1.1.1 Keyboard (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to keyboards or a keyboard interface, it shall satisfy the WCAG 2.1 Success Criterion 2.1.1 Keyboard.

NOTE: This does not imply that software is required to directly support a keyboard or "keyboard interface". Nor does it imply that software is required to provide a soft keyboard. Underlying platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard and would comply.

C.11.2.1.1.1 Keyboard (open functionality)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

2. The software provides support to keyboards or a keyboard interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.1.1 Keyboard.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.1.1 Keyboard.

11.2.1.1.2 Keyboard (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

C.11.2.1.1.2 Keyboard (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to keyboards or keyboard interfaces.

Procedure

1. Check that all functionality of the user interface is operable without vision.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.2.1.2 No keyboard trap

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.3.

Table 11.3: Software success criterion: No keyboard trap

If keyboard focus can be moved to a component of the software using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

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, it is necessary for all content in the software (whether or not it is used to meet other success criteria) to meet this success criterion.

NOTE 2: Standard exit methods may vary by platform. For example, on many desktop platforms, the Escape key is a standard method for exiting.

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap replacing "content", "page" and "Web page" with "software", removing "See Conformance Requirement 5: Non-Interference" and with the addition of note 2 above " and with note 1 above re-drafted to avoid the use of the word "shall".

C.11.2.1.2 No keyboard trap

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.3.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.2.1.4 Character key shortcuts
EN 301 549 clauseDetermination of conformance

11.2.1.4.1 Character key shortcuts (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

C.11.2.1.4.1 Character key shortcuts (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

11.2.1.4.2 Character key shortcuts (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

C.11.2.1.4.2 Character key shortcuts (closed functionality)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

2. ICT functionality is closed to keyboards or keyboard interfaces.

Procedure

1. Check that all functionality is operable without vision.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.2.2 Enough time
EN 301 549 clauseDetermination of conformance

11.2.2.1 Timing adjustable

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.4.

Table 11.4: Software success criterion: Timing adjustable

For each time limit that is set by the software, at least one of the following is true:

  • Turn off: The user is allowed to turn off the time limit before encountering it; or
  • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception: The time limit is essential and extending it would invalidate the activity; or
  • 20 Hour Exception: The time limit is longer than 20 hours.

NOTE 1: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with WCAG 2.1 Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable replacing "the content" with "software" and with the words "WCAG 2.1" added before the word "Success Criterion" in note 1 above.

C.11.2.2.1 Timing adjustable

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.4.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.2.2.2 Pause, stop, hide

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.5.

Table 11.5: Software success criterion: Pause, stop, hide

For moving, blinking, scrolling, or auto-updating information, all of the following are true:

  • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
  • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

NOTE 1: For requirements related to flickering or flashing content, refer to WCAG 2.1 Guideline 2.3.

NOTE 2: This success criteria is applicable to all content in the software (whether or not there is an alternate accessible mode of operation of the software) 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 (including a user interface element that enables the user to activate the alternate accessible mode of operation).

NOTE 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

NOTE 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

NOTE 5: This is to be applied to all content. Any content, whether informative or decorative, that is updated automatically, blinks, or moves may create an accessibility barrier.

NOTE 6: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide replacing "page" and "Web page" with "software", removing "See Conformance Requirement 5: Non-Interference" in note 2 of the success criterion, with the words "WCAG 2.1" added before the word "Guideline" in note 1 above, with note 2 above re-drafted to avoid the use of the word "must" and with the addition of note 5 above.

C.11.2.2.2 Pause, stop, hide

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.5.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.2.3 Seizures and physical reactions
EN 301 549 clauseDetermination of conformance

11.2.3.1 Three flashes or below threshold

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.6.

Table 11.6: Software success criterion: Three flashes or below threshold

Software does not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

NOTE 1: This success criteria is applicable to all content in the software (whether or not there is an alternate accessible mode of operation of the software) 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 (including a user interface element that enables the user to activate the alternate accessible mode of operation).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold replacing "Web pages" with "software", "the whole page" with "the whole software", "the Web page" with "the software" and removing "See Conformance Requirement 5: Non-Interference" and with note 1 above re-drafted to avoid the use of the word "must".

C.11.2.3.1 Three flashes or below threshold

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.6.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.2.4 Navigable
EN 301 549 clauseDetermination of conformance

11.2.4.3 Focus order

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.7.

Table 11.7: Software success criterion: Focus order

If software can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

NOTE: This success criterion is identical to the WCAG 2.1 Success Criterion 2.4.3 Focus order replacing "Web page" with "software".

C.11.2.4.3 Focus order

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.7.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.2.4.4 Link purpose (in context)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

C.11.2.4.4 Link purpose (in context)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

11.2.4.6 Headings and labels

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

NOTE: In software, headings and labels are used to describe sections of content and controls respectively. In some cases it may be unclear whether a piece of static text is a heading or a label. But whether treated as a label or a heading, the requirement is the same: that if they are present they describe the topic or purpose of the item(s) they are associated with.

C.11.2.4.6 Headings and labels

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

11.2.4.7 Focus visible

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

C.11.2.4.7 Focus visible

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

11.2.5 Input modalities
EN 301 549 clauseDetermination of conformance

11.2.5.1 Pointer gestures

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.8.

Table 11.8: Software success criterion: Pointer gestures

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

C.11.2.5.1 Pointer gestures

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.8.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.2.5.2 Pointer cancellation

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.9.

Table 11.9: Software success criterion: Pointer cancellation

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

C.11.2.5.2 Pointer cancellation

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.9.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.2.5.3 Label in name
EN 301 549 clauseDetermination of conformance

11.2.5.3.1 Label in name (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

C.11.2.5.3.1 Label in name (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.5.3 Label in Name.

Result

Pass: Check 1 is true

Fail: Check 1 is false

11.2.5.3.2 Label in name (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it should meet requirement 5.1.3.3 (Auditory output correlation).

C.11.2.5.3.2 Label in name (closed functionality)

Clause 11.2.5.3.2 is informative only and contains no requirements requiring test.

EN 301 549 clauseDetermination of conformance

11.2.5.4 Motion actuation

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

C.11.2.5.4 Motion actuation

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

11.3 Understandable
11.3.1 Readable
11.3.1.1 Language of software
EN 301 549 clauseDetermination of conformance

11.3.1.1.1 Language of software (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.10.

Table 11.10: Software success criterion: Language of software

The default human language of software can be programmatically determined.

NOTE 1: Where software platforms provide a "locale / language" setting, applications that use that setting and render their interface in that "locale / language" would comply with this success criterion. Applications that do not use the platform "locale / language" setting but instead use an accessibility-supported method for exposing the human language of the software would also comply with this success criterion. Applications implemented in technologies where assistive technologies cannot determine the human language and that do not support the platform "locale / language" setting may not be able to meet this success criterion in that locale / language.

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 3.1.1 Language of page, replacing "each web page" with "software" and with the addition of note 1 above.

C.11.3.1.1.1 Language of software (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.10.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.3.1.1.2 Language of software (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.14 (Spoken languages).

C.11.3.1.1.2 Language of software (closed functionality)

Type of assessment

Testing

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. The speech output is provided as non-visual access to closed functionality.

4. The speech output is not proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

5. The content is not generated externally and is under the control of the ICT vendor.

6. The displayed languages can be selected using non-visual access.

7. The user has not selected a speech language that is different from the language of the displayed content.

Procedure

1. Check that the speech output is in the same human language of the displayed content provided.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1, 2, 3, 4, 5, 6 or 7 is not met.

11.3.2 Predictable
EN 301 549 clauseDetermination of conformance

11.3.2.1 On focus

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 3.2.1 On Focus.

NOTE: Some compound documents and their user agents are designed to provide significantly different viewing and editing functionality depending upon what portion of the compound document is being interacted with (e.g. a presentation that contains an embedded spreadsheet, where the menus and toolbars of the user agent change depending upon whether the user is interacting with the presentation content, or the embedded spreadsheet content). If the user uses a mechanism other than putting focus on that portion of the compound document with which they mean to interact (e.g. by a menu choice or special keyboard gesture), any resulting change of context would not be subject to this success criterion because it was not caused by a change of focus.

C.11.3.2.1 On focus

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 3.2.1 On Focus.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 3.2.1 On Focus.

11.3.2.2 On input

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 3.2.2 On Input.

C.11.3.2.2 On input

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 3.2.2 On Input.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 3.2.2 On Input.

11.3.3 Input assistance
11.3.3.1 Error identification
EN 301 549 clauseDetermination of conformance

11.3.3.1.1 Error identification (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 3.3.1 Error Identification.

C.11.3.3.1.1 Error identification (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 3.3.1 Error Identification.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 3.3.1 Error Identification.

11.3.3.1.2 Error Identification (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.15 (Non-visual error identification).

C.11.3.3.1.2 Error Identification (closed functionality)

Type of assessment

Testing

Pre-conditions

1. ICT is non-web software that provides a user interface.

2. The user interface is closed to assistive technologies for screen reading.

3. Speech output is provided as non-visual access to closed functionality.

4. An input error is automatically detected.

Procedure

1. Check that speech output identifies the item that is in error.

2. Check that the speech output describes the item that is in error.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or check 2 false

Not applicable: Pre-condition 1, 2,3 or 4 is not met.

11.3.3.2 Labels or instructions

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

C.11.3.3.2 Labels or instructions

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

11.3.3.3 Error suggestion

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

C.11.3.3.3 Error suggestion

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

11.3.3.4 Error prevention (legal, financial, data)

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.11.

Table 11.11: Software success criterion: Error prevention (legal, financial, data)

For software that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:

1. Reversible: Submissions are reversible.

2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.

3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

NOTE: This success criterion is identical to the WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data) replacing "web pages" with "software".

C.11.3.3.4 Error prevention (legal, financial, data)

Type of assessment

Inspection

Pre-conditions

1. The ICT is non-web software that provides a user interface.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.11.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.4 Robust
11.4.1 Compatible
11.4.1.1 Parsing
EN 301 549 clauseDetermination of conformance

11.4.1.1.1 Parsing (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the success criterion in Table 11.12.

Table 11.12: Software success criterion: Parsing

For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

NOTE 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.

NOTE 2: Markup is not always available to assistive technology or to user selectable user agents such as browsers. In such cases, conformance to this provision would have no impact on accessibility as it can for web content where it is exposed.

NOTE 3: Examples of markup that is separately exposed and available to assistive technologies and to user agents include but are not limited to: documents encoded in HTML, ODF, and OOXML. In these examples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may directly open the document, (b) by assistive technologies using DOM APIs of user agents for these document formats.

NOTE 4: Examples of markup used internally for persistence of the software user interface that are never exposed to assistive technology include but are not limited to: XUL, GladeXML, and FXML. In these examples assistive technology only interacts with the user interface of generated software.

NOTE 5: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.1 Parsing replacing "In content implemented using markup languages" with "For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent" with the addition of notes 2, 3 and 4 above.

C.11.4.1.1.1 Parsing (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.12.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.4.1.1.2 Parsing (closed functionality)

Not applicable.

NOTE: Where ICT is non-web software that provides a user interface which is closed to all assistive technology it shall not have to meet the "Parsing" success criterion in Table 11.10 because the intent of this success criterion is to provide consistency so that different user agents or assistive technologies will yield the same result.

C.11.4.1.1.2 Parsing (closed functionality)

Clause 11.4.1.1.2 contains no requirements requiring test.

11.4.1.2 Name, role, value
EN 301 549 clauseDetermination of conformance

11.4.1.2.1 Name, role, value (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the success criterion in Table 11.13.

Table 11.13: Software success criterion: Name, role, value

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification.

NOTE 2: For conforming to this success criterion, it is usually best practice for software user interfaces to use the accessibility services provided by platform software. These accessibility services enable interoperability between software user interfaces and both assistive technologies and accessibility features of software in standardised ways. Most platform accessibility services go beyond programmatic exposure of name and role, and programmatic setting of states, properties and values (and notification of same), and specify additional information that could or should be exposed and / or set (for instance, a list of the available actions for a given user interface component, and a means to programmatically execute one of the listed actions).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value replacing the original WCAG 2.1 note with: "This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification." and the addition of note 2 above.

C.11.4.1.2.1 Name, role, value (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail the Success Criterion in Table 11.13.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.4.1.2.2 Name, role, value (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to all assistive technology it shall not have to meet the "Name, role, value" success criterion in Table 11.11 because this success criterion requires information in a programmatically determinable form.

C.11.4.1.2.2 Name, role, value (closed functionality)

Clause 11.4.1.2.2 contains no testable requirements.

11.4.1.3 Status messages
EN 301 549 clauseDetermination of conformance

11.4.1.3.1 Status messages (open functionality)

Where tWhere ICT is non-web software, it shall satisfy satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

C.11.4.1.3.1 Status messages (open functionality)

Type of assessment

Inspection

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.

Procedure

1. Check that the software does not fail WCAG 2.1 Success Criterion 4.1.3 Status messages.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met, or the non-web software does not contain content relevant to WCAG 2.1 Success Criterion 4.1.3 Status messages.

11.4.1.3.2 Status messages (closed functionality)

Not applicable.

C.11.4.1.3.2 Status messages (closed functionality)

Clause 11.4.1.3.2 contains no testable requirements.

11.5 Interoperability with assistive technology
EN 301 549 clauseDetermination of conformance

11.5.1 Closed functionality

Where the closed functionality of software conforms to clause 5.1 (Closed functionality) it shall not be required to conform with clause 11.5.2 to clause 11.5.2.17.

C.11.5.1 Closed functionality

Type of assessment

Inspection

Pre-conditions

1. The software has closed functionality.

Procedure

1. Check that the closed functionality conforms to clause 5.1.

Result

If check 1 is true, the software is not required to conform to clauses 11.5.2 to 11.5.17

If check 1 is false the software is required to conform to clauses 11.5.2 to 11.5.17

Not applicable: Pre-condition 1 is not met.

11.5.2 Accessibility services
EN 301 549 clauseDetermination of conformance

11.5.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Platform software should support requirements 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality of software providing user interfaces when using platform services.

NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 3: User interface services that provide accessibility support by default are considered to be part of the services provided to conform to this clause (e.g. the service for creating a new user interface element provides role, state, boundary, name and description).

NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

NOTE 5: Within specific programming environments, the technical attributes associated with the user interface properties described in clauses 11.5.2.5 to 11.5.2.17 might have different names than those used within the clauses.

C.11.5.2.1 Platform accessibility service support for software that provides a user interface

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is platform software.

Procedure

1. Check that the platform software documentation includes information about platform services that may be used by software that provides a user interface to interoperate with assistive technology.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.2 Platform accessibility service support for assistive technologies

Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.

Platform software should support the requirements of clauses 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirement are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.

NOTE 2: The definition of platform in clause 3.1 applies to software that provides services to other software, including but not limited to, operating systems, web browsers, virtual machines.

NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 4: Typically these services belong to the same set of services that are described in clause 11.5.2.1.

NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

C.11.5.2.2 Platform accessibility service support for assistive technologies

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is platform software.

Procedure

1. Check that the platform software documentation includes information about platform accessibility services that enables assistive technology to interoperate with software that provides a user interface running on the platform software.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.3 Use of accessibility services

Where the software provides a user interface it shall use the applicable documented platform accessibility services. If the documented platform accessibility services do not allow the software to meet the applicable requirements of clauses 11.5.2.5 to 11.5.2.17, then software that provides a user interface shall use other documented services to interoperate with assistive technology.

NOTE: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

It is best practice to develop software using toolkits that automatically implement the underlying platform accessibility services.

C.11.5.2.3 Use of accessibility services

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

Procedure

1. Check that the software uses the applicable documented platform accessibility services.

2. Check that the software can meet the applicable requirements 11.5.2.5 to 11.5.2.17 whilst using the documented platform accessibility services.

3. Check that the software can meet requirements 11.5.2.5 to 11.5.2.17 whilst using the documented platform accessibility services and other documented services.

Result

Pass: Check 1 is true and check 2 or check 3 is true

Fail: Check 1 or check 3 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

NOTE 2: Assistive technology can also use other documented accessibility services.

C.11.5.2.4 Assistive technology

Type of assessment

Inspection

Pre-conditions

1. The ICT is assistive technology.

Procedure

1. Check that the assistive technology uses the documented platform accessibility services.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

C.11.5.2.5 Object information

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

Procedure

1. Check that the user interface element's role is programmatically determinable by assistive technologies.

2. Check that the user interface element's state(s) is programmatically determinable by assistive technologies.

3. Check that the user interface element's boundary is programmatically determinable by assistive technologies.

4. Check that the user interface element's name is programmatically determinable by assistive technologies.

5. Check that the user interface element's description is programmatically determinable by assistive technologies.

Result

Pass: Checks 1, 2, 3, 4 and 5 are true

Fail: Check 1 or 2 or 3 or 4 or 5 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

C.11.5.2.6 Row, column, and headers

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are data tables in the user interface.

Procedure

1. Select a data table in which the tests are to be performed.

2. Check that each cell's row is programmatically determinable by assistive technologies.

3. Check that each cell's column is programmatically determinable by assistive technologies.

4. Check that each cell's row header, if the row header exists, is programmatically determinable by assistive technologies.

5. Check that each cell's column header, if the column header exists, is programmatically determinable by assistive technologies.

Result

Pass: Checks 2, 3, 4 and 5 are true

Fail: Check 2 or 3 or 4 or 5 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.5.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

C.11.5.2.7 Values

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that can have values.

Procedure

1. Select a user interface element that can have a value.

2. Check that the current value is programmatically determinable by assistive technologies.

3. If the user interface element conveys information about a range of values, check that the minimum value is programmatically determinable by assistive technologies.

4. If the user interface element conveys information about a range of values, check that the maximum value is programmatically determinable by assistive technologies.

Result

Pass: Checks 2, 3 and 4 are true

Fail: Check 2 or 3 or 4 is false

Not applicable: Pre-condition 1 or 2 is not met

11.5.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.

C.11.5.2.8 Label relationships

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that are labels of other user interface elements.

Procedure

1. Obtain the information of each user interface element.

2. Check that the user interface element's information includes the relationship with the user interface element that is its label, if the current user interface element has a label, and that this relationship is programmatically determinable by assistive technologies.

3. Check that the user interface element's information includes the relationship with the user interface element that it is labelling, if the current user interface element is a label, and that this relationship is programmatically determinable by assistive technologies.

Result

Pass: Checks 2 or 3 are true

Fail: Check 2 and 3 are false

Not applicable: Pre-condition 1 or 2 is not met.

11.5.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

C.11.5.2.9 Parent-child relationships

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that are parents of other user interface elements in a hierarchical structure.

Procedure

1. For user interface elements that have a parent, check that the user interface element's information includes the relationship with the user interface element that is its parent.

2. Check that the user interface elements that are parents of the user interface element selected in check 1, include the relationship with the user interface elements that are its children in their information, and that this relationship is programmatically determinable by assistive technologies.

3. For user interface elements that are a parent of other user interface elements, check that the user interface element's information includes the relationship with the user interface elements that are its children, and that this relationship is programmatically determinable by assistive technologies.

4. Check that the user interface elements that are a child of the user interface element selected in check 3, include the relationship with the user interface elements that are its parents in their information, and that this relationship is programmatically determinable by assistive technologies.

Result

Pass: Checks 1 or 2 is true and check 3 or 4 is true

Fail: Checks 1 and 2 are false or check 3 and 4 are false

Not applicable: Pre-condition 1 or 2 is not met.

NOTE: For this requirement it is enough that one of the two directions of a parent-child relationship is programmatically determinable. This is the reason why the requirement checks are in pairs and why the requirement is met if one member of each pair is true.

11.5.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

C.11.5.2.10 Text

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There is text rendered to the screen.

Procedure

1. For instances of text rendered to the screen, check that the text's information includes its text content, and that this information is programmatically determinable by assistive technologies.

2. For instances of text rendered to the screen, check that the text's information includes its attributes, and that this information is programmatically determinable by assistive technologies.

3. For instances of text rendered to the screen, check that the text's information includes its boundary, and that this information is programmatically determinable by assistive technologies.

Result

Pass: Checks 1, 2 and 3 are true

Fail: Check 1 or 2 or 3 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.5.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

C.11.5.2.11 List of available actions

Type of assessment

Inspection

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that have actions that can be executed by the user.

Procedure

1. Check that the user interface element's information includes the list of actions that can be executed.

2. Check that this list is programmatically determinable by assistive technologies.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.5.2.12 Execution of available actions

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

C.11.5.2.12 Execution of available actions

Type of assessment

Inspection and testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that have actions that can be executed by the user.

3. The security requirements permit assistive technology to programmatically execute user actions.

Procedure

1. Check that the user interface element's information includes the list of actions that can be executed by assistive technologies according to 11.5.2.11.

2. Check that all the actions in the list can successfully be executed by assistive technologies.

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.5.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

C.11.5.2.13 Tracking of focus and selection attributes

Type of assessment

Inspection and testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that enable text editing.

Procedure

1. Check that the user interface element's information includes mechanisms to track focus, text insertion point and selection attributes.

2. Check that this information is programmatically determinable by assistive technologies.

3. Activate those tracking mechanisms.

4. As a user, use the text editing functionality in the evaluated software product.

5. Check that the tracking of focus, text insertion point and selection attributes work.

Result

Pass: Checks 2 and 5 are true

Fail: Check 1 or 5 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.5.2.14 Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

C.11.5.2.14 Modification of focus and selection attributes

Type of assessment

Testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements that can receive focus or that enable text editing.

3. The security requirements permit platform software to programmatically modify focus, text insertion point and selection attributes of user interface elements.

Procedure

1. For user interface elements that can receive focus and where the focus can be modified by a user without the use of assistive technology, check that the focus can be programmatically modified by assistive technologies.

2. For user interface elements that enable text editing by a user without the use of assistive technology, check that the position of the text insertion point can be programmatically modified by assistive technologies.

3. For user interface elements that enable text editing, check that the selection attributes can be programmatically modified by assistive technologies where they can be modified by user without the use of assistive technology.

Result

Pass: All checks are true

Fail: Any check is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.5.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

C.11.5.2.15 Change notification

Type of assessment

Inspection and testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

Procedure

1. Activate notifications of changes in the user interface elements.

2. Check that notifications about changes in object information (role, state, boundary, name and description) are sent to assistive technologies, if this information changes in the software user interface.

3. Check that notifications about changes in row, column and headers of data tables are sent to assistive technologies, if this information changes in the software.

4. Check that notifications about changes in values (current value, minimum value and maximum value) are sent, if this information changes in the software.

5. Check that notifications about changes in label relationships are sent to assistive technologies, if this information changes in the software.

6. Check that notifications about changes in parent-child relationships are sent to assistive technologies, if this information changes in the software.

7. Check notifications about changes in text (text contents, text attributes and the boundary of text rendered to the screen) are sent to assistive technologies, if this information changes in the software.

8. Check that notifications about changes in the list of available actions are sent to assistive technologies, if this information changes in the software.

9. Check that notifications about changes in focus, text insertion point and selection attributes are sent to assistive technologies, if this information changes in the software.

Result

Pass: Checks 2, 3, 4, 5, 6, 7, 8 and 9 are true

Fail: Check 2, 3, 4, 5, 6, 7, 8 or 9 is false

Not applicable: Pre-condition 1 is not met.

11.5.2.16 Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

C.11.5.2.16 Modifications of states and properties

Type of assessment

Testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements whose state or properties can be modified by a user without the use of assistive technology.

3. The security requirements permit assistive technology to programmatically modify states and properties of user interface elements.

Procedure

1. Check that the state of user interface elements, whose state can be modified by a user without the use of assistive technology, can be programmatically modified by assistive technologies.

2. Check the properties of user interface elements, whose properties can be modified by a user without the use of assistive technologies, can be programmatically modified by assistive technologies.

Result

Pass: All checks are true

Fail: Any check is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

C.11.5.2.17 Modifications of values and text

Type of assessment

Testing

Pre-conditions

1. The software evaluated is software that provides a user interface.

2. There are user interface elements whose values or text can be modified by a user without the use of assistive technology.

3. The security requirements permit assistive technology to programmatically modify values and text of user interface elements.

Procedure

1. Check that the values of user interface elements, whose values can be modified by a user without the use of assistive technology, can be modified by assistive technologies using the input methods of the platform.

2. Check that the text of user interface elements, whose text can be modified by a user without the use of assistive technology, can be modified by assistive technologies using the input methods of the platform.

Result

Pass: all checks are true

Fail: any check is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.6 Documented accessibility usage
EN 301 549 clauseDetermination of conformance

11.6.1 User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

C.11.6.1 User control of accessibility features

Type of assessment

Testing

Pre-conditions

1. There are platform features that are defined in the platform documentation as accessibility features intended for users.

Procedure

1. Check that sufficient modes of operation exist where user control over platform features, that are defined in the platform documentation as accessibility features intended for users, is possible.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.6.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

C.11.6.2 No disruption of accessibility features

Type of assessment

Testing

Pre-conditions

1. There are platform features that are defined in the platform documentation as accessibility features.

Procedure

1. Check if software that provides a user interface disrupts normal operation of platform accessibility features.

2. Check if the disruption was specifically requested or confirmed by the user.

Result

Pass: Check 1 is false or both checks are true

Fail: Check 1 is true and check 2 is false

Not applicable: Pre-condition 1 is not met.

11.7 User preferences

Where software is not designed to be isolated from its platform, and provides a user interface, that user interface shall follow the values of the user preferences for platform settings for: units of measurement, colour, contrast, font type, font size, and focus cursor except where they are overridden by the user.

NOTE 1: Software that is isolated from its underlying platform has no access to user settings in the platform and thus cannot adhere to them.

NOTE 2: For web content, the underlying platform is the user agent.

NOTE 3: This does not preclude the software from having additional values for a setting as long as there is one mode where the application will follow the system settings even if more restricted.

C.11.7 User preferences

Type of assessment

Inspection and Testing

Pre-conditions

1. The software is software that provides a user interface.

Procedure

1. Check if the software provides sufficient modes of operation that uses user preferences for platform settings for colour, contrast, font type, font size, and focus cursor.

2. Check that the software documentation indicates that the software is designed to be isolated from its underlying platform.

Result

Pass: Check 1 is true or Check 1 is false and check 2 is true

Fail: Check 1 is false and check 2 is false

Not applicable: Pre-condition 1, 2 or 3 is not met.

11.8 Authoring tools
EN 301 549 clauseDetermination of conformance

11.8.1 Content technology

Authoring tools shall conform to clauses 11.8.2 to 11.8.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.

C.11.8.1 Content technology

Type of assessment

Inspection and Testing

Pre-conditions

1. The software is an authoring tool.

2. The output format of the authoring tool supports information required for accessibility.

Procedure

1. Check if the authoring tool conforms to 11.8.2 to 11.8.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

NOTE: Where the output format of the authoring tool does not support certain types of information required for accessibility, con with requirements that relate to that type of information is not required.

11.8.2 Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

NOTE: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

C.11.8.2 Accessible content creation

Type of assessment

Inspection and Testing

Pre-conditions

1. The software is an authoring tool.

Procedure

1. Check if the authoring tool has features that enable and guide the production of content that conforms to clauses 9 (Web) and 10 (Non-web documents).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

11.8.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

C.11.8.3 Preservation of accessibility information in transformations

Type of assessment

Inspection and Testing

Pre-conditions

1. The software is an authoring tool.

2. The authoring tool provides restructuring transformations or re-coding transformations.

Procedure

1. For a restructuring transformation, check if the accessibility information is preserved in the output.

2. For a restructuring transformation, check if the content technology supports accessibility information for the restructured form of the information.

3. For a re-coding transformation, check if the accessibility information is preserved in the output.

4. For a re-coding transformation, check if the accessibility information is supported by the technology of the re-coded output.

Result

Pass: Check 1 is true or checks 1 and 2 are false or check 3 is true or checks 3 and 4 are false

Fail: Check 1 is false and check 2 is true

Not applicable: Pre-condition 1 or 2 is not met.

11.8.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

NOTE: This does not preclude automated and semi-automated repair which is possible (and encouraged) for many types of content accessibility problems.

C.11.8.4 Repair assistance

Type of assessment

Inspection

Pre-conditions

1. The software is an authoring tool.

2. The accessibility checking functionality of the authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable.

Procedure

1. The authoring tool provides repair suggestions when content does not meet a requirement of clauses 9 or 10 (as applicable).

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

11.8.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.

C.11.8.5 Templates

Type of assessment

Inspection

Pre-conditions

1. The software is an authoring tool.

2. The authoring tool provides templates.

Procedure

1. Check that the authoring tool provides at least one template that supports the creation of content that conforms to requirements of clauses 9 (Web content) or 10 (Documents) as applicable.

2. Check that at least one template identified in step 1 is available and is identified as conforming to clauses 9 or 10 (as applicable).

Result

Pass: Checks 1 and 2 are true

Fail: Check 1 or 2 is false

Not applicable: Pre-condition 1 or 2 is not met.

NOTE: The identification as conforming to the requirements of clauses 9 or 10 (as applicable) described in check 2 may be described in terms such as "Conformant to WCAG 2.1". Where the identification does not explicitly state that all of the requirements identified in clauses 9 or 10 (as appropriate) are covered, it may be necessary to use the template to create a web site or document and then test that web site or document according to the requirements of clauses 9 or 10 to provide full assurance that the template behaves as required.

12 Documentation and support services

12.1 Product documentation
EN 301 549 clauseDetermination of conformance

12.1.1 Accessibility and compatibility features

Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.

NOTE 1: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

NOTE 2: It is best practice to use WebSchemas/Accessibility 2.0 [i.38] to provide meta data on the accessibility of the ICT.

NOTE 3: The accessibility statement and help pages are both examples of the provision of product information.

C.12.1.1 Accessibility and compatibility features

Type of assessment

Inspection

Pre-conditions

1. Product documentation is supplied with the ICT.

Procedure

1. Check that product documentation provided with the ICT lists and explains how to use the accessibility and compatibility features of the ICT.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

1. a Web format that conforms to the requirements of clause 9, or

2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which is accessible.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

C.12.1.2 Accessible documentation

Type of assessment

Inspection

Pre-conditions

1. Product documentation in electronic format is supplied with the ICT.

Procedure

1. Check that product documentation in electronic format provided with the ICT conforms to the requirements of clauses 9 or 10 as appropriate.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

12.2 Support services
EN 301 549 clauseDetermination of conformance

12.2.1 General (informative)

ICT support services include, but are not limited to: help desks, call centres, technical support, relay services and training services.

C.12.2.1 General (informative)

Clause 12.2.1 is informative only and contains no requirements requiring test.

12.2.2 Information on accessibility and compatibility features

ICT support services shall provide information on the accessibility and compatibility features that are included in the product documentation.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

C.12.2.2 Information on accessibility and compatibility features

Type of assessment

Inspection

Pre-conditions

1. ICT support services are provided.

Procedure

1. Check that the ICT support services provide information on the accessibility and compatibility features that are included in the product documentation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

12.2.3 Effective communication

ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.

C.12.2.3 Effective communication

Type of assessment

Inspection

Pre-conditions

1. ICT support services are provided.

Procedure

1. Check that the ICT support services accommodate the communication needs of individuals with disabilities either directly or through a referral point.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

NOTE: The provision of any level of support for the communication needs of individuals with disabilities constitutes a pass of this requirement. Suppliers may wish to provide further information about the level of support that is provided to enable the adequacy and quality of the support to be judged.

12.2.4 Accessible documentation

Documentation provided by support services shall be made available in at least one of the following electronic formats:

1. a Web format that conforms to clause 9; or

2. a non-web format that conforms to clause 10.

NOTE 1: This does not preclude the possibility of also providing the documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

C.12.2.4 Accessible documentation

Type of assessment

Inspection

Pre-conditions

1. Documentation is provided by the ICT support services.

Procedure

1. Check that documentation in electronic format provided by the ICT support services conforms to the requirements of clauses 9 or 10 as appropriate.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13 ICT providing relay or emergency service access

13.1 Relay services requirements
EN 301 549 clauseDetermination of conformance

13.1.1 General (informative)

Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.

It is best practice to meet the applicable relay service requirements of ETSI ES 202 975 [i.5].

C.13.1.1 General (informative)

Clause 13.1.1 is informative only and contains no requirements requiring test.

13.1.2 Text relay services

Where ICT is intended to provide a text relay service, the text relay service shall enable text users and speech users to interact by providing conversion between the two modes of communication.

C.13.1.2 Text relay services

Type of assessment

Inspection

Pre-conditions

1. The service is a text relay service.

Procedure

1. Check that the service enables text users and speech users to interact by providing conversion between the two modes of communication.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13.1.3 Sign relay services

Where ICT is intended to provide a sign relay service, the sign relay service shall enable sign language users and speech users to interact by providing conversion between the two modes of communication.

NOTE: Sign relay services are also sometimes referred to as sign language relay services or video relay services.

C.13.1.3 Sign relay services

Type of assessment

Inspection

Pre-conditions

1. The service is a sign relay service.

Procedure

1. Check that the service enables sign language users and speech users to interact by providing conversion between the two modes of communication.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13.1.4 Lip-reading relay services

Where ICT is intended to provide a lip-reading relay service, the lip-reading service shall enable lip-readers and voice telephone users to interact by providing conversion between the two modes of communication.

C.13.1.4 Lip-reading relay services

Type of assessment

Inspection

Pre-conditions

1. The service is a lip-reading relay service.

Procedure

1. Check that the service enables lip-readers and voice telephone users to interact by providing conversion between the two modes of communication.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13.1.5 Captioned telephony services

Where ICT is intended to provide a captioned telephony service, the captioned telephony service shall assist a deaf or hard of hearing user in a spoken dialogue by providing text captions translating the incoming part of the conversation.

C.13.1.5 Captioned telephony services

Type of assessment

Inspection

Pre-conditions

1. The service is a captioned telephony service.

Procedure

1. Check that the service assists a deaf or hard of hearing user in a spoken dialogue by providing text captions translating the incoming part of the conversation.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13.1.6 Speech to speech relay services

Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable speech or cognitively impaired telephone users and any other user to communicate by providing assistance between them.

C.13.1.6 Speech to speech relay services

Type of assessment

Inspection

Pre-conditions

1. The service is a speech to speech relay service.

Procedure

1. Check that the service enables enable speech or cognitively impaired telephone users and any other user to communicate by providing assistance between them.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 is not met.

13.2 Access to relay services

Where ICT systems support two-way communication, and the system is specified for use with relay services, access to those relay services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the relay service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access by persons with disabilities.

NOTE 2: The system may be specified as needing to work with relay services by, for example: procurers, regulators, or product specifications.

C.13.2 Access to relay services

Type of assessment

Inspection

Pre-conditions

1. The ICT system supports two-way communication.

2. A set of relay services for two-way communication is specified.

Procedure

1. Check that the system does not prevent access to those relay services for incoming and outgoing calls.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met.

13.3 Access to emergency services

Where ICT systems support two-way communication, and the system is specified for use with emergency services, access to those emergency services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the emergency service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access to the emergency service by persons with disabilities.

NOTE 2: The system may be specified as needing to work with emergency services by, for example: procurers, regulators, or product specifications.

C.13.3 Access to emergency services

Type of assessment

Inspection

Pre-conditions

1. The ICT system supports two-way communication.

2. A set of emergency services for two-way communication is specified.

Procedure

1. Check that the system does not prevent access to those emergency services for outgoing and incoming calls.

Result

Pass: Check 1 is true

Fail: Check 1 is false

Not applicable: Pre-condition 1 or 2 is not met

Annex - Tables and figures (from EN 301 549)

The below tables and figures are copied from the EN 301 549 (2021) clauses without alteration. For each table or figure a link has been created to reference the associated clause, which doesn’t exist in the official EN 301 549 (2021) PDF as the official PDF includes these tables and figures inline with the clause.

Table 5.1: Relationship between maximum design viewing distance and minimum character height at 0,7 degrees minimum subtended angle

Maximum design viewing distanceMinimum character height

100 mm

1,2 mm

200 mm

2,4 mm

250 mm

3,1 mm

300 mm

3,7 mm

350 mm

4,3 mm

400 mm

4,9 mm

450 mm

5,5 mm

500 mm

6,1 mm

550 mm

6,7 mm

600 mm

7,3 mm

Figure 1: Relationship between minimum character height and maximum design viewing distance
Diagram illustrating the linear relationship of the text 5.1.4 Functionality closed to text enlargement

Related content:

Figure 2: Unobstructed forward reach
A diagram illustrating the content of the text 8.3.2.2 Unobstructed low forward reach. Person in a wheelchair reaching forward.

Related content:

Figure 3: Obstructed forward reach
A diagram illustrating the content of the text 8.3.2.3.3 Obstructed (< 635 mm) forward reach. Person in wheelchair reaching over a desk demonstrating unobstructed and obstructed high reach.

Related content:

Figure 4: Toe clearance
A diagram illustrating the content of the text 8.3.2.5 Toe clearance.

Related content:

Figure 5: Knee clearance
A diagram illustrating the content of the text 8.3.2.6 Knee clearance.

Related content:

Figure 6: Unobstructed side reach
A diagram illustrating the content of the text 8.3.3.2 Unobstructed low side reach. Person in a wheelchair reaching to the side.

Related content:

Figure 7: Obstructed high side reach
A diagram illustrating the content of the text 8.3.3.3.2 Obstructed (≤ 610 mm) side reach. Person in a wheelchair reaching to the side demonstrating unobstructed and obstructed high side reach.

Related content:

Figure 8: Vertical change in level
Diagram illustrating the content of the text 8.3.4.1 Change in level

Related content:

Figure 9: Bevelled change in level
Diagram illustrating the content of 8.3.4.1 Change in level

Related content:

Figure 10: Clear floor or ground space
Diagram illustrating the content of the text 8.3.4.2 Clear floor or ground space. Person in a wheelchair demonstrating minimum clearance.

Related content:

Figure 11: Manoeuvring Clearance in an Alcove, Forward Approach
A diagram illustrating the content of the text 8.3.4.3.2 Forward approach. Person in a wheelchair in an alcove.

Related content:

Figure 12: Manoeuvring Clearance in an Alcove, Parallel Approach
A diagram illustrating the content of the text 8.3.4.3.3 Parallel approach. person in a wheelchair in an alcove.

Related content:

Table 9.1: WCAG 2.1 Level AAA Success Criteria
No.GuidelineSuccess Criterion NumberSuccess Criteria Name
1Time-based media1.2.6Sign Language (Prerecorded)
2Time-based media1.2.7Extended Audio Description (Prerecorded)
3Time-based media1.2.8Media Alternative (Prerecorded)
4Time-based media1.2.9Audio-only (Live)
5Adaptable1.3.6Identify Purpose
6Distinguishable1.4.6Contrast (Enhanced)
7Distinguishable1.4.7Low or No Background Audio
8Distinguishable1.4.8Visual Presentation
9Distinguishable1.4.9Images of Text (No Exception)
10Keyboard Accessible2.1.3Keyboard (No Exception)
11Enough time2.2.3No Timing
12Enough time2.2.4Interruptions
13Enough time2.2.5Re-authenticating
14Enough time2.2.6Timeouts
15Seizures and physical reactions2.3.2Three Flashes
16Seizures and physical reactions2.3.3Animation form Interactions
17Navigable2.4.8Location
18Navigable2.4.9Link Purpose (Link Only)
19Navigable2.4.10Section Headings
20Input modalities2.5.5Target Size
21Input modalities2.5.6Concurrent Input Mechanisms
22Readable3.1.3Unusual Words
23Readable3.1.4Abbreviations
24Readable3.1.5Reading Level
25Readable3.1.6Pronunciation
26Predictable3.2.5Change on Request
27Input assistance3.3.5Help
28Input assistance3.3.6Error Prevention (All)

Annex – Chapter 14 Conformance

Conformance to the present document is achieved by meeting all the applicable requirements, these are clauses containing the word "shall". Those clauses containing the word "should" are recommendations and are not required for conformance.

All clauses except those in clause 12 are self-scoping. This means they are introduced with the phrase 'Where ICT'. A requirement is met when the pre-condition is true and the corresponding test (in Annex C) is passed. When one of the pre-conditions is false the requirement is not applicable. Consequently, the result of the tests in Annex C can be: not applicable, pass, fail, or (in exceptional circumstances) not testable.

ICT is often comprised of an assembly of two or more items of ICT. In some cases, two or more interoperable items of ICT may together meet more requirements of the standard when one item complements the functionality of the other and the sum together meets more of the accessibility requirements. However, combining two items of ICT, both of which fail to meet any particular requirement, will not lead to a combined ICT system that meets that requirement.

The present document does not prioritize requirements.

NOTE 1: Conformance with the accessibility requirements could be affected by subsequent implementation or maintenance.

NOTE 2: Sampling is frequently required on complex ICT when there are too many instances of the object to be tested. The present document cannot recommend specific ICT evaluation sampling techniques as these are context specific.

The inherent nature of certain situations makes it impossible to make reliable and definitive statements that accessibility requirements have been met. In those situations therefore, the requirements in the present document are not applicable:

NOTE 3: Even in the above situations, it is best practice to apply requirements in the present document wherever it is feasible and safe to do so.

Annex - References (from EN 301 549)

2.1 Normative references 

References are specific, identified by date of publication and/or edition number or version number. Only the cited version applies. 

Referenced documents which are not found to be publicly available in the expected location might be found at ETSI References in docbox. 

The following referenced documents are necessary for the application of the present document. 

[1] ETSI ETS 300 381 (Edition 1) (December 1994): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids". 

[2] ETSI ES 200 381-1 (V1.2.1) (October 2012): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids Part 1: Fixed-line speech terminals". 

[3] ETSI ES 200 381-2 (V1.1.1) (October 2012): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids; Part 2: Cellular speech terminals".

[4] W3C Recommendation (December 2008) /ISO/IEC 40500:2012: "Web Content Accessibility Guidelines (WCAG) 2.0". 

[5] W3C Proposed Recommendation (June 2018): "Web Content Accessibility Guidelines (WCAG) 2.1". 

2.2 Informative references 

References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. 

The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. 

[i.1] ANSI/IEEE C63.19 (2011): "American National Standard Method of Measurement of Compatibility between Wireless Communication Devices and Hearing Aids". 

[i.2] ANSI/TIA-4965: "Receive volume control requirements for digital and analogue wireline terminals". 

[i.3] European Commission M 376-EN: "Standardization Mandate to CEN, CENELEC and ETSI in support of European accessibility requirements for public procurement of products and services in the ICT domain". 

[i.4] ETSI EG 201 013: "Human Factors (HF); Definitions, abbreviations and symbols". 

[i.5] ETSI ES 202 975: "Human Factors (HF); Requirements for relay services". 

[i.6] ETSI ETS 300 767: "Human Factors (HF); Telephone Prepayment Cards; Tactile Identifier". 

[i.7] ETSI CEN/CENELEC/ETSI TR 101 550: "Documents relevant to EN 301 549 "Accessibility requirements suitable for public procurement of ICT products and services in Europe"". 

[i.8] ETSI CEN/CENELEC/ETSI TR 101 551: "Guidelines on the use of accessibility award criteria suitable for publicly procured ICT products and services in Europe". 

[i.9] ETSI TR 102 612: "Human Factors (HF); European accessibility requirements for public procurement of products and services in the ICT domain (European Commission Mandate M 376, Phase 1)". 

[i.10] ETSI TS 126 114: "Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction (3GPP TS 26.114)". 

[i.11] ETSI TS 122 173: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 (3GPP TS 22.173)". 

[i.12] ETSI TS 134 229: "Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification (3GPP TS 34.229)". 

[i.13] IETF RFC 4103 (2005): "RTP Payload for Text Conversation".

[i.14] ISO/IEC 17007:2009: "Conformity assessment - Guidance for drafting normative documents suitable for use for conformity assessment". 

[i.15] ISO 9241-11:2018:"Ergonomics of human-system interaction - Part 11: Usability: Definitions and concepts". 

[i.16] ISO 9241-110:2006: "Ergonomics of human-system interaction -- Part 110: Dialogue principles". 

[i.17] ISO 9241-171:2008: "Ergonomics of human-system interaction-Part 171: Guidance on software accessibility". 

[i.18] void

[i.19] ISO/IEC 13066-1:2011: "Information technology - Interoperability with assistive technology (AT) - Part 1: Requirements and recommendations for interoperability". 

[i.20] Recommendation ITU-T E.161 (2001): "Arrangement of digits, letters and symbols on telephones and other devices that can be used for gaining access to a telephone network". 

[i.21] Recommendation ITU-T G.722 (1988): "7 kHz audio-coding within 64 kbit/s". 

[i.22] Recommendation ITU-T G.722.2 (2003): "Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB)". 

[i.23] Recommendation ITU-T V.18 (2000): "Operational and interworking requirements for DCEs operating in the text telephone mode". 

[i.24] TIA-1083-A (2010): "Telecommunications; Telephone Terminal equipment; Handset magnetic measurement procedures and performance requirements". 

[i.25] Section 508 of the United States Rehabilitation Act of 1973, revised 2017. NOTE: Available at https://www.section508.gov/manage/laws-and-policies . 

[i.26] W3C Working Group Note 5 September 2013: "Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT)". 

[i.27] M 554 Commission Implementing Decision C(2017)2585 of 27.4.2017 on a standardisation request to the European standardisation organisations in support of Directive (EU) 2016/2102 of the European Parliament and of the Council on the accessibility of the websites and mobile applications of public sector bodies. 

[i.28] Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies. 

[i.29]ETSI/CEN/CENELEC EN 301 549 (V2.1.2) (August 2018): "Accessibility requirements for ICT products and services". 

[i.30] ETSI/CEN/CENELEC TR 101 552: "Guidance for the application of conformity assessment to accessibility requirements for public procurement of ICT products and services in Europe".

[i.31] ISO/IEC TS 20071-25:2017: "Information technology - User interface component accessibility - Part 25: Guidance on the audio presentation of text in videos, including captions, subtitles and other on-screen text".

[i.32] W3C Recommendation (September 2015): "Authoring Tool Accessibility Guidelines (ATAG) 2.0". NOTE: Available at http://www.w3.org/TR/ATAG20/.

[i.33] W3C Recommendation (September 2015): "User Agent Accessibility Guidelines (UAAG) 2.0". NOTE: Available at http://www.w3.org/TR/UAAG20/.

[i.34]ISO 21542:2011: "Building construction - Accessibility and usability of the built environment".

[i.35]ISO/IEC Guide 71:2014: "Guide for addressing accessibility in standards".

[i.36]Recommendation ITU-T T.140 (1988): "Protocol for multimedia application text conversation".

[i.37]Recommendation ITU-T F.703 (2000): "Multimedia conversational services".

[i.38] W3C WebSchemas/Accessibility 2.0. NOTE: Available at https://www.w3.org/wiki/WebSchemas/Accessibility.

[i.39]Void

[i.40]Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on public procurement and repealing Directive 2004/18/EC.

Annex – Definition of terms, symbols and abbreviations (from EN 301 549)

3.1 Terms

For the purposes of the present document, the terms given in ETSI EG 201 013 [i.4] and the following apply:

accessibility:

extent to which products, systems, services, environments and facilities can be used by people from a population with the widest range of user needs, characteristics and capabilities, to achieve identified goals in identified contexts of use (from ISO 9241-11:2018 [i.15])

  • NOTE 1: Context of use includes direct use or use supported by assistive technologies.
  • NOTE 2: The context in which the ICT is used may affect its overall accessibility. This context could include other products and services with which the ICT may interact.
access space:

space intended to be occupied by the person, including their Assistive Technology, while they are using the product

Assistive Listening Devices (ALDs):

devices that help separate the sounds, particularly speech, that a person wants to hear from background noise by bringing sound directly into the ear

  • NOTE: These are often found in meetings and public venues such as plays, concerts and places of worship. They can also be used at home with televisions and other products with auditory output.
Assistive Technology (AT):

equipment, product system, hardware, software or service that is used to increase, maintain or improve capabilities of individuals (from ISO/IEC Guide 71:2014 [i.35])

  • NOTE 1: Assistive technology is an umbrella term that is broader than assistive products.
  • NOTE 2: Assistive technology can include assistive services, and professional services needed for assessment, recommendation and provision.
  • NOTE 3: Where ICT does not support directly connected assistive technology, but which can be operated by a system connected over a network or other remote connection, such a separate system (with any included assistive technology) can also be considered assistive technology. This is an additional note, not included in ISO/IEC Guide 71:2014 [i.35].
audio description

additional audible narrative, interleaved with the dialogue, which describes the significant aspects of the visual content of audio-visual media that cannot be understood from the main soundtrack alone

  • NOTE: This is also variously described using terms such as "video description" or variants such as "descriptive narration".
authoring tool

software that can be used to create or modify content

  • NOTE 1: An authoring tool may be used by a single user or multiple users working collaboratively.
  • NOTE 2: An authoring tool may be a single stand-alone application or be comprised of collections of applications.
  • NOTE 3: An authoring tool may produce content that is intended for further modification or for use by end-users.
caption

synchronized visual and/or text alternative for both speech and non-speech audio information needed to understand the media content (after WCAG 2.1 [5])

  • NOTE: This is also variously described using terms such as "subtitles" or variants such as "subtitles for the deaf and hard-of-hearing".
closed functionality

functionality that is limited by characteristics that prevent a user from attaching, installing or using assistive technology

content

information and sensory experience to be communicated to the user by means of software, including code or mark-up that defines the content's structure, presentation, and interactions (after WCAG2ICT [i.26])

  • NOTE: Content occurs in three places: web pages, documents and software. When content occurs in a web page or a document, a user agent is needed in order to communicate the content's information and sensory experience to the user. When content occurs in software, a separate user agent is not needed in order to communicate the content's information and sensory experience to the user - the software itself performs that function.
context of use

combination of users, goals and tasks, resources, and environment. (from ISO 9241-11:2018 [i.15])

  • NOTE: The "environment" in a context of use includes the technical, physical, social, cultural and organizational environments.
document

logically distinct assembly of content (such as a file, set of files, or streamed media) that functions as a single entity rather than a collection, that is not part of software and that does not include its own user agent (after WCAG2ICT [i.26])

  • NOTE 1: A document always requires a user agent to present its content to the user.
  • NOTE 2: Letters, e-mail messages, spreadsheets, books, pictures, presentations, and movies are examples of documents.
  • NOTE 3: Software configuration and storage files such as databases and virus definitions, as well as computer instruction files such as source code, batch/script files, and firmware, are examples of files that function as part of software and thus are not examples of documents. If and where software retrieves "information and sensory experience to be communicated to the user" from such files, it is just another part of the content that occurs in software and is covered by WCAG2ICT like any other parts of the software. Where such files contain one or more embedded documents, the embedded documents remain documents under this definition.
  • NOTE 4: A collection of files zipped together into an archive, stored within a single virtual hard drive file, or stored in a single encrypted file system file, do not constitute a single document when so collected together. The software that archives/encrypts those files or manages the contents of the virtual hard drive does not function as a user agent for the individually collected files in that collection because that software is not providing a fully functioning presentation of that content.
  • NOTE 5: Anything that can present its own content without involving a user agent, such as a self-playing book, is not a document but is software.
  • NOTE 6: A single document may be composed of multiple files such as the video content and closed caption text. This fact is not usually apparent to the end-user consuming the document/content.
  • NOTE 7: An assembly of files that represented the video, audio, captions and timing files for a movie is an example of a document.
  • NOTE 8: A binder file used to bind together the various exhibits for a legal case would not be a document.
  • NOTE 9: Documents may contain sub-documents.
embedded:

directly included in the content that is downloaded to the user agent and its extension, and is intended to be used in rendering the web page

  • NOTE: Something that is downloaded using a mechanism on the web page but is not used in rendering the page is not "embedded" in the page.
ICT network:

technology and resources supporting the connection and operation of interconnected ICT

Information and Communication Technology (ICT):

technology, equipment, or interconnected system or subsystem of equipment for which the principal function is the creation, conversion, duplication, automatic acquisition, storage, analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission, reception, or broadcast of data or information

  • NOTE: Examples of ICT are web pages, electronic content, telecommunications products, computers and ancillary equipment, software including mobile applications, information kiosks and transaction machines, videos, IT services, and multifunction office machines which copy, scan, and fax documents.
mechanically operable part:

operable part that has a mechanical interface to activate, deactivate, or adjust the ICT

  • NOTE: Examples of mechanically operable parts include scanner covers, notebook docking stations and lids as well as physical switches and latches.
mechanism for private listening:

auditory output designed so that only the current user can receive the sound

  • NOTE: Personal headsets, directional speakers and audio hoods are examples of mechanisms for private listening.
non-text content:

content that is not a sequence of characters that can be programmatically determined or where the sequence is not expressing something in human language (after WCAG 2.1 [5])

non-web document:

document that is not a web page, not embedded in web pages nor used in the rendering or functioning of the page

non-web software:

software that is not a web page, not embedded in web pages nor used in the rendering or functioning of the page

open functionality

functionality that supports access by assistive technology

  • NOTE: This is the opposite of Closed Functionality.
operable part

component of ICT used to activate, deactivate, or adjust the ICT

  • NOTE 1: Operable parts can be provided in either hardware (see mechanically operable parts, above) or software. An on-screen button is an example of an operable part provided by software.
  • NOTE 2: Operable parts do not include parts involved only in maintenance or repair or other actions that are not expected of a typical user if the product is not malfunctioning. These actions include: clearing paper jams internal to the machine, replacing items or parts internal to the machine that may expose the end user to sharp or hot surfaces, replacing or repairing items designated by manufacturers as service or maintenance items in user documentation.
platform software

collection of software components that runs on an underlying software or hardware layer, and that provides a set of software services to other software components that allows those applications to be isolated from the underlying software or hardware layer (after ISO/IEC 13066-1 [i.19])

  • NOTE: A particular software component might play the role of a platform in some situations and a client in others.
programmatically determinable

able to be read by software from developer-supplied data in a way that other software, including assistive technologies, can extract and present this information to users in different modalities

  • NOTE: WCAG 2.1 uses "determined" where this definition uses "able to be read" (to avoid ambiguity with the word "determined").
Real-Time Text (RTT):

form of a text conversation in point to point situations or in multipoint conferencing where the text being entered is sent in such a way that the communication is perceived by the user as being continuous

  • NOTE 1: Users will perceive communication as continuous if the delay between text being created by the sender and received by the recipient is less than 500 ms. However, the actual delay will be dependent on the communication network.
  • NOTE 2: The creation of text will differ between systems where text is entered on a word-by-word basis (e.g. speech to text and predictive-text based systems) and systems where each character is separately generated (e.g. typing on a physical keyboard).
satisfies a success criterion

success criterion does not evaluate to "false" when applied to the ICT (after WCAG 2.1 [5])

single user connection:

connection that consists of sound, RTT or video (or a combination of two or three of those media) that is established by a single user action

  • NOTE: Even though the different media may travel over different channels, and more than one piece of hardware may be involved, it appears to the user like a single connection, and is treated by any intermediate technologies (e.g. network, auto-reception) as a single connection for purposes such as transfer.
spoken captions/subtitles audio captions/subtitles:

captions/subtitles that are voiced over the audiovisual content (from ISO/IEC TS 20071-25 [i.31])

stationary ICT:

ICT that stands on the floor, or is mounted on a wall or other immovable structure, and is not intended to be moved by its user

  • NOTE 1: Typically, stationary ICT rests on the ground (such as an information kiosk) or is installed in a wall (such as a machine that dispenses cash or performs other banking services).
  • NOTE 2: A manufacturer cannot control the height of ICT that is put on a table by someone else, but they are able to control the reach dimensions of self-contained ICT that rests on the ground and can specify the heights for installation in walls.
terminal

combination of hardware and/or software with which the end user directly interacts and that provides the user interface

  • NOTE 1: The hardware may consist of more than one device working together e.g. a mobile device and a computer.
  • NOTE 2: For some systems, the software that provides the user interface may reside on more than one device such as a telephone and a server.
turn-taking:

type of organization in conversation and discourse where participants speak one at a time in alternating turns

user agent

software that retrieves and presents content for users (after WCAG 2.1 [5])

  • NOTE 1: Software that only displays the content contained within it is treated as software and not considered to be a user agent.
  • NOTE 2: An example of software that is not a user agent is a calculator application that does not retrieve the calculations from outside the software to present it to a user. In this case, the calculator software is not a user agent, it is simply software with a user interface.
  • NOTE 3: Software that only shows a preview of content such as a thumbnail or other non-fully functioning presentation is not providing user agent functionality.
user interface

all components of an interactive system (software or hardware) that provide information and/or controls for the user to accomplish specific tasks with the interactive system (from ISO 9241-110 [i.16])

user interface element

entity of the user interface that is presented to the user by the software (after ISO 9241-171 [i.17])

  • NOTE 1: This term is also known as "user interface component".
  • NOTE 2: User-interface elements can be interactive or not.
web content

content that belongs to a web page, and that is used in the rendering or that is intended to be used in the rendering of the web page

web page

non-embedted resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent (after WCAG 2.1 [5])

3.2 Symbols

void

3.3 Abbreviations

For the purposes of the present document, the following abbreviations apply:

ANSI
American National Standards Institute
AT
Assistive Technology
ATAG
Authoring Tool Accessibility Guidelines (of W3C)
CEN
Comité Européen de Normalisation (no English Term)
CSS
Cascading Style Sheets
DOM
Document Object Model
EU
European Union
FPS
Frames Per Second
FXML
XML-based user interface markup language
HTML
HyperText Markup Language
HTTP
HyperText Transfer Protocol
ICT
Information and Communication Technology
IETF
Internet Engineering Task Force
IMS
IP Multimedia System
IP
Internet Protocol
JWG
Joint Working Group (of CEN/CENELEC/ETSI)
ODF
Open Document Format
OOXML
Office Open eXtensible Markup Language
PSTN
Public Switched Telephone Network
RFC
Request For Comment
RTT
Real-Time Text
SIP
Session Initiation Protocol
URI
Uniform Resource Identifier
USB
Universal Serial Bus
VoIP
Voice over IP
W3C
World Wide Web Consortium
WCAG
Web Content Accessibility Guidelines (of W3C)
XML
eXtensible Markup Language
XUL
XML User interface Language
ISO
International Organization for Standardization
ITU-T
International Telecommunication Union - Telecommunication standardization sector
LED
Light Emitting Device
QVGA
Quarter Video Graphics Array
UAAG
User Agent Accessibility Guidelines (of W3C)
VGA
Video Graphics Array
WAI
Web Accessibility Initiative
WLAN
Wireless Local Access Network

Annex - Practical guidance for accessible non-web documentation

In WCAG “success criteria” are all technology agnostic. The requirements for non-web documents are based on the WCAG 2.1 level AA requirements, which means all level A and AA criteria relevant to documents must be met.

The W3C publishes sufficient techniques to meet WCAG success criteria, including techniques for non-web document formats such as PDF. Using a given technique is considered “sufficient” to meet the criteria relevant to the technique, but you can also meet the criteria in other ways.

Shared Services Canada has created a set of guides for producing accessible documents in Microsoft Office:

Various software vendors and organizations offer supplementary material that provides instructions for making documents accessible:

NOTE: Following the guidance given in the links above does not guarantee compliance with WCAG 2.1. Links are provided for reference only.

Page details

Date modified:
\ No newline at end of file diff --git a/en/introduction-to-accessibility-requirements-for-audio-video/index.html b/en/introduction-to-accessibility-requirements-for-audio-video/index.html index 53a7cf548..508f12ad8 100644 --- a/en/introduction-to-accessibility-requirements-for-audio-video/index.html +++ b/en/introduction-to-accessibility-requirements-for-audio-video/index.html @@ -1,4 +1,4 @@ -Introduction to accessibility requirements for audio-video - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Introduction to accessibility requirements for audio-video

This document is a great introduction on how to make accessible video for a communication advisor audience which are in between the web author and the content expert.

Introduction

The purpose of this guide is to teach you how to ensure all audio-video learning products are accessible for all learners. WCAG 2.1 and other accessibility guidelines refer to audio-video recordings, live or pre-recorded as Time-Based Media.

Time-based media can be any of the following:

We often use audio and video to present information, facilitate courses and demo systems. By not including the appropriate information when developing a time-based media learning object, we are excluding many learners or at minimum, making it difficult for them to access the training they need to do their job.

General Requirements

Whether the time-based media is accessible largely depends on the following four factors being taken into consideration:

Summaries for each of the factors are presented here, while guidelines, checklists and samples follow later in the document.

Transcript summary

Transcripts are the text equivalent of an audio or video file. They make it easier for people who need to access information in audio and visual media but can't hear or see the content. Ensure that transcripts include all:

Transcript Guidelines

Transcript Checklist

Captioning summary

Videos with audio require synchronized captioning (where the text aligns with the spoken words in the audio and when important actions are presented on the screen).

Most “closed captions” can be hidden or shown by people watching the video. They can also be “open captions” that are always displayed and cannot be turned off.

Open captions are recommended at the top of American Sign Language (ASL) and Langue des Signes Québécoise (LSQ) videos.

Anything said or heard in the video must be included in the captioning. It is important that captions are:

Design teams or a contractor can provide the caption text.

Captioning Guidelines

Captioning Checklist

Audio description summary

Audio description allows any user with a visual disability or cognitive disability to receive a very detailed and descriptive experience of what is happening on the screen. During existing pauses in dialogue, audio description provides information about actions, characters, scene changes, and on-screen text that are important and are not described or spoken in the main soundtrack.

This can be done using:

Audio Description Guidelines

Audio Description Checklist

Keyboard Access

All video controls must be accessible and navigable via the keyboard. It is the responsibility of the developer to ensure that video players are accessible such as:

Keyboard access is tested by the developer, design teams or a contractor.

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Introduction to accessibility requirements for audio-video

This document is a great introduction on how to make accessible video for a communication advisor audience which are in between the web author and the content expert.

Introduction

The purpose of this guide is to teach you how to ensure all audio-video learning products are accessible for all learners. WCAG 2.1 and other accessibility guidelines refer to audio-video recordings, live or pre-recorded as Time-Based Media.

Time-based media can be any of the following:

We often use audio and video to present information, facilitate courses and demo systems. By not including the appropriate information when developing a time-based media learning object, we are excluding many learners or at minimum, making it difficult for them to access the training they need to do their job.

General Requirements

Whether the time-based media is accessible largely depends on the following four factors being taken into consideration:

Summaries for each of the factors are presented here, while guidelines, checklists and samples follow later in the document.

Transcript summary

Transcripts are the text equivalent of an audio or video file. They make it easier for people who need to access information in audio and visual media but can't hear or see the content. Ensure that transcripts include all:

Transcript Guidelines

Transcript Checklist

Captioning summary

Videos with audio require synchronized captioning (where the text aligns with the spoken words in the audio and when important actions are presented on the screen).

Most “closed captions” can be hidden or shown by people watching the video. They can also be “open captions” that are always displayed and cannot be turned off.

Open captions are recommended at the top of American Sign Language (ASL) and <span =lang="fr">Langue des Signes Québécoise (LSQ) videos.

Anything said or heard in the video must be included in the captioning. It is important that captions are:

Design teams or a contractor can provide the caption text.

Captioning Guidelines

Captioning Checklist

Audio description summary

Audio description allows any user with a visual disability or cognitive disability to receive a very detailed and descriptive experience of what is happening on the screen. During existing pauses in dialogue, audio description provides information about actions, characters, scene changes, and on-screen text that are important and are not described or spoken in the main soundtrack.

This can be done using:

Audio Description Guidelines

Audio Description Checklist

Keyboard Access

All video controls must be accessible and navigable via the keyboard. It is the responsibility of the developer to ensure that video players are accessible such as:

Keyboard access is tested by the developer, design teams or a contractor.

Page details

Date modified:
\ No newline at end of file diff --git a/en/mapping-between-revised-section-508-and-en-301-549-2014-2018-2019-and-2021/index.html b/en/mapping-between-revised-section-508-and-en-301-549-2014-2018-2019-and-2021/index.html index f9b243605..19baab9e6 100644 --- a/en/mapping-between-revised-section-508-and-en-301-549-2014-2018-2019-and-2021/index.html +++ b/en/mapping-between-revised-section-508-and-en-301-549-2014-2018-2019-and-2021/index.html @@ -1,4 +1,4 @@ -Mapping between Revised Section 508 and EN 301 549 (2014, 2018, 2019 and 2021) - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Mapping between Revised Section 508 and EN 301 549 (2014, 2018, 2019 and 2021)

As the EN 301 549 standards continue to evolve and release updates, this document shows the progression of the EN 301 549 standard from 2014 through the proceeding updates of 2018, 2019 and 2021. This information is important as the Government of Canada (GC) is moving towards adopting the EN 301 549 (2021) as its accessibility standard for ICT. The GC, as part of the solicitation process, may ask suppliers to provide accessibility conformance reports based on the Voluntary Product Accessibility Template (VPAT®). Each VPAT® is based on a specific technical standard – Revised Section 508, EN 301 549, or Web Content Accessibility Guidelines (WCAG). Suppliers, technical authorities and contracting authorities need to understand the differences between these standards to ensure that the accessibility requirements are properly addressed.

On this page

This document reproduces relevant ICT accessibility requirements from the EN 301 549 Harmonised European Standard "Accessibility requirements for ICT products and services" (© used under license from European Telecommunications Standards Institute 2014, 2018, 2019 and 2021. © Comité Européen de Normalisation 2014, 2018, 2019, 2021. © Comité Européen de Normalisation Électrotechnique 2014, 2018, 2019 and 2021. All rights reserved.)

Caveat

This document was created by the Shared Services Canada (SSC) Accessibility, Accommodations and Adaptive Computer Technology (AAACT) program in February 2020 and updated in October 2022. To the best of our knowledge, this document was accurate as of October 2022. SSC does not warrant any jurisdiction’s reliance on this work. If you have any questions about this document, please email the AAACT program.

Intended Audience

The intended audience is Technical and Contracting Authorities within SSC and the Government of Canada (GC), as well as Suppliers who are delivering Information and Communications Technology (ICT) products and services.

Background

This document deals with technical standards for ICT accessibility. The most common standards are the Web Content Accessibility Guidelines (WCAG), Revised Section 508 and EN 301 549 Harmonized European Standard for ICT Accessibility.

The Revised Section 508 (2017) provides the technical standard for the US government to procure accessible products and services. This standard is, by design, closely harmonized with the EN 301 549 (2014) – which drew its requirements largely from the original Section 508 standards and WCAG 2.0. Consequently, these standards are very similar but do contain key differences. The EN 301 549 has been updated four times since the release of the Revised Section 508, introducing further differences between the standards.

Purpose

The purpose of this document is to identify the similarities and differences between Revised Section 508 and the EN 301 549 standards.

As the EN 301 549 standards continue to evolve and release updates, this document shows the progression of the EN 301 549 standards from 2014 through the proceeding updates of 2018, 2019 and 2021. This information is important as the GC is moving towards adopting the EN 301 549 (2021) as its accessibility standard for ICT. The GC, as part of the solicitation process, may ask suppliers to provide accessibility conformance reports based on the Voluntary Product Accessibility Template (VPAT). Each VPAT is based on a specific technical standard – Revised Section 508, EN 301 549, or WCAG. Suppliers, technical authorities and contracting authorities need to understand the differences between these standards to ensure that the accessibility requirements are properly addressed.

Summary of differences

WCAG to Revised Section 508 / EN 301 549

WCAG, while technology-agnostic, is typically applicable to websites and web applications. For these products, specifying WCAG 2.0 level AA or 2.1 level AA as a technical standard may be sufficient. However, the other standards include additional requirements which may apply to web applications that provide any of the following features: documented accessibility features, authoring tools, two-way communication, video and conversion of information between electronic formats. The other standards also include requirements for support and documentation, which may apply to website or web application procurements.

Through the WCAG2ICT Task Force, the requirements of WCAG have been adapted to more precisely address the requirements for other kinds of ICT including non-web software and non-web documents. These adaptations have been integrated into Revised Section 508 and EN 301 549, so specifying those standards will result in clearer accessibility requirements for non-web ICT products than specifying WCAG would.

While Revised Section 508 and EN 301 549 include WCAG leveled requirements, these standards have a broader scope. For hardware ICT and ICT services, WCAG will not properly address accessibility requirements. If the functionality of the product or service may not be fully addressed by WCAG, GC procurements should specify the EN 301 549 standard.

Revised Section 508 to EN 301 549 (2014)

These standards are closely harmonized. Some requirements vary in specificity, with the EN 301 549 usually taking a more general approach. Revised Section 508 requirements may refer to specific US standards, while the EN 301 549 either includes the relevant specifications within the document or refers to international standards. Some general requirements of Revised Section 508 are only addressed in the Software chapter of the EN 301 549, so the Software requirements may need to be included even for hardware devices which have displays.

EN 301 549 (2014) to EN 301 549 (2018)

Primarily, WCAG-related chapters (9, 10 and 11) differ between these versions, along with several explanatory updates, stylistic rewordings, numbering changes, and functional changes. The 2014 version includes all WCAG 2.0 level A and AA success criteria, while the 2018 version is updated to directly reference all WCAG 2.1 level A and AA success criteria. (Although the 2018 and 2019 versions do not duplicate WCAG text, we have included the new requirements with the text in this document for clarity.) The numbering in WCAG-related chapters in the 2018 version directly follows WCAG 2.1 success criteria. For example, clause 9.2.3.1 of the EN 301 549 refers to WCAG success criterion 2.3.1.

EN 301 549 (2018) to EN 301 549 (2019)

The majority of changes are stylistic rewordings and additional explanatory notes. There are 14 new requirements, primarily relating to use with limited hearing. A few requirements from the 2018 version have been split up or consolidated. Requirements relating to physical access to ICT have been reworked into “8.3 Stationary ICT”. Numbering is otherwise consistent between versions.

EN 301 549 (2019) to EN 301 549 (2021)

The EN 301 549 V3.2.1 (2021) document was developed from EN 301 549 V2.1.2 (2018). There are no new requirements. The Annex F track changes table, has been added for future releases. Some clarification in 7.1.1 concerning captioning but numbering is otherwise consistent between versions. The numbering in WCAG-related chapters 9, 10 and 11 in the 2021 version directly follows WCAG 2.1 success criteria. For example, clause 9.2.3.1 of the EN 301 549 (2021) refers to WCAG success criterion 2.3.1. As stated in the footnotes, there are items that point to clauses that are not included in this document. They are only included if it is a new requirement and it points only to the WCAG guidelines.

Sources

Comparison Tables

Glossary

Stylistic rewording:
the text of the criterion modifies what is said, but does not modify what the criterion asks for, nor does it add new content or stipulations to the existing criterion
Functional change:
the text of the criterion significantly changes what the criterion is asking for, for example: the word “should” (denoting a recommendation) is replaced by the word “shall” (denoting a requirement)
Explanatory update:
the text has content or stipulations that clarify the purpose of the criterion without changing its purpose outright, such as specifying the source of a document
Numbering change:
the numbering is the criterion is updated due to either integration of WCAG numbering into the document, or changing the order in which they appear in the document for better flow and understanding
New requirement:
a criterion that does not exist in a previous version of the EN 301 549 document. Several new criteria were added in the 2019 version that do not appear in either the 2014 or 2018 version

Changes between versions of EN 301 549 are emphasized:

  1. For changes in hyperlinks the changes are reflected in bold, using the strong blue under style
  2. For changes in text the changes are reflected in bold, using the strong style
  3. For changes in the clause title the changes are reflected in bold, using the strong blue style
Select to see changes

List tables

List of tables

Chapter 2: Scoping Requirements

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

E207.2 WCAG Conformance

User interface components and content of platforms and applications shall conform to Level A and Level AA Success Criteria and Conformance Requirements specified for web pages in WCAG 2.0.

EXCEPTIONS:

  1. Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to E207.2.
  2. Non-Web software shall not be required to conform to the following four Success Criteria in WCAG 2.0: 2.4.1 Bypass Blocks; 2.4.5 Multiple Ways; 3.2.3 Consistent Navigation; and 3.2.4 Consistent Identification.
  3. Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in WCAG 2.0.

Chapters 9, 10, and 11 apply WCAG 2.0 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).

EN 301 549 Video Series

Stylistic rewordingChapters 9, 10, 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).Functional changeChapters 9, 10, 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).Chapters 9, 10, 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).

Chapter 3: Functional Performance Statements

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
302.1 Without vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

4.2.1 Usage without vision

Where ICT provides visual modes of operation, some users need ICT to provide at least one mode of operation that does not require vision.

NOTE: Audio and tactile user interfaces may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.1 Usage without vision

Where ICT provides visual modes of operation, some users need ICT to provide at least one mode of operation that does not require vision.

NOTE 1: A web page or application with a well formed semantic structure can allow users without vision to identify, navigate and interact with a visual user interface.

NOTE 2: Audio and tactile user interfaces may contribute towards meeting this clause.

Explanatory update

4.2.1 Usage without vision

Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that does not require vision. This is essential for users without vision and benefits many more users in different situations.

NOTE 1: A web page or application with a well formed semantic structure can allow users without vision to identify, navigate and interact with a visual user interface.

NOTE 2: Audio and tactile user interfaces may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.1 Usage without vision

Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that does not require vision. This is essential for users without vision and benefits many more users in different situations.

NOTE 1: A web page or application with a well formed semantic structure can allow users without vision to identify, navigate and interact with a visual user interface.

NOTE 2: Audio and tactile user interfaces may contribute towards meeting this clause.

302.2 With limited vision Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

4.2.2 Usage with limited vision

Where ICT provides visual modes of operation, some users will need the ICT to provide features that enable users to make better use of their limited vision.

NOTE 1: Magnification, reduction of required field of vision and control of contrast, brightness and intensity can contribute towards meeting this clause.

NOTE 2: Where significant features of the user interface are dependent on depth perception, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

NOTE 3: Users with limited vision may also benefit from non-visual access (see clause 4.2.1).

Stylistic rewording

Explanatory update

4.2.2 Usage with limited vision

Where ICT provides visual modes of operation, some users will need the ICT to provide features that enable users to make better use of their limited vision.

NOTE 1: Magnification, reduction of required field of vision and control of contrast, brightness and intensity can contribute towards meeting this clause.

NOTE 2: Where significant features of the user interface are dependent on depth perception, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

NOTE 3: Users with limited vision may also benefit from non-visual access (see clause 4.2.1).

4.2.2 Usage with limited vision

Where ICT provides visual modes of operation, the ICT provides features that enable users to make better use of their limited vision. This is essential for users with limited vision and benefits many more users in different situations.

NOTE 1: Magnification, reduction of required field of vision and control of contrast, brightness and intensity can contribute towards meeting this clause.

NOTE 2: Where significant features of the user interface are dependent on depth perception, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

NOTE 3: Users with limited vision may also benefit from non-visual access (see clause 4.2.1).

Stylistic rewording

Explanatory update

4.2.2 Usage with limited vision

Where ICT provides visual modes of operation, the ICT provides features that enable users to make better use of their limited vision. This is essential for users with limited vision and benefits many more users in different situations.

NOTE 1: Magnification, reduction of required field of vision and control of contrast, brightness and intensity can contribute towards meeting this clause.

NOTE 2: Where significant features of the user interface are dependent on depth perception, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

NOTE 3: Users with limited vision may also benefit from non-visual access (see clause 4.2.1).

302.3 Without Perception of Color

Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

4.2.3 Usage without perception of colour

Where ICT provides visual modes of operation, some users will need the ICT to provide a visual mode of operation that does not require user perception of colour.

NOTE: Where significant features of the user interface are colour-coded, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.3 Usage without perception of colour

Where ICT provides visual modes of operation, some users will need the ICT to provide a visual mode of operation that does not require user perception of colour.

NOTE: Where significant features of the user interface are colour-coded, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

4.2.3 Usage without perception of colour

Where ICT provides visual modes of operation, the ICT provides a visual mode of operation that does not require user perception of colour. This is essential for users with limited colour perception and benefits many more users in different situations.

NOTE: Where significant features of the user interface are colour-coded, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.3 Usage without perception of colour

Where ICT provides visual modes of operation, the ICT provides a visual mode of operation that does not require user perception of colour. This is essential for users with limited colour perception and benefits many more users in different situations.

NOTE: Where significant features of the user interface are colour-coded, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

302.4 Without Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

4.2.4 Usage without hearing

Where ICT provides auditory modes of operation, some users need ICT to provide at least one mode of operation that does not require hearing.

NOTE: Visual and tactile user interfaces may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.4 Usage without hearing

Where ICT provides auditory modes of operation, some users need ICT to provide at least one mode of operation that does not require hearing.

NOTE: Visual and tactile user interfaces may contribute towards meeting this clause.

4.2.4 Usage without hearing

Where ICT provides auditory modes of operation, the ICT provides at least one mode of operation that does not require hearing. This is essential for users without hearing and benefits many more users in different situations.

NOTE: Visual and tactile user interfaces, including those based on sign language, may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.4 Usage without hearing

Where ICT provides auditory modes of operation, the ICT provides at least one mode of operation that does not require hearing. This is essential for users without hearing and benefits many more users in different situations.

NOTE: Visual and tactile user interfaces, including those based on sign language, may contribute towards meeting this clause.

302.5 With Limited Hearing

Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

4.2.5 Usage with limited hearing

Where ICT provides auditory modes of operation, some users will need the ICT to provide enhanced audio features.

NOTE 1: Enhancement of the audio clarity, reduction of background noise, increased range of volume and greater volume in the higher frequency range can contribute towards meeting this clause.

NOTE 2: Users with limited hearing may also benefit from non-hearing access (see clause 4.2.4).

Stylistic rewording

Explanatory update

4.2.5 Usage with limited hearing

Where ICT provides auditory modes of operation, some users will need the ICT to provide enhanced audio features.

NOTE 1: Enhancement of the audio clarity, reduction of background noise, increased range of volume and greater volume in the higher frequency range can contribute towards meeting this clause.

NOTE 2: Users with limited hearing may also benefit from non-hearing access (see clause 4.2.4).

4.2.5 Usage with limited hearing

Where ICT provides auditory modes of operation, the ICT provides enhanced audio features. This is essential for users with limited hearing and benefits many more users in different situations.

NOTE 1: Enhancement of the audio clarity, reduction of background noise, providing a joint monaural option, adjustment of balance of both audio channels, increased range of volume and greater volume in the higher frequency range can contribute towards meeting this clause.

NOTE 2: Allowing the use of Assistive Listening Devices, such as headsets with noise cancellation (connected by cable, Bluetooth or WLAN) can contribute towards meeting this clause.

NOTE 3: Users with limited hearing may also benefit from non-hearing access (see clause 4.2.4).

Stylistic rewording

Explanatory update

Functional change

4.2.5 Usage with limited hearing

Where ICT provides auditory modes of operation, the ICT provides enhanced audio features. This is essential for users with limited hearing and benefits many more users in different situations.

NOTE 1: Enhancement of the audio clarity, reduction of background noise, providing a joint monaural option, adjustment of balance of both audio channels, increased range of volume and greater volume in the higher frequency range can contribute towards meeting this clause.

NOTE 2: Allowing the use of Assistive Listening Devices, such as headsets with noise cancellation (connected by cable, Bluetooth or WLAN) can contribute towards meeting this clause.

NOTE 3: Users with limited hearing may also benefit from non-hearing access (see clause 4.2.4).

302.6 Without Speech Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

4.2.6 Usage without vocal capability

Where ICT requires vocal input from users, some users will need the ICT to provide at least one mode of operation that does not require them to generate vocal output.

NOTE 1: This clause covers the alternatives to the use of orally-generated sounds, including speech, whistles, clicks, etc.

NOTE 2: Keyboard, pen or touch user interfaces may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.6 Usage without vocal capability

Where ICT requires vocal input from users, some users will need the ICT to provide at least one mode of operation that does not require them to generate vocal output.

NOTE 1: This clause covers the alternatives to the use of orally-generated sounds, including speech, whistles, clicks, etc.

NOTE 2: Keyboard, pen or touch user interfaces may contribute towards meeting this clause.

4.2.6 Usage with no or limited vocal capability

Where ICT requires vocal input from users, the ICT provides at least one mode of operation that does not require them to generate vocal output. This is essential users with no or limited vocal capability and benefits many more users in different situations.

NOTE 1: Vocal output includes speech and other orally generated sounds, such as whistles and clicks.

NOTE 2: Keyboard, pen or touch user interfaces may contribute towards meeting this clause.

Functional change

Stylistic rewording

Explanatory update

4.2.6 Usage with no or limited vocal capability

Where ICT requires vocal input from users, the ICT provides at least one mode of operation that does not require them to generate vocal output. This is essential users with no or limited vocal capability and benefits many more users in different situations.

NOTE 1: Vocal output includes speech and other orally generated sounds, such as whistles and clicks.

NOTE 2: Keyboard, pen or touch user interfaces may contribute towards meeting this clause.

302.7 With Limited Manipulation

Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.1

4.2.7 Usage with limited manipulation or strength

Where ICT requires manual actions, some users will need the ICT to provide features that enable users to make use of the ICT through alternative actions not requiring manipulation or hand strength.

NOTE 1: Examples of operations that users may not be able to perform include those that require fine motor control, path dependant gestures, pinching, twisting of the wrist, tight grasping, or simultaneous manual actions.

NOTE 2: One-handed operation, sequential key entry and speech user interfaces may contribute towards meeting this clause.

NOTE 3: Some users have limited hand strength and may not be able to achieve the level of strength to perform an operation. Alternative user interface solutions that do not require hand strength may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.7 Usage with limited manipulation or strength

Where ICT requires manual actions, some users will need the ICT to provide features that enable users to make use of the ICT through alternative actions not requiring manipulation or hand strength.

NOTE 1: Examples of operations that users may not be able to perform include those that require fine motor control, path dependant gestures, pinching, twisting of the wrist, tight grasping, or simultaneous manual actions.

NOTE 2: One-handed operation, sequential key entry and speech user interfaces may contribute towards meeting this clause.

NOTE 3: Some users have limited hand strength and may not be able to achieve the level of strength to perform an operation. Alternative user interface solutions that do not require hand strength may contribute towards meeting this clause.

4.2.7 Usage with limited manipulation or strength

Where ICT requires manual actions, the ICT provides features that enable users to make use of the ICT through alternative actions not requiring manipulation, simultaneous action or hand strength. This is essential for users with limited manipulation or strength and benefits many more users in different situations.

NOTE 1: Examples of operations that users may not be able to perform include those that require fine motor control, path dependant gestures, pinching, twisting of the wrist, tight grasping, or simultaneous manual actions.

NOTE 2: One-handed operation, sequential key entry and speech user interfaces may contribute towards meeting this clause.

NOTE 3: Some users have limited hand strength and may not be able to achieve the level of strength to perform an operation. Alternative user interface solutions that do not require hand strength may contribute towards meeting this clause.

Stylistic rewording

Functional change

Explanatory update

4.2.7 Usage with limited manipulation or strength

Where ICT requires manual actions, the ICT provides features that enable users to make use of the ICT through alternative actions not requiring manipulation, simultaneous action or hand strength. This is essential for users with limited manipulation or strength and benefits many more users in different situations.

NOTE 1: Examples of operations that users may not be able to perform include those that require fine motor control, path dependant gestures, pinching, twisting of the wrist, tight grasping, or simultaneous manual actions.

NOTE 2: One-handed operation, sequential key entry and speech user interfaces may contribute towards meeting this clause.

NOTE 3: Some users have limited hand strength and may not be able to achieve the level of strength to perform an operation. Alternative user interface solutions that do not require hand strength may contribute towards meeting this clause.

302.8 With Limited Reach and Strength

Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.2

4.2.8 Usage with limited reach

Where ICT products are free-standing or installed, the operational elements will need to be within reach of all users.

NOTE: Considering the needs of wheelchair users and the range of user statures in the placing of operational elements of the user interface may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.8 Usage with limited reach

Where ICT products are free-standing or installed, the operational elements will need to be within reach of all users.

NOTE: Considering the needs of wheelchair users and the range of user statures in the placing of operational elements of the user interface may contribute towards meeting this clause.

4.2.8 Usage with limited reach

Where ICT products are free-standing or installed, all the elements required for operation will need to be within reach of all users. This is essential for users with limited reach and benefits many more users in different situations.

NOTE: Considering the needs of wheelchair users and the range of user statures in the placing of operational elements of the user interface may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.8 Usage with limited reach

Where ICT products are free-standing or installed, all the elements required for operation will need to be within reach of all users. This is essential for users with limited reach and benefits many more users in different situations.

NOTE: Considering the needs of wheelchair users and the range of user statures in the placing of operational elements of the user interface may contribute towards meeting this clause.

302.9 With Limited Language, Cognitive, and Learning Abilities

ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

4.2.10 Usage with limited cognition

Some users will need the ICT to provide features that make it simpler and easier to use.

NOTE 1: This clause is intended to include the needs of persons with limited cognitive, language and learning abilities.

NOTE 2: Adjustable timings, error indication and suggestion, and a logical focus order are examples of design features that may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.10 Usage with limited cognition

Some users will need the ICT to provide features that make it simpler and easier to use.

NOTE 1: This clause is intended to include the needs of persons with limited cognitive, language and learning abilities.

NOTE 2: Adjustable timings, error indication and suggestion, and a logical focus order are examples of design features that may contribute towards meeting this clause.

4.2.10 Usage with limited cognition, language or learning

The ICT provides features and/or presentation that makes it simpler and easier to understand, operate and use. This is essential for users with limited cognition, language or learning, and benefits many more users in different situations.

NOTE 1: Adjustable timings, error indication and suggestion, and a logical focus order are examples of design features that may contribute towards meeting this clause.

NOTE 2: Providing an audio output of the text is an example of providing support for people with limited reading abilities.

NOTE 3: Providing spelling aid and word prediction of the text is an example of providing support for people with limited writing abilities.

NOTE 4: Interaction with content can be made easier, and less prone to errors, by presenting tasks in steps that are easy to follow.

Functional change

Stylistic rewording

Explanatory update

4.2.10 Usage with limited cognition, language or learning

The ICT provides features and/or presentation that makes it simpler and easier to understand, operate and use. This is essential for users with limited cognition, language or learning, and benefits many more users in different situations.

NOTE 1: Adjustable timings, error indication and suggestion, and a logical focus order are examples of design features that may contribute towards meeting this clause.

NOTE 2: Providing an audio output of the text is an example of providing support for people with limited reading abilities.

NOTE 3: Providing spelling aid and word prediction of the text is an example of providing support for people with limited writing abilities.

NOTE 4: Interaction with content can be made easier, and less prone to errors, by presenting tasks in steps that are easy to follow.

List tables

Chapter 4: Hardware

402 Closed Functionality

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

402.1 General

ICT with closed functionality shall be operable without requiring the user to attach or install assistive technology other than personal headsets or other audio couplers, and shall conform to 402.

5.1.2.2 Assistive technology

Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.7 as applicable. Personal headsets and induction loops shall not be classed as assistive technology for the purpose of this clause.

Stylistic rewording

Explanatory update

5.1.2.2 Assistive technology Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.6 as applicable. Personal headsets and induction loops shall not be classed as assistive technology for the purpose of this clause.Explanatory update

5.1.2.2 Assistive technology

Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.6 as applicable. Personal headsets and personal induction loops shall not be classed as assistive technology for the purpose of this clause.

Stylistic rewording

5.1.2.2 Assistive technology

Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.6 as applicable. Personal headsets and personal induction loops shall not be classed as assistive technology for the purpose of this clause.

402.2 Speech-Output Enabled

ICT with a display screen shall be speech-output enabled for full and independent use by individuals with vision impairments.3

EXCEPTIONS:

  1. Variable message signs conforming to 402.5 shall not be required to be speech-output enabled.
  2. Speech output shall not be required where ICT display screens only provide status indicators and those indicators conform to 409.
  3. Where speech output cannot be supported due to constraints in available memory or processor capability, ICT shall be permitted to conform to 409 in lieu of 402.2.
  4. Audible tones shall be permitted instead of speech output where the content of user input is not displayed as entered for security purposes, including, but not limited to, asterisks representing personal identification numbers.
  5. Speech output shall not be required for: the machine location; date and time of transaction; customer account number; and the machine identifier or label.
  6. Speech output shall not be required for advertisements and other similar information unless they convey information that can be used for the transaction being conducted.

5.1.3.1 General

Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.

NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form.

NOTE 2: The visual information needed to enable use of some functions may include operating instructions and orientation, transaction prompts, user input verification, error messages and non-text content.

Stylistic rewording

Explanatory update

5.1.3.1 General

Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.

NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form.

NOTE 2: The visual information needed to enable use of some functions may include operating instructions and orientation, transaction prompts, user input verification, error messages and non-text content.

5.1.3.1 Audio output of visual information

Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.

NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form such as braille for deaf-blind users.

NOTE 2: The visual information needed to enable use of some functions may include operating instructions and orientation, transaction prompts, user input verification, error messages and non-text content.

Explanatory update

5.1.3.1 Audio output of visual information

Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.

NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form such as braille for deaf-blind users.

NOTE 2: The visual information needed to enable use of some functions may include operating instructions and orientation, transaction prompts, user input verification, error messages and non-text content.

402.2.1 Information Displayed On-Screen

Speech output shall be provided for all information displayed on-screen.

5.1.3.6 Speech output for non-text content

Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in WCAG 2.0 Success Criterion 1.1.1.

Stylistic rewording

Explanatory update

5.1.3.6 Speech output for non-text content

Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1.

Functional change

5.1.3.6 Speech output for non-text content

Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1.

5.1.3.6 Speech output for non-text content

Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in WCAG 2.1 [5] Success Criterion 1.1.1.

402.2.1 Information Displayed On-Screen Speech output shall be provided for all information displayed on-screen.

5.1.3.7 Speech output for video information

Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content.

NOTE: This speech output can take the form of an audio description or an auditory transcript of the video content.

Stylistic rewording

Explanatory update

5.1.3.7 Speech output for video information

Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content.

NOTE: This speech output can take the form of an audio description or an auditory transcript of the video content.

5.1.3.7 Speech output for video information

Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content.

NOTE: This speech output can take the form of an audio description or an auditory transcript of the video content.

5.1.3.7 Speech output for video information

Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content. NOTE: This speech output can take the form of an audio description or an auditory transcript of the video content.

402.2.1 Information Displayed On-Screen

Speech output shall be provided for all information displayed on-screen.4

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

Stylistic rewording

Explanatory update

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

402.2.2 Transactional Outputs

Where transactional outputs are provided, the speech output shall audibly provide all information necessary to verify a transaction.

5.1.3.16 Receipts, tickets, and transactional outputs

Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.

NOTE: The speech output may be provided by any element of the total ICT system.

Stylistic rewording

Explanatory update

5.1.3.16 Receipts, tickets, and transactional outputs

Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.

NOTE: The speech output may be provided by any element of the total ICT system.

5.1.3.16 Receipts, tickets, and transactional outputs

Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.

NOTE: The speech output may be provided by any element of the total ICT system.

5.1.3.16 Receipts, tickets, and transactional outputs

Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.

NOTE: The speech output may be provided by any element of the total ICT system.

402.2.3 Speech Delivery Type and Coordination Speech output shall be delivered through a mechanism that is readily available to all users, including, but not limited to, an industry standard connector or a telephone handset. Speech shall be recorded or digitized human, or synthesized. Speech output shall be coordinated with information displayed on the screen.

5.1.3.2 Auditory output delivery including speech

Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:

  1. either directly by a mechanism included in or provided with the ICT;
  2. or by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision.

NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in handset/headset, or other industry standard coupled peripheral.

NOTE 2: An industry standard connection could be a wireless connection.

NOTE 3: Some users may benefit from the provision of an inductive loop.

Stylistic rewording

Explanatory update

5.1.3.2 Auditory output delivery including speech

Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:

  1. either directly by a mechanism included in or provided with the ICT; or
  2. by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision.

NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in handset/headset, or other industry standard coupled peripheral.

NOTE 2: An industry standard connection could be a wireless connection.

NOTE 3: Some users may benefit from the provision of an inductive loop.

5.1.3.2 Auditory output delivery including speech

Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:

  1. either directly by a mechanism included in or provided with the ICT; or
  2. by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision.

NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in handset/headset, or other industry standard coupled peripheral.

NOTE 2: An industry standard connection could be a wireless connection.

NOTE 3: Some users may benefit from the provision of an inductive loop.

5.1.3.2 Auditory output delivery including speech

Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:

  1. either directly by a mechanism included in or provided with the ICT; or
  2. by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision.

NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in handset/headset, or other industry standard coupled peripheral.

NOTE 2: An industry standard connection could be a wireless connection.

NOTE 3: Some users may benefit from the provision of an inductive loop.

402.2.3 Speech Delivery Type and Coordination

Speech output shall be delivered through a mechanism that is readily available to all users, including, but not limited to, an industry standard connector or a telephone handset. Speech shall be recorded or digitized human, or synthesized. Speech output shall be coordinated with information displayed on the screen.

5.1.3.3 Auditory output correlation

Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

Stylistic rewording

Explanatory update

5.1.3.3 Auditory output correlation

Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

5.1.3.3 Auditory output correlation

Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

5.1.3.3 Auditory output correlation

Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

402.2.4 User Control

Speech output for any single function shall be automatically interrupted when a transaction is selected. Speech output shall be capable of being repeated and paused.

5.1.3.4 Speech output user control

Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.

NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.

NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to start from the beginning.

Stylistic rewording

Explanatory update

5.1.3.4 Speech output user control

Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.

NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.

NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to start from the beginning.

5.1.3.4 Speech output user control

Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.

NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.

NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to start from the beginning.

5.1.3.4 Speech output user control

Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.

NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.

NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to start from the beginning.

402.2.4 User Control

Speech output for any single function shall be automatically interrupted when a transaction is selected. Speech output shall be capable of being repeated and paused.

5.1.3.5 Speech output automatic interruption

Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.

NOTE: Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT may need to block all user action so that speech is not interrupted.

Stylistic rewording

Explanatory update

5.1.3.5 Speech output automatic interruption

Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.

NOTE: Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT may need to block all user action so that speech is not interrupted.

5.1.3.5 Speech output automatic interruption

Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.

NOTE: Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT may need to block all user action so that speech is not interrupted.

5.1.3.5 Speech output automatic interruption

Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.

NOTE: Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT may need to block all user action so that speech is not interrupted.

402.2.5 Braille Instructions

Where speech output is required by 402.2, braille instructions for initiating the speech mode of operation shall be provided. Braille shall be contracted and shall conform to 36 CFR part 1191, Appendix D, Section 703.3.1.

EXCEPTION: Devices for personal use shall not be required to conform to 402.2.5.

8.5 Tactile indication of speech mode

Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.

NOTE: The tactile indication could include Braille instructions.

Stylistic rewording

Explanatory update

Functional change

8.5 Tactile indication of speech mode

Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.

NOTE: The tactile indication could include Braille instructions.

8.5 Tactile indication of speech mode

Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.

NOTE: The tactile indication could include Braille instructions.

8.5 Tactile indication of speech mode

Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.

NOTE: The tactile indication could include Braille instructions.

402.3.1 Private Listening

Where ICT provides private listening, it shall provide a mode of operation for controlling the volume. Where ICT delivers output by an audio transducer typically held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.

5.1.3.11 Private listening volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.

Stylistic rewording

Explanatory update

5.1.3.11 Private listening volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.

5.1.3.11 Private listening volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.

5.1.3.11 Private listening volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.

402.3.1 Private Listening

Where ICT provides private listening, it shall provide a mode of operation for controlling the volume. Where ICT delivers output by an audio transducer typically held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.5

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETS 300 381, it shall provide a means of magnetic coupling which meets the requirements of ES 200 381-1.

NOTE: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

Stylistic rewording

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETSI ETS 300 381, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1.

NOTE: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1 and shall carry the "T" symbol specified in ETSI ETS 300 381.

NOTE 1: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

NOTE 2: Magnetic coupling is also known as inductive coupling for T-coil.

Stylistic rewording

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1 [2] and shall carry the "T" symbol specified in ETSI ETS 300 381 [1].

NOTE 1: ICT fulfilling the requirements of TIA-1083-A [i.24] is deemed to comply with the requirements of this clause. NOTE 2: Magnetic coupling is also known as inductive coupling for T-coil.

402.3.1 Private Listening

Where ICT provides private listening, it shall provide a mode of operation for controlling the volume. Where ICT delivers output by an audio transducer typically held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.6

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

Stylistic rewording

Explanatory update

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

Explanatory update

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2 [3].

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 [i.1] is deemed to comply with the requirements of this clause.

402.3.2 Non-private Listening

Where ICT provides non-private listening, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. A function shall be provided to automatically reset the volume to the default level after every use.

5.1.3.12 Speaker volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).

NOTE: For noisy environments, 65dBA may not be sufficient.

Stylistic rewording

5.1.3.12 Speaker volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).

NOTE: For noisy environments, 65 dBA may not be sufficient.

5.1.3.12 Speaker volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).

NOTE: For noisy environments, 65 dBA may not be sufficient.

5.1.3.12 Speaker volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).

NOTE: For noisy environments, 65 dBA may not be sufficient.

402.3.2 Non-private Listening Where ICT provides non-private listening, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. A function shall be provided to automatically reset the volume to the default level after every use.

5.1.3.13 Volume reset

Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.

NOTE: A feature to disable the volume reset function may be provided in order to enable the single-user exception to be met.

Stylistic rewording

Explanatory update

5.1.3.13 Volume reset

Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.

NOTE: A feature to disable the volume reset function may be provided in order to enable the single-user exception to be met.

5.1.3.13 Volume reset

Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.

NOTE: A feature to disable the volume reset function may be provided in order to enable the single-user exception to be met.

5.1.3.13 Volume reset

Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.

NOTE: A feature to disable the volume reset function may be provided in order to enable the single-user exception to be met.

402.4 Characters on Display Screens

At least one mode of characters displayed on the screen shall be in a sans serif font. Where ICT does not provide a screen enlargement feature, characters shall be 3/16 inch (4.8 mm) high minimum based on the uppercase letter “I”. Characters shall contrast with their background with either light characters on a dark background or dark characters on a light background.7

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

Stylistic rewording

Explanatory update

Functional change

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE 1: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

402.5 Characters on Variable Message Signs. Characters on variable message signs shall conform to section 703.7 Variable Message Signs of ICC A117.1-2009 (incorporated by reference, see 702.6.1).8

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

Explanatory update

Functional change

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE 1: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

List tables

403 Biometrics

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

403.1 General Biometrics shall not be the only means for user identification or control.

EXCEPTION: Where at least two biometric options that use different biological characteristics are provided, ICT shall be permitted to use biometrics as the only means of user identification or control.

5.3 Biometrics

Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.

NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.

NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals with disabilities possess at least one of the specified biological characteristics. Examples of dissimilar biological characteristics are fingerprints, eye retinal patterns, voice, and face.

Stylistic rewording

Explanatory update

5.3 Biometrics

Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.

NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.

NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals with disabilities possess at least one of the specified biological characteristics. Examples of dissimilar biological characteristics are fingerprints, eye retinal patterns, voice, and face.

5.3 Biometrics

Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.

NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.

NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals with disabilities possess at least one of the specified biological characteristics. Examples of dissimilar biological characteristics are fingerprints, eye retinal patterns, voice, and face.

5.3 Biometrics

Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.

NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.

NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals with disabilities possess at least one of the specified biological characteristics.

List tables

404 Preservation of Information Provided for Accessibility

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
404.1 General ICT that transmits or converts information or communication shall not remove non-proprietary information provided for accessibility or shall restore it upon delivery.

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

Stylistic rewording

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

List tables

405 Privacy

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

405.1 General

The same degree of privacy of input and output shall be provided to all individuals. When speech output required by 402.2 is enabled, the screen shall not blank automatically.9

5.1.3.9 Private access to personal data

Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.

NOTE 1: This requirement does not apply in cases where data is not defined as being private according to the applicable privacy policy or where there is no applicable privacy policy.

NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

Stylistic rewording

Explanatory update

5.1.3.9 Private access to personal data

Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.

NOTE 1: This requirement does not apply in cases where data is not defined as being private according to the applicable privacy policy or where there is no applicable privacy policy.

NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.9 Private access to personal data

Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.

NOTE 1: This requirement does not apply in cases where data is not defined as being private according to the applicable privacy policy or where there is no applicable privacy policy.

NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.9 Private access to personal data

Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.

NOTE 1: This requirement does not apply in cases where data is not defined as being private according to the applicable privacy policy or where there is no applicable privacy policy.

NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

405.1 General The same degree of privacy of input and output shall be provided to all individuals. When speech output required by 402.2 is enabled, the screen shall not blank automatically.10

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

Stylistic rewording

Explanatory update

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

List tables

406 Standard Connections

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
406.1 General Where data connections used for input and output are provided, at least one of each type of connection shall conform to industry standard non-proprietary formats.

8.1.2 Standard connections

Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.

NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the use of standard connections on ICT.

NOTE 2: The word connection applies to both physical and wireless connections.

NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.

Stylistic rewording

Explanatory update

8.1.2 Standard connections

Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.

NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the use of standard connections on ICT.

NOTE 2: The word connection applies to both physical and wireless connections.

NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.

8.1.2 Standard connections

Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.

NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the use of standard connections on ICT.

NOTE 2: The word connection applies to both physical and wireless connections.

NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.

8.1.2 Standard connections

Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.

NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the use of standard connections on ICT.

NOTE 2: The word connection applies to both physical and wireless connections.

NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.

List tables

407 Operable Parts

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

407.3.1 Tactilely Discernible

Input controls shall be operable by touch and tactilely discernible without activation.

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

Stylistic rewording

Explanatory update

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

407.3.1 Tactilely Discernible

Input controls shall be operable by touch and tactilely discernible without activation.

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

Stylistic rewording

Explanatory update

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and the status of that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

Explanatory update

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and the status of that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

407.3.2 Alphabetic Keys Where provided, individual alphabetic keys shall be arranged in a QWERTY-based keyboard layout and the “F” and “J” keys shall be tactilely distinct from the other keys.11

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

Stylistic rewording

Explanatory update

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

407.3.3 Numeric Keys

Where provided, numeric keys shall be arranged in a 12-key ascending or descending keypad layout. The number five key shall be tactilely distinct from the other keys. Where the ICT provides an alphabetic overlay on numeric keys, the relationships between letters and digits shall conform to ITU-T Recommendation E.161 (incorporated by reference, see 702.7.1).12

8.4.1 Numeric keys

Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.

NOTE: Recommendation ITU-T E.161 describes the 12-key telephone keypad layout and provides further details of the form of tactile markers.

Stylistic rewording

Explanatory update

8.4.1 Numeric keys

Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.

NOTE: Recommendation ITU-T E.161 describes the 12-key telephone keypad layout and provides further details of the form of tactile markers.

8.4.1 Numeric keys

Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.

NOTE: Recommendation ITU-T E.161 describes the 12-key telephone keypad layout and provides further details of the form of tactile markers.

8.4.1 Numeric keys

Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.

NOTE: Recommendation ITU-T E.161 [i.20] describes the 12-key telephone keypad layout and provides further details of the form of tactile markers.

407.4 Key Repeat

Where a keyboard with key repeat is provided, the delay before the key repeat feature is activated shall be fixed at, or adjustable to, 2 seconds minimum.

5.7: Key repeat

Where ICT with key repeat is provided and the key repeat cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

Stylistic rewording

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

Stylistic rewording

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

407.6 Operation

At least one mode of operation shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate operable parts shall be 5 pounds (22.2 N) maximum.

5.5.1 Means of operation

Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.

Stylistic rewording

Explanatory update

5.5.1 Means of operation

Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.

5.5.1 Means of operation

Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.

5.5.1 Means of operation

Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.

407.6 Operation At least one mode of operation shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate operable parts shall be 5 pounds (22.2 N) maximum.

8.4.2.1 Means of Operation of mechanical parts

Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.

Stylistic rewording

Explanatory update

8.4.2.1 Means of operation of mechanical parts

Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.

8.4.2.1 Means of operation of mechanical parts

Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.

8.4.2.1 Means of operation of mechanical parts

Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.

407.6 Operation At least one mode of operation shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate operable parts shall be 5 pounds (22.2 N) maximum.

8.4.2.2 Force of operation of mechanical parts

Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.

Stylistic rewording

Explanatory update

8.4.2.2 Force of operation of mechanical parts

Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.

8.4.2.2 Force of operation of mechanical parts

Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.

NOTE: ISO 21542:2011: Building Construction - Accessibility and Usability of the Built Environment recommends a value between 2,5 and 5 Newtons.

Explanatory update

8.4.2.2 Force of operation of mechanical parts

Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.

NOTE: ISO 21542:2011 [i.34]: Building Construction - Accessibility and Usability of the Built Environment recommends a value between 2,5 and 5 Newtons.

407.7 Tickets, Fare Cards, and Keycards

Where tickets, fare cards, or keycards are provided, they shall have an orientation that is tactilely discernible if orientation is important to further use of the ticket, fare card, or keycard.

8.4.3 Keys, tickets and fare cards

Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.

NOTE: ETS 300 767 defines suitable tactile indications for plastic cards.

Stylistic rewording

Explanatory update

8.4.3 Keys, tickets and fare cards

Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.

NOTE: ETSI ETS 300 767 defines suitable tactile indications for plastic cards.

Explanatory update

8.4.3 Keys, tickets and fare cards

Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.

NOTE: ETSI ETS 300 767 defines suitable tactile indications for plastic cards.

8.4.3 Keys, tickets and fare cards

Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.

NOTE: ETSI ETS 300 767 [i.6] defines suitable tactile indications for plastic cards.

407.8.1.1 Vertical Plane for Side Reach

Where a side reach is provided, the vertical reference plane shall be 48 inches (1220 mm) long minimum.

8.3.2.2 Clear floor or ground space

Where the operating area is integral to the ICT, it should provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

Stylistic rewording

Explanatory update

8.3.2.2 Clear floor or ground space

Where the operating area is integral to the ICT, it should provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

8.3.4.2 Clear floor or ground space

Where stationary ICT has an operating area within it, it shall provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

Numbering change

Stylistic rewording

Functional change

8.3.4.2 Clear floor or ground space

Where stationary ICT has an operating area within it, it shall provide a clear floor area that has the minimum

dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

407.8.1.2 Vertical Plane for Forward Reach Where a forward reach is provided, the vertical reference plane shall be 30 inches (760 mm) long minimum.

8.3.2.2 Clear floor or ground space

Where the operating area is integral to the ICT, it should provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

Stylistic rewording

Explanatory update

8.3.2.2 Clear floor or ground space

Where the operating area is integral to the ICT, it should provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

8.3.4.2 Clear floor or ground space

Where stationary ICT has an operating area within it, it shall provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

Numbering change

Stylistic rewording

Functional change

8.3.4.2 Clear floor or ground space

Where stationary ICT has an operating area within it, it shall provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

407.8.2.1 Unobstructed Side Reach

Where the operable part is located 10 inches (255 mm) or less beyond the vertical reference plane, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.

8.3.3.2.1 Unobstructed high side reach

Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.2.1 Unobstructed high side reach

Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space.

8.3.3.1 Unobstructed high side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.3.1 Unobstructed high side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space.

407.8.2.1 Unobstructed Side Reach Where the operable part is located 10 inches (255 mm) or less beyond the vertical reference plane, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.

8.3.3.2.2 Unobstructed low side reach

Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.2.2 Unobstructed low side reach

Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space.

8.3.3.2 Unobstructed low side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

Explanatory update

8.3.3.2 Unobstructed low side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space.

407.8.2.2 Obstructed Side Reach

Where the operable part is located more than 10 inches (255 mm), but not more than 24 inches (610 mm), beyond the vertical reference plane, the height of the operable part shall be 46 inches (1170 mm) high maximum and 15 inches (380 mm) high minimum above the floor. The operable part shall not be located more than 24 inches (610 mm) beyond the vertical reference plane.

8.3.3.2.3.1 Obstructed (<= 255 mm) side reach

Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is less than or equal to 255 mm (10 inches), the high side reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.2.3.1 Obstructed (<= 255 mm) side reach

Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is less than or equal to 255 mm (10 inches), the high side reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor of the access space.

8.3.3.3.1 Obstructed (<= 255 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is less than or equal to 255 mm (10 inches), the high side reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.3.3.1 Obstructed (≤ 255 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is less than or equal to 255 mm (10 inches), the high side reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor of the access space.

407.8.2.2 Obstructed Side Reach

Where the operable part is located more than 10 inches (255 mm), but not more than 24 inches (610 mm), beyond the vertical reference plane, the height of the operable part shall be 46 inches (1170 mm) high maximum and 15 inches (380 mm) high minimum above the floor. The operable part shall not be located more than 24 inches (610 mm) beyond the vertical reference plane.

8.3.3.2.3.2 Obstructed (<= 610 mm) side reach

Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is greater than 255 mm (10 inches) and 610 mm (24 inches) maximum, the high side reach to all essential controls should be no higher than 1 170 mm (46 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.2.3.2 Obstructed (<= 610 mm) side reach

Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is greater than 255 mm (10 inches) with a maximum depth of 610 mm (24 inches), the high side reach to all essential controls should be no higher than 1 170 mm (46 inches) above the floor of the access space.

Stylistic rewording

8.3.3.3.2 Obstructed (<= 610 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is greater than 255 mm (10 inches) with a maximum depth of 610 mm (24 inches), the high side reach to at least one of each type of operable part shall be no higher than 1 170 mm (46 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

Explanatory update

8.3.3.3.2 Obstructed (≤ 610 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is greater than 255 mm (10 inches) with a maximum depth of 610 mm (24 inches), the high side reach to at least one of each type of operable part shall be no higher than 1 170 mm (46 inches) above the floor of the access space.

407.8.3 Forward Reach

Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

8.3.3.1.1 Unobstructed high forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no higher than 1 220 mm (48 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.1 Unobstructed high forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no higher than 1 220 mm (48 inches) above the floor of the access space.

8.3.2.1 Unobstructed high forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no higher than 1 220 mm (48 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

8.3.2.1 Unobstructed high forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no higher than 1 220 mm (48 inches) above the floor of the access space.

407.8.3 Forward Reach

Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

8.3.3.1.2 Unobstructed low forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no lower than 380 mm (15 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.2 Unobstructed low forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no lower than 380 mm (15 inches) above the floor of the access space.

8.3.2.2 Unobstructed low forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no lower than 380 mm (15 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

8.3.2.2 Unobstructed low forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no lower than 380 mm (15 inches) above the floor of the access space.

407.8.3 Forward Reach

Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory

Functional change

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

407.8.3 Forward Reach

Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

407.8.3.1 Unobstructed Forward Reach Where the operable part is located at the leading edge of the maximum protrusion within the length of the vertical reference plane of the ICT, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.

8.3.3.1.1 Unobstructed high forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no higher than 1 220 mm (48 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.1.1 Unobstructed high forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no higher than 1 220 mm (48 inches) above the floor of the access space.

8.3.2.1 Unobstructed high forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no higher than 1 220 mm (48 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

8.3.2.1 Unobstructed high forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no higher than 1 220 mm (48 inches) above the floor of the access space.

407.8.3.1 Unobstructed Forward Reach Where the operable part is located at the leading edge of the maximum protrusion within the length of the vertical reference plane of the ICT, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.

8.3.3.1.2 Unobstructed low forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no lower than 380 mm (15 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.1.2 Unobstructed low forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no lower than 380 mm (15 inches) above the floor of the access space.

8.3.2.2 Unobstructed low forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no lower than 380 mm (15 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

8.3.2.2 Unobstructed low forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no lower than 380 mm (15 inches) above the floor of the access space.

407.8.3.2 Obstructed Forward Reach Where the operable part is located beyond the leading edge of the maximum protrusion within the length of the vertical reference plane, the operable part shall conform to 407.8.3.2. The maximum allowable forward reach to an operable part shall be 25 inches (635 mm).

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory

Functional change

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

407.8.3.2 Obstructed Forward Reach Where the operable part is located beyond the leading edge of the maximum protrusion within the length of the vertical reference plane, the operable part shall conform to 407.8.3.2. The maximum allowable forward reach to an operable part shall be 25 inches (635 mm).

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach The height of the operable part shall conform to Table 407.8.3.2.1.

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory

Functional change

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach The height of the operable part shall conform to Table 407.8.3.2.1.

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach

Knee and toe space under ICT shall be 27 inches (685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30 inches (760 mm) wide minimum and shall be clear of obstructions.

EXCEPTIONS:

  1. Toe space shall be permitted to provide a clear height of 9 inches (230 mm) above the floor and a clear depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT.
  2. At a depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT, space between 9 inches (230 MM) and 27 inches (685 mm) minimum above the floor shall be permitted to reduce at a rate of 1 inch (25 mm) in depth for every 6 inches (150 mm) in height.13

8.3.2.4 Knee and toe clearance width

Where the space under an obstacle that is integral to the ICT is part of access space, the clearance should be at least 760 mm (30 inches) wide.

Stylistic rewording

Explanatory update

8.3.2.4 Knee and toe clearance width

Where the space under an obstacle that is integral to the ICT is part of access space, the clearance should be at least 760 mm (30 inches) wide.

8.3.2.4 Knee and toe clearance width

Where the space under an obstacle that is an integral part of the stationary ICT is part of access space, the clearance shall be at least 760 mm (30 inches) wide.

Stylistic rewording

Functional change

8.3.2.4 Knee and toe clearance width

Where the space under an obstacle that is an integral part of the stationary ICT is part of access space, the clearance shall be at least 760 mm (30 inches) wide.

407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach Knee and toe space under ICT shall be 27 inches (685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30 inches (760 mm) wide minimum and shall be clear of obstructions.

EXCEPTIONS:

  1. Toe space shall be permitted to provide a clear height of 9 inches (230 mm) above the floor and a clear depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT.
  2. At a depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT, space between 9 inches (230 mm) and 27 inches (685 mm) minimum above the floor shall be permitted to reduce at a rate of 1 inch (25 mm) in depth for every 6 inches (150 mm) in height.14

8.3.2.5 Toe clearance

Where an obstacle is integral to the ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and should:

  1. extend 635 mm (25 inches) maximum under the whole obstacle;
  2. provide a space at least 430 mm (17 inches) deep and 230 mm above the floor under the obstacle;
  3. extend no more than150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

Stylistic rewording

Explanatory update

Functional change

8.3.2.5 Toe clearance

Where an obstacle is integral to the ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and should:

  1. extend 635 mm (25 inches) maximum under the whole obstacle;
  2. provide a space at least 430 mm (17 inches) deep and 230 mm above the floor under the obstacle;
  3. extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

8.3.2.5 Toe clearance

Where an obstacle is an integral part of the stationary ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and shall:

  1. extend 635 mm (25 inches) maximum under the whole obstacle;
  2. provide a space at least 430 mm (17 inches) deep and 230 mm (9 inches) above the floor under the obstacle;
  3. extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

Stylistic rewording

Functional change

Explanatory update

8.3.2.5 Toe clearance

Where an obstacle is an integral part of the stationary ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and shall:

  1. extend 635 mm (25 inches) maximum under the whole obstacle;
  2. provide a space at least 430 mm (17 inches) deep and 230 mm (9 inches) above the floor under the obstacle;
  3. extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach Knee and toe space under ICT shall be 27 inches (685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30 inches (760 mm) wide minimum and shall be clear of obstructions.

EXCEPTIONS:

  1. Toe space shall be permitted to provide a clear height of 9 inches (230 mm) above the floor and a clear depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT.
  2. At a depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT, space between 9 inches (230 MM) and 27 inches (685 mm) minimum above the floor shall be permitted to reduce at a rate of 1 inch (25 mm) in depth for every 6 inches (150 mm) in height.15

8.3.2.6 Knee clearance

Where an obstacle is integral to the ICT, the space under the obstacle that is between 230 mm and 685 mm above the floor is considered knee clearance and should:

  1. extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  2. extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  3. extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;
  4. be between 230 mm (9 inches) and 685 mm (27 inches) above the floor be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.

Stylistic rewording

Explanatory update

Functional change

8.3.2.6 Knee clearance

Where an obstacle is integral to the ICT, the space under the obstacle that is between 230 mm and 685 mm above the floor is considered knee clearance and should:

  1. extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  2. extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  3. extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;
  4. d) be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.
Stylistic rewording

8.3.2.6 Knee clearance

Where an obstacle is an integral part of the stationary ICT, the space under the obstacle that is between 230 mm (9 inches) and 685 mm (25 inches)16 above the floor is considered knee clearance and shall:

  1. extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  2. extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  3. extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;
  4. d) be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.

Stylistic rewording

Explanatory update

Functional change

8.3.2.6 Knee clearance

Where an obstacle is an integral part of the stationary ICT, the space under the obstacle that is between 230 mm (9 inches) and 685 mm (25 inches) above the floor is considered knee clearance and shall:

  1. extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  2. extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  3. extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;
  4. d) be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.

List tables

408 Display Screen

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
408.2 Visibility Where stationary ICT provides one or more display screens, at least one of each type of display screen shall be visible from a point located 40 inches (1015 mm) above the floor space where the display screen is viewed.

8.3.4 Visibility

Where the operating area is integral to the ICT, and a display screen is provided, information on the screen should be legible from a point located 1 015 mm (40 inches) above the centre of the floor of the operating area (as defined in clause 8.3.2.2).

NOTE: The intent of this provision is that the information on the screen can be read by users with normal vision and appropriate language skills, when seated in a wheelchair.

Stylistic rewording

Explanatory update

8.3.4 Visibility

Where the operating area is integral to the ICT, and a display screen is provided, information on the screen should be legible from a point located 1 015 mm (40 inches) above the centre of the floor of the operating area (as defined in clause 8.3.2.2).

NOTE: The intent of this provision is that the information on the screen can be read by users with normal vision and appropriate language skills, when seated in a wheelchair.

8.3.5 Visibility

Where stationary ICT provides one or more display screens , at least one of each type of display screen shall be positioned such that the information on the screen is legible from a point located 1 015 mm (40 inches) above the centre of the floor of the operating area).

NOTE: The intent of this requirement is that the information on the screen can be read by users with normal vision and appropriate language skills, when seated in a wheelchair.

Numbering change

Stylistic rewording

Functional change

8.3.5 Visibility

Where stationary ICT provides one or more display screens, at least one of each type of display screen shall be positioned such that the information on the screen is legible from a point located 1 015 mm (40 inches) above the centre of the floor of the operating area).

NOTE: The intent of this requirement is that the information on the screen can be read by users with normal vision and appropriate language skills, when seated in a wheelchair.

List tables

409 Status Indicators

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

409.1 General

Where provided, status indicators shall be discernible visually and by touch or sound.

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

Stylistic rewording

Explanatory update

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and the status of that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

Explanatory update

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and the status of that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

409.1 General Where provided, status indicators shall be discernible visually and by touch or sound.

5.6.2 Visual status

Where ICT has a locking or toggle control and the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example of making the status of a control determinable is a visual status indicator on a keyboard.

Stylistic rewording

Explanatory update

5.6.2 Visual status

Where ICT has a locking or toggle control and the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example of making the status of a control determinable is a visual status indicator on a keyboard.

5.6.2 Visual status

Where ICT has a locking or toggle control and the status of the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example of making the status of a control determinable is a visual status indicator on a keyboard.

Explanatory update

5.6.2 Visual status

Where ICT has a locking or toggle control and the status of the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example of making the status of a control determinable is a visual status indicator on a keyboard.

List tables

410 Color Coding

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
410.1 General Where provided, color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

8.1.3 Colour

Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Stylistic rewording

8.1.3 Colour

Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

8.1.3 Colour

Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

8.1.3 Colour

Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

List tables

412 ICT with Two-Way Voice Communication

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

412.2.1 Volume Gain for Wireline Telephones

Volume gain conforming to 47 CFR 68.317 shall be provided on analog and digital wireline telephones.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

Stylistic rewording

Explanatory update

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

412.2.1 Volume Gain for Wireline Telephones

Volume gain conforming to 47 CFR 68.317 shall be provided on analog and digital wireline telephones.17

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

Stylistic rewording

Explanatory update

Functional change

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

412.2.2 Volume Gain for Non-Wireline ICT

A method for increasing volume shall be provided for non-wireline ICT.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

Stylistic rewording

Explanatory update

Functional change

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

412.2.2 Volume Gain for Non-Wireline ICT

A method for increasing volume shall be provided for non-wireline ICT.18

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

Stylistic rewording

Explanatory update

Functional change

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

412.3.1 Wireless Handsets

ICT in the form of wireless handsets shall conform to ANSI/IEEE C63.19-2011 (incorporated by reference, see 702.5.1).19

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

Stylistic rewording

Explanatory update

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

Explanatory update

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

412.3.2 Wireline Handsets

ICT in the form of wireline handsets, including cordless handsets, shall conform to TIA-1083-B (incorporated by reference, see 702.9.1).20

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETS 300 381, it shall provide a means of magnetic coupling which meets the requirements of ES 200 381-1.

NOTE: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

Stylistic rewording

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETSI ETS 300 381, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1.

NOTE: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1 and shall carry the "T" symbol specified in ETSI ETS 300 381.

NOTE 1: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

NOTE 2: Magnetic coupling is also known as inductive coupling for T-coil.

Stylistic rewording

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1 and shall carry the "T" symbol specified in ETSI ETS 300 381.

NOTE 1: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause. NOTE 2: Magnetic coupling is also known as inductive coupling for T-coil.

412.4 Digital Encoding of Speech

ICT in IP-based networks shall transmit and receive speech that is digitally encoded in the manner specified by ITU-T Recommendation G.722.2 (incorporated by reference, see 702.7.2) or IETF RFC 6716 (incorporated by reference, see 702.8.1).21

6.1: Audio bandwidth for speech (informative recommendation)

Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT should be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7 000 Hz.

NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 is widely used.

NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation ITU-T G.722.2 are sometimes used so as to avoid transcoding.

Stylistic rewording

Explanatory update

Functional change

6.1 Audio bandwidth for speech

Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT shall be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7 000 Hz.

NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 is widely used.

NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation ITU-T G.722.2 are sometimes used so as to avoid transcoding.

Functional change

6.1 Audio bandwidth for speech

Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT shall be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7 000 Hz.

NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 is widely used.

NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation ITU-T G.722.2 are sometimes used so as to avoid transcoding.

6.1 Audio bandwidth for speech

Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT shall be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7 000 Hz.

NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 is widely used.

NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation ITU-T G.722.2 are sometimes used so as to avoid transcoding.

412.5 Real-Time Text Functionality [Reserved].22See RTT requirements in EN 301 549 V1.1.1 (2014) Chapter 6, below.See RTT requirements in EN 301 549 V2.1.2 (2018) Chapter 6, below.See RTT requirements in EN 301 549 V3.1.1 (2019) Chapter 6, below.See RTT requirements in EN 301 549 V3.2.1 (2021) Chapter 6, below.
412.6 Caller ID Where provided, caller identification and similar tele-communications functions shall be visible and audible.23

6.3: Caller ID

Where ICT provides caller identification and similar tele-communications functions are provided, the caller identification and similar tele-communications functions shall be available in text form and in at least one other modality.

Stylistic rewording

Explanatory update

Functional change

6.3 Caller ID

Where ICT provides caller identification or similar tele-communications functions are provided, the caller identification and similar tele-communications functions shall be available in text form and in at least one other modality.

6.3 Caller ID

Where ICT provides caller identification or similar tele-communications functions, the caller identification and similar tele-communications functions shall be available in text form as well as being programmatically determinable, unless the functionality is closed.

Functional change

6.3 Caller ID

Where ICT provides caller identification or similar telecommunications functions, the caller identification and similar telecommunications functions shall be available in text form as well as being programmatically determinable, unless the functionality is closed.

412.7 Video Communication Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.24

6.5.1 General (informative)

Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with Common Intermediate Format (CIF) resolution, a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.

When the resolution is reduced to Quarter Common Intermediate Format (QCIF) and the frame rate drops to 12 frames per second the communication is still usable with some restrictions.

A lower resolution causes less disturbance to the perception of sign language and lip-reading than that caused by a lower frame rate.

Delay can be a problem in video communication. Overall delay values below 0,4 s are preferred, with an increase in preference down to 0,1 s. Values over 0,8 s are felt to hinder a good sign conversation. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.

Stylistic rewording

Explanatory update

Functional change

6.5.1 General (informative)

Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with Common Intermediate Format (CIF) resolution, a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.

When the resolution is reduced to Quarter Common Intermediate Format (QCIF) and the frame rate drops to 12 frames per second the communication is still usable with some restrictions.

A lower resolution causes less disturbance to the perception of sign language and lip-reading than that caused by a lower frame rate.

Delay can be a problem in video communication. Overall delay values below 0,4 s are preferred, with an increase in preference down to 0,1 s. Values over 0,8 s are felt to hinder a good sign conversation. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.

6.5.1 General (informative)

Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with a resolution of at least Quarter Video Graphics Array (QVGA, 320 x 240), a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.

Increasing the resolution and frame rate further improves both sign language (especially finger spelling) and lip-reading, with frame rate being more important than resolution.

Time differences between audio and video (asynchronicity) can have a great impact onlip-reading - with video that lags behind audio having greater negative effect.

End-to-end latency can be a problem in video (sign) communication. Overall delay values below 400 ms are preferred, with an increase in preference down to 100 ms. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.

NOTE: Recommendation ITU-T F.703 defines and gives requirements for Total Conversation that relate to the integration of audio, RTT and video in a single user connection.

Functional change

Explanatory update

Stylistic rewording

6.5.1 General (informative)

Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with a resolution of at least Quarter Video Graphics Array (QVGA, 320 x 240), a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.

Increasing the resolution and frame rate further improves both sign language (especially finger spelling) and lipreading, with frame rate being more important than resolution.

Time differences between audio and video (asynchronicity) can have a great impact onlip-reading - with video that lags behind audio having greater negative effect.

End-to-end latency can be a problem in video (sign) communication. Overall delay values below 400 ms are preferred, with an increase in preference down to 100 ms. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.

NOTE: Recommendation ITU-T F.703 defines and gives requirements for Total Conversation that relate to the integration of audio, RTT and video in a single user connection.

412.7 Video Communication Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.25

6.5.2 Resolution

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support at least QCIF resolution;

b) should preferably support at least CIF resolution.

Stylistic rewording

Explanatory update

Functional change

6.5.2 Resolution

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support at least QCIF resolution;

b) should preferably support at least CIF resolution.

6.5.2 Resolution

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support at least QVGA resolution;

b) should preferably support at least VGA resolution.

Functional update

6.5.2 Resolution

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support at least QVGA resolution;

b) should preferably support at least VGA resolution.

412.7 Video Communication Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.26

6.5.3 Frame rate

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support a frame rate of at least 12 frames per second (FPS);

b) should preferably support a frame rate of at least 20 frames per second (FPS) with or without sign language in the video stream.

Stylistic rewording

Explanatory update

Functional change

6.5.3 Frame rate

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support a frame rate of at least 12 frames per second (FPS);

b) should preferably support a frame rate of at least 20 frames per second (FPS) with or without sign language in the video stream.

6.5.3 Frame rate

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support a frame rate of at least 20 frames per second (FPS);

b) should preferably support a frame rate of at least 30 frames per second (FPS) with or without sign language in the video stream.

Functional update

6.5.3 Frame rate

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support a frame rate of at least 20 Frames Per Second (FPS);

b) should preferably support a frame rate of at least 30 Frames Per Second (FPS) with or without sign language in the video stream.

Stylistic change
412.7 Video Communication Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.27

6.5.4 Synchronization between audio and video

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT should ensure a maximum time difference of 100 ms between the speech and video presented to the user.

Stylistic rewording

Explanatory update

Functional change

6.5.4 Synchronization between audio and video

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT should ensure a maximum time difference of 100 ms between the speech and video presented to the user.

6.5.4 Synchronization between audio and video

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT shall ensure a maximum time difference of 100 ms between the speech and video presented to the user.

NOTE: Recent research shows that, if audio leads the video, the intelligibility suffers much more than the reverse.

Functional change

Explanatory update

6.5.4 Synchronization between audio and video

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT shall ensure a maximum time difference of 100 ms between the speech and video presented to the user.

NOTE: Recent research shows that, if audio leads the video, the intelligibility suffers much more than the reverse.

List tables

413 Closed Caption Processing Technologies

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
413.1.1 Decoding and Display of Closed Captions Players and displays shall decode closed caption data and support display of captions.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

Stylistic rewording

Explanatory update

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

Functional change

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

NOTE 3: Clause 7.1.1 refers to the ability of the player to display captions. Clauses 9.1.2.2, 10.1.2.2 and 11.1.2.2 refer to the provision of captions for the content (the video).

Explanatory update
413.1.2 Pass-Through of Closed Caption Data Cabling and ancillary equipment shall pass through caption data.

5.4: Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

Stylistic rewording

Explanatory update

Functional change

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

413.1.2 Pass-Through of Closed Caption Data Cabling and ancillary equipment shall pass through caption data.

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

Stylistic rewording

Explanatory update

Functional change

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

List tables

414 Audio Description Processing Technologies

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

414.1.1 Digital Television Tuners

Digital television tuners shall provide audio description processing that conforms to ATSC A/53 Digital Television Standard, Part 5 (2014) (incorporated by reference, see 702.2.1). Digital television tuners shall provide processing of audio description when encoded as a Visually Impaired (VI) associated audio service that is provided as a complete program mix containing audio description according to the ATSC A/53 standard.28

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

Stylistic rewording

Explanatory update

Functional change

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

414.1.2 Other ICT

ICT other than digital television tuners shall provide audio description processing.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

Stylistic rewording

Explanatory update

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

List tables

415 User Controls for Captions and Audio Descriptions

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

415.1.1 Caption Controls

Where ICT provides operable parts for volume control, ICT shall also provide operable parts for caption selection.29

7.3: User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

Stylistic rewording

Explanatory update

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

415.1.2 Audio Description Controls

Where ICT provides operable parts for program selection, ICT shall also provide operable parts for the selection of audio description.30

7.3: User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

Stylistic rewording

Explanatory update

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

List tables

Chapter 5: Software

501 General

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

501.1 Scope

The requirements of Chapter 5 shall apply to software where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

EXCEPTION: Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

Chapters 9, 10, and 11 apply WCAG 2.0 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).

Explanatory update

Stylistic rewording

Chapters 9, 10, and 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).Functional changeChapters 9, 10, and 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).Chapters 9, 10, and 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).

List tables

502 Interoperability with Assistive Technology

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
502.2.1 User Control of Accessibility Features Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features.

11.4.1 User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

Stylistic rewording

11.6.1 User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

Numbering change

11.6.1 User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

11.6.1 User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

502.2.2 No Disruption of Accessibility Features Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.

11.4.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

Stylistic rewording

Explanatory update

11.6.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

Numbering change

11.6.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

11.6.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

502.3 Accessibility Services

Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms hall expose the underlying platform accessibility services or implement other documented accessibility services.

11.3.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Platform software should support requirements 11.3.2.5 to 11.3.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.3.2.5 to 11.3.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.3.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality of software providing user interfaces when using platform services.

NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 3: User interface services that provide accessibility support by default are considered to be part of the services provided to conform to this clause (i.e. the service for creating a new user interface element provides role, state, boundary, name and description).

NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

NOTE 5: Within specific programming environments, the technical attributes associated with the user interface properties described in clauses 11.3.2.5 to 11.3.2.17 might have different names than those used within the clauses.

Stylistic rewording

Explanatory update

11.5.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Platform software should support requirements 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality of software providing user interfaces when using platform services.

NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 3: User interface services that provide accessibility support by default are considered to be part of the services provided to conform to this clause (e.g. the service for creating a new user interface element provides role, state, boundary, name and description).

NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

NOTE 5: Within specific programming environments, the technical attributes associated with the user interface properties described in clauses 11.5.2.5 to 11.5.2.17 might have different names than those used within the clauses.

Numbering change

Stylistic rewording

11.5.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Where a user interface concept corresponding to one of the clauses 11.5.2.5 to 11.5.2.17 is supported within the software environment, the platform software should support that requirement. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality of software providing user interfaces when using platform services.

NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 3: User interface services that provide accessibility support by default are considered to be part of the services provided to conform to this clause (e.g. the service for creating a new user interface element provides role, state, boundary, name and description).

NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

NOTE 5: Within specific programming environments, the technical attributes associated with the user interface properties described in clauses 11.5.2.5 to 11.5.2.17 might have different names than those used within the clauses.

Stylistic rewording

11.5.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Where a user interface concept corresponding to one of the clauses 11.5.2.5 to 11.5.2.17 is supported within the software environment, the platform software should support that requirement. For example, selection attributes from clause 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality of software providing user interfaces when using platform services.

NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 3: User interface services that provide accessibility support by default are considered to be part of the services provided to conform to this clause (e.g. the service for creating a new user interface element provides role, state, boundary, name and description).

NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

NOTE 5: Within specific programming environments, the technical attributes associated with the user interface properties described in clauses 11.5.2.5 to 11.5.2.17 might have different names than those used within the clauses.

502.3 Accessibility Services

Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms hall expose the underlying platform accessibility services or implement other documented accessibility services.

11.3.2.2 Platform accessibility service support for assistive technologies

Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.

Platform software should support the requirements of clauses 11.3.2.5 to 11.3.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.3.2.5 to 11.3.2.17 is not supported within the software environment, these requirement are not applicable. For example, selection attributes from 11.3.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.

NOTE 2: The definition of platform in 3.1 applies to software that provides services to other software, including but not limited to, operating systems, internet browsers, virtual machines.

NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 4: Typically these services belong to the same set of services that are described in clause 11.3.2.1.

NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

Stylistic rewording

Explanatory update

11.5.2.2 Platform accessibility service support for assistive technologies

Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.

Platform software should support the requirements of clauses 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirement are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.

NOTE 2: The definition of platform in clause 3.1 applies to software that provides services to other software, including but not limited to, operating systems, web browsers, virtual machines.

NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 4: Typically these services belong to the same set of services that are described in clause 11.5.2.1.

NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

Numbering change

Stylistic rewording

11.5.2.2 Platform accessibility service support for assistive technologies

Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.

Where a user interface concept corresponding to one of the clauses 11.5.2.5 to 11.5.2.17 is supported within the software environment, the platform software should support that requirement. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.

NOTE 2: The definition of platform in clause 3.1 applies to software that provides services to other software, including but not limited to, operating systems, web browsers, virtual machines.

NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 4: Typically these services belong to the same set of services that are described in clause 11.5.2.1.

NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

Stylistic rewording

11.5.2.2 Platform accessibility service support for assistive technologies

Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.

Where a user interface concept corresponding to one of the clauses 11.5.2.5 to 11.5.2.17 is supported within the software environment, the platform software should support that requirement. For example, selection attributes from clause 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.

NOTE 2: The definition of platform in clause 3.1 applies to software that provides services to other software, including but not limited to, operating systems, web browsers, virtual machines.

NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 4: Typically these services belong to the same set of services that are described in clause 11.5.2.1.

NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

502.3.1 Object Information

The object role, state(s), properties, boundary, name, and description shall be programmatically determinable.

11.3.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

Numbering change

11.5.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

11.5.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

502.3.2 Modification of Object Information States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology.

11.3.2.16 Modifications of states and properties

When permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Stylistic rewording

Explanatory update

Functional change

11.5.2.16 Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Numbering change

Stylistic rewording

11.5.2.16 Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.16 Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

502.3.3 Row, Column, and Headers

If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable.

11.3.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

Numbering change

11.5.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

11.5.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

502.3.4 Values Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable.

11.3.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.3.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

Numbering change

11.5.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

11.5.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

502.3.5 Modification of Values

Values that can be set by the user shall be capable of being set programmatically, including through assistive technology.

11.3.2.17 Modifications of values and text

When permitted by security requirements, software that provides a user interface shall, by using the services as described in 11.3.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Stylistic rewording

Explanatory update

Functional change

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Numbering change

Stylistic rewording

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

502.3.6 Label Relationships Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable.

11.3.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.3.2.3, so that this information is programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.

Numbering change

11.5.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.

11.5.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.

502.3.7 Hierarchical Relationships Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable.

11.3.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

Numbering change

11.5.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

11.5.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

502.3.8 Text

The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable.

11.3.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

Numbering change

11.5.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

11.5.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

502.3.9 Modification of Text

Text that can be set by the user shall be capable of being set programmatically, including through assistive technology.

11.3.2.17 Modifications of values and text

When permitted by security requirements, software that provides a user interface shall, by using the services as described in 11.3.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Stylistic rewording

Explanatory update

Functional change

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Numbering change

Stylistic rewording

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

502.3.10 List of Actions

A list of all actions that can be executed on an object shall be programmatically determinable.

11.3.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

Numbering change

11.5.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

11.5.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

502.3.11 Actions on Objects

Applications shall allow assistive technology to programmatically execute available actions on objects.

11.3.2.12 Execution of available actions

When permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow the programmatic execution of the actions exposed according to clause 11.3.2.11 by assistive technologies.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Stylistic rewording

Explanatory update

Functional change

11.5.2.12 Execution of available actions

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Numbering change

Stylistic rewording

11.5.2.12 Execution of available actions

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.12 Execution of available actions

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

502.3.12 Focus Cursor

Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components.

11.3.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

Numbering change

11.5.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

11.5.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

502.3.13 Modification of Focus Cursor Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.

11.3.2.14 Modification of focus and selection attributes

When permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Stylistic rewording

Explanatory update

Functional change

11.5.2.14 Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Numbering change

Stylistic rewording

11.5.2.14 Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.14 Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

502.3.14 Event Notification Notification of events relevant to user interactions, including but not limited to, changes in the component’s state(s), value, name, description, or boundary, shall be available to assistive technology.

11.3.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in 11.3.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.3.2.5 to 11.3.2.11 and 11.3.2.13.

Stylistic rewording

Explanatory update

11.5.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

Numbering change

Stylistic rewording

11.5.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

11.5.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

502.4 Platform Accessibility Features

Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:

See A-G, below.See A-G, below.See A-G, below.See A-G, below.
  1. Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;31

5.9: Simultaneous user actions

Where ICT uses simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.

NOTE: Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or having to touch a surface with more than one finger are examples of simultaneous user actions.

Stylistic rewording

Explanatory update

5.9 Simultaneous user actions

Where ICT uses simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.

NOTE: Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or having to touch a surface with more than one finger are examples of simultaneous user actions.

5.9 Simultaneous user actions

Where ICT has a mode of operation requiring simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.

NOTE: Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or having to touch a surface with more than one finger are examples of simultaneous user actions.

Stylistic rewording

5.9 Simultaneous user actions

Where ICT has a mode of operation requiring simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.

NOTE: Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or having to touch a surface with more than one finger are examples of simultaneous user actions.

  1. Section 9.3.4 Provide adjustment of delay before key acceptance;

5.7: Key repeat

Where ICT with key repeat is provided and the key repeat cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

Stylistic rewording

Explanatory update

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

Stylistic rewording

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

  1. Section 9.3.5 Provide adjustment of same-key double-strike acceptance;32

5.8: Double-strike key acceptance

Where a keyboard or keypad is provided, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.

Stylistic rewording

Explanatory update

5.8 Double-strike key acceptance

Where ICT has a keyboard or keypad, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.

Stylistic rewording

5.8 Double-strike key acceptance

Where ICT has a keyboard or keypad, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.

5.8 Double-strike key acceptance

Where ICT has a keyboard or keypad, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.

  1. Section 10.7.1 Display any captions provided.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

Stylistic rewording

Explanatory update

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

Functional change

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

NOTE 3: Clause 7.1.1 refers to the ability of the player to display captions. Clauses 9.1.2.2, 10.1.2.2 and 11.1.2.2 refer to the provision of captions for the content (the video).

Explanatory change

List tables

503 Applications

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

503.2 User Preferences Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.

EXCEPTION: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2.

11.5 User preferences

Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for colour, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms.

NOTE: Software that is isolated from its underlying platform has no access to user settings in the platform and thus cannot adhere to them.

Stylistic rewording

Explanatory update

11.7 User preferences

Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for colour, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms.

NOTE: Software that is isolated from its underlying platform has no access to user settings in the platform and thus cannot adhere to them.

Numbering change

11.7 User preferences

Where software is not designed to be isolated from its platform, and provides a user interface, that user interface shall follow the values of the user preferences for platform settings for: units of measurement, colour, contrast, font type, font size, and focus cursor except where they are overridden by the user.

NOTE 1: Software that is isolated from its underlying platform has no access to user settings in the platform and thus cannot adhere to them.

NOTE 2: For web content, the underlying platform is the user agent.

NOTE 3: This does not preclude the software from having additional values for a setting as long as there is one mode where the application will follow the system settings even if more restricted.

Stylistic rewording

Functional change

11.7 User preferences

Where software is not designed to be isolated from its platform, and provides a user interface, that user interface shall follow the values of the user preferences for platform settings for: units of measurement, colour, contrast, font type, font size, and focus cursor except where they are overridden by the user.

NOTE 1: Software that is isolated from its underlying platform has no access to user settings in the platform and thus cannot adhere to them.

NOTE 2: For web content, the underlying platform is the user agent.

NOTE 3: This does not preclude the software from having additional values for a setting as long as there is one mode where the application will follow the system settings even if more restricted.

503.3 Alternative User Interfaces Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.

11.3.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.3.2.1 and 11.3.2.2.

NOTE 2: Assistive technology can also use other documented accessibility services.

Stylistic rewording

Explanatory update

11.5.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

NOTE 2: Assistive technology can also use other documented accessibility services.

Numbering change

11.5.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

NOTE 2: Assistive technology can also use other documented accessibility services.

11.5.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

NOTE 2: Assistive technology can also use other documented accessibility services.

503.4 User Controls for Captions and Audio Description Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

Stylistic rewording

Explanatory update

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

Functional change

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

NOTE 3: Clause 7.1.1 refers to the ability of the player to display captions. Clauses 9.1.2.2, 10.1.2.2 and 11.1.2.2 refer to the provision of captions for the content (the video).

Explanatory update
503.4.1 Caption Controls Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

Stylistic rewording

Explanatory update

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

503.4.2 Audio Description Controls Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

Stylistic rewording

Explanatory update

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

List tables

504 Authoring Tools

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
504.1 General Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.11.6.1 Content technology Authoring tools shall conform to clauses 11.6.2 to 11.6.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.Stylistic rewording

11.8.1 Content technology

Authoring tools shall conform to clauses 11.8.2 to 11.8.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.

Numbering change11.8.1 Content technology Authoring tools shall conform to clauses 11.8.2 to 11.8.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.

11.8.1 Content technology

Authoring tools shall conform to clauses 11.8.2 to 11.8.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.

504.2 Content Creation or Editing Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility.

EXCEPTION: Authoring tools shall not be required to conform to 504.2 when used to directly edit plain text source code.

11.6.2 Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

NOTE: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

Stylistic rewording

Explanatory update

11.8.2 Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

NOTE: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

Numbering change

11.8.2 Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

NOTE: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

11.8.2 Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

NOTE: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format.

11.6.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

Stylistic rewording

Explanatory update

11.8.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

Numbering change

11.8.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

11.8.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

504.3 Prompts Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for supported features and, as applicable, to file formats supported by the authoring tool.

11.6.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web content) or 10 (Documents) as applicable, then the authoring tool shall provide repair suggestion(s).

NOTE: This does not preclude automated and semi-automated repair which is possible (and encouraged) for many types of content accessibility problems.

Stylistic rewording

Explanatory update

Functional change

11.8.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

NOTE: This does not preclude automated and semi-automated repair which is possible (and encouraged) for many types of content accessibility problems.

Numbering change

Stylistic rewording

11.8.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

NOTE: This does not preclude automated and semi-automated repair which is possible (and encouraged) for many types of content accessibility problems.

11.8.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

NOTE: This does not preclude automated and semi-automated repair which is possible (and encouraged) for many types of content accessibility problems.

504.4 Templates Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool.

11.6.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web content) or 10 (Documents) as applicable shall be available and identified as such.

Stylistic rewording

Explanatory update

11.8.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.

Numbering change

Stylistic rewording

11.8.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.

11.8.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.

List tables

Chapter 6: Support Documentation and Services

602 Support Documentation

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
602.2 Accessibility and Compatibility Features Documentation shall list and explain how to use the accessibility and compatibility features required by Chapters 4 and 5. Documentation shall include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

12.1.1 Accessibility and compatibility features

Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

Stylistic rewording

Explanatory update

12.1.1 Accessibility and compatibility features

Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

12.1.1 Accessibility and compatibility features

Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.

NOTE 1: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

NOTE 2: It is best practice to use WebSchemas/Accessibility 2.0 to provide meta data on the accessibility of the ICT.

NOTE 3: The accessibility statement and help pages are both examples of the provision of product information.

Functional change

12.1.1 Accessibility and compatibility features

Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.

NOTE 1: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

NOTE 2: It is best practice to use WebSchemas/Accessibility 2.0 [i.38] to provide meta data on the accessibility of the ICT.

NOTE 3: The accessibility statement and help pages are both examples of the provision of product information.

602.3 Electronic Support Documentation Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9, or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which is accessible.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

Stylistic rewording

Explanatory update

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9, or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which is accessible.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9; or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic, printed or audio) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with limited cognitive, language and learning abilities).

NOTE 3: Where documentation is incorporated into the ICT, the documentation falls under the requirements for accessibility in the present document.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

Functional change

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9; or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic, printed or audio) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with limited cognitive, language and learning abilities).

NOTE 3: Where documentation is incorporated into the ICT, the documentation falls under the requirements for accessibility in the present document.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

602.4 Alternate Formats for Non-Electronic Support Documentation Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9, or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which is accessible.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

Stylistic rewording

Explanatory update

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9, or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which is accessible.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9; or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic, printed or audio) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with limited cognitive, language and learning abilities).

NOTE 3: Where documentation is incorporated into the ICT, the documentation falls under the requirements for accessibility in the present document.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

Functional change

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9; or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic, printed or audio) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with limited cognitive, language and learning abilities).

NOTE 3: Where documentation is incorporated into the ICT, the documentation falls under the requirements for accessibility in the present document.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

List tables

603 Support Services

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
603.1 General ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.

12.2.1 General (informative)

ICT support services include, but are not limited to: help desks, call centres, technical support, relay services and training services.

Stylistic rewording

12.2.1 General (informative)

ICT support services include, but are not limited to: help desks, call centres, technical support, relay services and training services.

12.2.1 General (informative)

ICT support services include, but are not limited to: help desks, call centres, technical support, relay services and training services.

12.2.1 General (informative)

ICT support services include, but are not limited to: help desks, call centres, technical support, relay services and training services.

603.2 Information on Accessibility and Compatibility Features

ICT support services shall include information on the accessibility and compatibility features required by 602.2.

12.2.2 Information on accessibility and compatibility features

ICT support services shall provide information on the accessibility and compatibility features that are included in the product documentation.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

Stylistic rewording

Explanatory update

12.2.2 Information on accessibility and compatibility features

ICT support services shall provide information on the accessibility and compatibility features that are included in the product documentation.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

12.2.2 Information on accessibility and compatibility features

ICT support services shall provide information on the accessibility and compatibility features that are mentioned in the product documentation.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

12.2.2 Information on accessibility and compatibility features

ICT support services shall provide information on the accessibility and compatibility features that are mentioned in the product documentation.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

603.3 Accommodation of Communication Needs

Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities.

12.2.3 Effective communication

ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.

Stylistic rewording

Explanatory update

12.2.3 Effective communication

ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.

12.2.3 Effective communication

ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.

12.2.3 Effective communication

ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.

List tables

Provisions Not Mapped

Revised Section 508

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

402.3 Volume

ICT that delivers sound, including speech output required by 402.2, shall provide volume control and output amplification conforming to 402.3.

EXCEPTION: ICT conforming to 412.2 shall not be required to conform to 402.3.

407.1 General Where provided, operable parts used in the normal operation of ICT shall conform to 407.
407.2 Contrast Where provided, keys and controls shall contrast visually from background surfaces. Characters and symbols shall contrast visually from background surfaces with either light characters or symbols on a dark background or dark characters or symbols on a light background.

407.3 Input Controls

At least one input control conforming to 407.3 shall be provided for each function.

EXCEPTION: Devices for personal use with input controls that are audibly discernable without activation and operable by touch shall not be required to conform to 407.3.

407.5 Timed Response

Where a timed response is required, the user shall be alerted visually, as well as by touch or sound, and shall be given the opportunity to indicate that more time is needed.33

407.8 Reach Height and Depth At least one of each type of operable part of stationary ICT shall be at a height conforming to 407.8.2 or 407.8.3 according to its position established by the vertical reference plane specified in 407.8.1 for a side reach or a forward reach. Operable parts used with speech output required by 402.2 shall not be the only type of operable part complying with 407.8 unless that part is the only operable part of its type.34
407.8.1 Vertical Reference Plane Operable parts shall be positioned for a side reach or a forward reach determined with respect to a vertical reference plane. The vertical reference plane shall be located in conformance to 407.8.2 or 407.8.3.

407.8.2 Side Reach

Operable parts of ICT providing a side reach shall conform to 407.8.2.1 or 407.8.2.2. The vertical reference plane shall be centered on the operable part and placed at the leading edge of the maximum protrusion of the ICT within the length of the vertical reference plane. Where a side reach requires a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

408.1 General Where provided, display screens shall conform to 408.

408.3 Flashing Where ICT emits lights in flashes, there shall be no more than three flashes in any one-second period.

EXCEPTION: Flashes that do not exceed the general flash and red flash thresholds defined in WCAG 2.0 (incorporated by reference, see 702.10.1) are not required to conform to 408.3. 35

411.1 General Where provided, audible signals or cues shall not be used as the only means of conveying information, indicating an action, or prompting a response.36

412.1 General

ICT that provides two-way voice communication shall conform to 412.

412.2 Volume Gain

ICT that provides two-way voice communication shall conform to 412.2.1 or 412.2.2.

412.3 Interference Reduction and Magnetic Coupling Where ICT delivers output by a handset or other type of audio transducer that is typically held up to the ear, ICT shall reduce interference with hearing technologies and provide a means for effective magnetic wireless coupling in conformance with 412.3.1 or 412.3.2.

412.8 Legacy TTY Support

ICT equipment or systems with two-way voice communication that do not themselves provide TTY functionality shall conform to 412.8.

412.8.1 TTY Connectability

ICT shall include a standard non-acoustic connection point for TTYs.

412.8.2 Voice and Hearing Carry Over

ICT shall provide a microphone capable of being turned on and off to allow the user to intermix speech with TTY use.

412.8.3 Signal Compatibility

ICT shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols where the system interoperates with the Public Switched Telephone Network (PSTN).

412.8.4 Voice Mail and Other Messaging Systems

Where provided, voice mail, auto-attendant, interactive voice response, and caller identification systems shall be usable with a TTY.

413.1 General

Where ICT displays or processes video with synchronized audio, ICT shall provide closed caption processing technology that conforms to 413.1.1 or 413.1.2.

414.1 General Where ICT displays or processes video with synchronized audio, ICT shall provide audio description processing technology conforming to 414.1.1 or 414.1.2.

415.1 General Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 415.1.

EXCEPTION: Devices for personal use shall not be required to conform to 415.1 provided that captions and audio descriptions can be enabled through system-wide platform settings.

502.1 General Software shall interoperate with assistive technology and shall conform to 502.

EXCEPTION: ICT conforming to 402 shall not be required to conform to 502.

502.4 Platform Accessibility Features

Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:

  1. Section 10.6.7 Allow users to choose visual alternative for audio output;37

502.4 Platform Accessibility Features

Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:

  1. Section 10.6.8 Synchronize audio equivalents for visual events;38

502.4 Platform Accessibility Features

Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:

  1. Section 10.6.9 Provide speech output services;39

504.2.2 PDF Export

Authoring tools capable of exporting PDF files that conform to ISO 32000-1:2008 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1) (incorporated by reference, see 702.3.1).40

List tables

EN 301 549

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
­­­

4.2.11 Privacy

Where ICT provides features that are provided for accessibility, some users will need their privacy to be maintained when using those ICT features that are provided for accessibility. NOTE: Enabling the connection of personal headsets for private listening, not providing a spoken version of characters being masked and enabling user control of legal, financial and personal data are examples of design features that may contribute towards meeting this clause.

4.2.11 Privacy

Where ICT provides features that are provided for accessibility, some users will need their privacy to be maintained when using those ICT features that are provided for accessibility. NOTE: Enabling the connection of personal headsets for private listening, not providing a spoken version of characters being masked and enabling user control of legal, financial and personal data are examples of design features that may contribute towards meeting this clause.

4.2.11 Privacy

Where ICT provides features for accessibility, the ICT maintains the privacy of users of these features at the same level as other users.

NOTE: Enabling the connection of personal headsets for private listening, not providing a spoken version of characters being masked and enabling user control of legal, financial and personal data are examples of design features that may contribute towards meeting this clause.

4.2.11 Privacy

Where ICT provides features for accessibility, the ICT maintains the privacy of users of these features at the same level as other users.

NOTE: Enabling the connection of personal headsets for private listening, not providing a spoken version of characters being masked and enabling user control of legal, financial and personal data are examples of design features that may contribute towards meeting this clause.

4.2.9 Minimize photosensitive seizure triggers

Where ICT provides visual modes of operation, some users need ICT to provide at least one mode of operation that minimizes the potential for triggering photosensitive seizures.

NOTE: Limiting the area and number of flashes per second may contribute towards meeting this clause.

4.2.9 Minimize photosensitive seizure triggers

Where ICT provides visual modes of operation, some users need ICT to provide at least one mode of operation that minimizes the potential for triggering photosensitive seizures.

NOTE: Limiting the area and number of flashes per second may contribute towards meeting this clause.

4.2.9 Minimize photosensitive seizure triggers

Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that minimizes the potential for triggering photosensitive seizures. This is essential for users with photosensitive seizure triggers.

NOTE: Limiting the area and number of flashes per second may contribute towards meeting this clause.

4.2.9 Minimize photosensitive seizure triggers

Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that minimizes the potential for triggering photosensitive seizures. This is essential for users with photosensitive seizure triggers.

NOTE: Limiting the area and number of flashes per second may contribute towards meeting this clause.

5.1.2.1 Closed functionality

Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.

NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to the requirements of clause 5.1.

NOTE 2: The requirements within this clause replace those in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. This may be because they relate to compatibility with assistive technology or to the ability for the user to adjust system accessibility settings in products with closed functionality (e.g. products that prevent access to the system settings control panel).

5.1.2.1 Closed functionality

Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.

NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to the requirements of clause 5.1.

NOTE 2: The requirements within this clause replace those in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. This may be because they relate to compatibility with assistive technology or to the ability for the user to adjust system accessibility settings in products with closed functionality (e.g. products that prevent access to the system settings control panel).

5.1.2.1 Closed functionality

Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.

NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to the requirements of clause 5.1.

NOTE 2: The requirements within this clause replace those in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. This may be because they relate to compatibility with assistive technology or to the ability for the user to adjust system accessibility settings in products with closed functionality (e.g. products that prevent access to the system settings control panel).

5.1.2.1 Closed functionality

Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.

NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to the requirements of clause 5.1.

NOTE 2: The requirements within this clause replace those in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. This may be because they relate to compatibility with assistive technology or to the ability for the user to adjust system accessibility settings in products with closed functionality (e.g. products that prevent access to the system settings control panel).

5.1.3.10 Non-interfering audio output

Where auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.

5.1.3.10 Non-interfering audio output

Where auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.

5.1.3.10 Non-interfering audio output

Where auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.

5.1.3.10 Non-interfering audio output

Where auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.

5.1.3.14 Spoken languages

Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:

  1. for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text;
  2. where the content is generated externally and not under the control of the ICT vendor, clause 5.1.3.14 shall not be required to apply for languages not supported by the ICT's speech synthesizer;
  3. for displayed languages that cannot be selected using non-visual access;
  4. where the user explicitly selects a speech language that is different from the language of the displayed content.

5.1.3.14 Spoken languages

Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:

  1. for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text;
  2. where the content is generated externally and not under the control of the ICT vendor, clause 5.1.3.14 shall not be required to apply for languages not supported by the ICT's speech synthesizer;
  3. for displayed languages that cannot be selected using non-visual access;
  4. where the user explicitly selects a speech language that is different from the language of the displayed content.

5.1.3.14 Spoken languages

Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:

  1. for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text;
  2. where the content is generated externally and not under the control of the ICT vendor, the present clause shall not be required to apply for languages not supported by the ICT's speech synthesizer;
  3. for displayed languages that cannot be selected using non-visual access;
  4. where the user explicitly selects a speech language that is different from the language of the displayed content.
Stylistic rewording

5.1.3.14 Spoken languages

Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:

  1. for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text;
  2. where the content is generated externally and not under the control of the ICT vendor, the present clause shall not be required to apply for languages not supported by the ICT's speech synthesizer;
  3. for displayed languages that cannot be selected using non-visual access;
  4. where the user explicitly selects a speech language that is different from the language of the displayed content.

5.1.3.15 Non-visual error identification

Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.

5.1.3.15 Non-visual error identification

Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.

5.1.3.15 Non-visual error identification

Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.

5.1.3.15 Non-visual error identification

Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.

5.1.5 Visual output for auditory information

Where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the pre-recorded auditory output.

NOTE: This visual information can take the form of captions or text transcripts.

5.1.5 Visual output for auditory information

Where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the pre-recorded auditory output.

NOTE: This visual information can take the form of captions or text transcripts.

5.1.5 Visual output for auditory information

Where auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the auditory output.

NOTE: This visual information can take the form of captions or text transcripts.

Stylistic rewording

5.1.5 Visual output for auditory information

Where auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the auditory output.

NOTE: This visual information can take the form of captions or text transcripts.

5.1.6.1 Closed functionality

Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.

5.1.6.1 Closed functionality

Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.

5.1.6.1 Closed functionality

Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.

5.1.6.1 Closed functionality

Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.

5.1.6.2 Input focus

Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.

5.1.6.2 Input focus

Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.

5.1.6.2 Input focus

Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.

5.1.6.2 Input focus

Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.

5.1.7 Access without speech

Where speech is needed to operate closed functions of ICT, the ICT shall provide at least one mode of operation using an alternative input mechanism that does not require speech.

New requirement

5.1.7 Access without speech

Where speech is needed to operate closed functions of ICT, the ICT shall provide at least one mode of operation using an alternative input mechanism that does not require speech.

6.2.1.1 RTT communication

Where ICT supports two-way voice communication in a specified context of use, the ICT shall allow a user to communicate with another user by RTT.

NOTE 1: The RTT capability can be provided as a factory default or added later.

NOTE 2: Provision of RTT may require additional service provision, additional hardware and/or software which may be provided separately or together.

6.2.1.1 RTT communication

Where ICT supports two-way voice communication in a specified context of use, the ICT shall allow a user to communicate with another user by RTT.

NOTE 1: The RTT capability can be provided as a factory default or added later.

NOTE 2: Provision of RTT may require additional service provision, additional hardware and/or software which may be provided separately or together.

6.2.1.1 RTT communication

Where ICT is in a mode that provides a means for two-way voice communication, the ICT shall provide a means for two-way RTT communication, except where this would require design changes to add input or output hardware to the ICT.

NOTE 1: This requirement includes those products which do not have physical display or text entry capabilities but have the capability to connect to devices that do have such capabilities. It also includes intermediate ICT between the endpoints of the communication.

NOTE 2: There is no requirement to add: a hardware display, a hardware keyboard, or hardware to support the ability to connect to a display or keyboard, wired or wirelessly, if this hardware would not normally be provided.

NOTE 3: For the purposes of interoperability, support of Recommendation ITU-T T.140 is widely used.

Stylistic rewording

Functional change

Explanatory update

6.2.1.1 RTT communication

Where ICT is in a mode that provides a means for two-way voice communication, the ICT shall provide a means for two-way RTT communication, except where this would require design changes to add input or output hardware to the ICT.

NOTE 1: This requirement includes those products which do not have physical display or text entry capabilities but have the capability to connect to devices that do have such capabilities. It also includes intermediate ICT between the endpoints of the communication.

NOTE 2: There is no requirement to add: a hardware display, a hardware keyboard, or hardware to support the ability to connect to a display or keyboard, wired or wirelessly, if this hardware would not normally be provided.

NOTE 3: For the purposes of interoperability, support of Recommendation ITU-T T.140 is widely used.

6.2.1.2 Concurrent voice and text

Where ICT supports two-way voice communication in a specified context of use, and enables a user to communicate with another user by RTT, it shall provide a mechanism to select a mode of operation which allows concurrent voice and text.

NOTE: The availability of voice and RTT running concurrently can allow the RTT to replace or support voice and transfer additional information such as numbers, currency amounts and spelling of names.

6.2.1.2 Concurrent voice and text

Where ICT supports two-way voice communication in a specified context of use, and enables a user to communicate with another user by RTT, it shall provide a mechanism to select a mode of operation which allows concurrent voice and text.

NOTE: The availability of voice and RTT running concurrently can allow the RTT to replace or support voice and transfer additional information such as numbers, currency amounts and spelling of names.

6.2.1.2 Concurrent voice and text

Where ICT provides a means for two-way voice communication and for users to communicate by RTT, it shall allow concurrent voice and text through a single user connection.

NOTE 1: With many-party communication, as in a conference system, it is allowed (but not required or necessarily recommended) that RTT be handled in a single display field and that "turn-taking" be necessary to avoid confusion (in the same way that turn-taking is required for those presenting/talking with voice).

NOTE 2: With many-party communication, best practice is for hand-raising for voice users and RTT users to be handled in the same way, so that voice and RTT users are in the same queue.

NOTE 3: With a many-party conference system that has chat as one of its features - the RTT (like the voice) would typically be separate from the chat so that RTT use does not interfere with chat (i.e. people can be messaging in the chat field while the person is presenting/talking with RTT - in the same manner that people message using the chat feature while people are talking with voice). RTT users would then use RTT for presenting and use the Chat feature to message while others are presenting (via Voice or RTT).

NOTE 4: The availability of voice and RTT running concurrently (and separately from chat) can also allow the RTT field to support text captioning when someone is speaking (and it is therefore not being used for RTT since it is not the RTT user's turn to speak).

NOTE 5: Where both server-side software and local hardware and software are required to provide voice communication, where neither part can support voice communication without the other and are sold as a unit for the voice communication function, the local and server-side components are considered a single product.

Stylistic rewording

Functional change

Explanatory update

6.2.1.2 Concurrent voice and text

Where ICT provides a means for two-way voice communication and for users to communicate by RTT, it shall allow concurrent voice and text through a single user connection.

NOTE 1: With many-party communication, as in a conference system, it is allowed (but not required or necessarily recommended) that RTT be handled in a single display field and that "turn-taking" be necessary to avoid confusion (in the same way that turn-taking is required for those presenting/talking with voice).

NOTE 2: With many-party communication, best practice is for hand-raising for voice users and RTT users to be handled in the same way, so that voice and RTT users are in the same queue.

NOTE 3: With a many-party conference system that has chat as one of its features - the RTT (like the voice) would typically be separate from the chat so that RTT use does not interfere with chat (i.e. people can be messaging in the chat field while the person is presenting/talking with RTT - in the same manner that people message using the chat feature while people are talking with voice). RTT users would then use RTT for presenting and use the Chat feature to message while others are presenting (via Voice or RTT).

NOTE 4: The availability of voice and RTT running concurrently (and separately from chat) can also allow the RTT field to support text captioning when someone is speaking (and it is therefore not being used for RTT since it is not the RTT user's turn to speak).

NOTE 5: Where both server-side software and local hardware and software are required to provide voice communication, where neither part can support voice communication without the other and are sold as a unit for the voice communication function, the local and server-side components are considered a single product.

6.2.2.1 Visually distinguishable display

Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from and separated from received text.

6.2.2.1 Visually distinguishable display

Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from and separated from received text.

6.2.2.1 Visually distinguishable display

Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from, and separated from, received text.

NOTE: The ability of the user to choose between having the send and receive text be displayed in-line or separately, and with options to select, allows users to display RTT in a form that works best for them. This would allow Braille users to use a single field and take turns and have text appear in the sequential way that they may need or prefer.

Explanatory update

6.2.2.1 Visually distinguishable display

Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from, and separated from, received text.

NOTE: The ability of the user to choose between having the send and receive text be displayed in-line or separately, and with options to select, allows users to display RTT in a form that works best for them. This would allow Braille users to use a single field and take turns and have text appear in the sequential way that they may need or prefer.

6.2.2.2 Programmatically determinable send and receive direction

Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted text shall be programmatically determinable, unless the RTT has closed functionality.

NOTE: The intent of clause 6.2.2.2 is to enable screen readers to be able to distinguish between incoming text and outgoing text when used with RTT functionality.

6.2.2.2 Programmatically determinable send and receive direction

Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted text shall be programmatically determinable, unless the RTT has closed functionality.

NOTE: The intent of this clause is to enable screen readers to be able to distinguish between incoming text and outgoing text when used with RTT functionality.

Stylistic rewording

6.2.2.2 Programmatically determinable send and receive direction

Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted/received text shall be programmatically determinable, unless the RTT is implemented as closed functionality.

NOTE: This enables screen readers to distinguish between incoming text and outgoing text when used with RTT functionality.

Functional change

Stylistic rewording

6.2.2.2 Programmatically determinable send and receive direction

Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted/received text shall be programmatically determinable, unless the RTT is implemented as closed functionality.

NOTE: This enables screen readers to distinguish between incoming text and outgoing text when used with RTT functionality.

6.2.2.3 Speaker identification

Where ICT has RTT capabilities, and provides speaker identification for voice, the ICT shall provide speaker identification for RTT.

NOTE: This is necessary to enable both voice and RTT participants to know who is currently communicating, whether it be in RTT or voice.

New requirement

6.2.2.3 Speaker identification

Where ICT has RTT capabilities, and provides speaker identification for voice, the ICT shall provide speaker identification for RTT.

NOTE: This is necessary to enable both voice and RTT participants to know who is currently communicating, whether it be in RTT or voice.

6.2.2.4 Visual indicator of Audio with RTT

Where ICT provides two-way voice communication, and has RTT capabilities, the ICT shall provide a real-time visual indicator of audio activity on the display.

NOTE 1: The visual indicator may be a simple character position on the display that flickers on and off to reflect audio activity, or presentation of the information in another way that can be both visible to sighted users and passed on to deaf-blind users who are using a braille display.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

New requirement

6.2.2.4 Visual indicator of Audio with RTT

Where ICT provides two-way voice communication, and has RTT capabilities, the ICT shall provide a real-time visual indicator of audio activity on the display.

NOTE 1: The visual indicator may be a simple character position on the display that flickers on and off to reflect audio activity, or presentation of the information in another way that can be both visible to sighted users and passed on to deaf-blind users who are using a braille display.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

6.2.3 Interoperability

Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by 6.2.1.1) they shall support at least one of the four RTT interoperability mechanisms described below:

  1. ICT interoperating over the Public Switched Telephone Network (PSTN), with other ICT that directly connects to the PSTN as described in Recommendation ITU-T V.18 or any of its annexes for text telephony signals at the PSTN interface;
  2. ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using real-time text that conforms to RFC 4103;
  3. ICT interoperating with other ICT using RTT that conforms with the IP Multimedia Sub-System (IMS) set of protocols specified in TS 126 114, TS 122 173 and TS 134 229;
  4. ICT interoperating with other ICT using a relevant and applicable common specification for RTT exchange that is published and available. This common specification shall include a method for indicating loss or corruption of characters.

6.2.3 Interoperability

Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by clause 6.2.1.1) they shall support at least one of the four RTT interoperability mechanisms described below:

  1. ICT interoperating over the Public Switched Telephone Network (PSTN), with other ICT that directly connects to the PSTN as described in Recommendation ITU-T V.18 or any of its annexes for text telephony signals at the PSTN interface;
  2. ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using real-time text that conforms to IETF RFC 4103;
  3. ICT interoperating with other ICT using RTT that conforms with the IP Multimedia Sub-System (IMS) set of protocols specified in ETSI TS 126 114, ETSI TS 122 173 and ETSI TS 134 229;
  4. ICT interoperating with other ICT using a relevant and applicable common specification for RTT exchange that is published and available. This common specification shall include a method for indicating loss or corruption of characters.

Stylistic rewording

Explanatory update

6.2.3 Interoperability

Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by clause 6.2.1.1) they shall support the applicable RTT interoperability mechanisms described below:

  1. ICT interoperating with other ICT directly connected to the Public Switched Telephone Network (PSTN), using Recommendation ITU-T V.18 or any of its annexes for text telephony signals at the PSTN interface;
  2. ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using RTT that conforms to IETF RFC 4103. For ICT interoperating with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, the set of protocols specified in ETSI TS 126 114, ETSI TS 122 173 and ETSI TS 134 229 describe how IETF RFC 4103 would apply;
  3. ICT interoperating with other ICT using technologies other than a or b, above, using a relevant and applicable common specification for RTT exchange that is published and available for the environments in which they will be operating. This common specification shall include a method for indicating loss or corruption of characters.
  4. ICT interoperating with other ICT using a standard for RTT that has been introduced for use in any of the above environments, and is supported by all of the other active ICT that support voice and RTT in that environment.

NOTE 1: In practice, new standards are introduced as an alternative codec/protocol that is supported alongside the existing common standard and used when all end-to-end components support it while technology development, combined with other reasons including societal development and cost efficiency, may make others become obsolete.

NOTE 2: Where multiple technologies are used to provide voice communication, multiple interoperability mechanisms may be needed to ensure that all users are able to use RTT.

EXAMPLE: A conferencing system that supports voice communication through an internet connection might provide RTT over an internet connection using a proprietary RTT method (option c). However, regardless of whether the RTT method is proprietary or non-proprietary, if the conferencing system also offers telephony communication it will also need to support options a or b to ensure that RTT is supported over the telephony connection.

Stylistic rewording

Explanatory update

Functional change

6.2.3 Interoperability

Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by clause 6.2.1.1) they shall support the applicable RTT interoperability mechanisms described below:

  1. ICT interoperating with other ICT directly connected to the Public Switched Telephone Network (PSTN), using Recommendation ITU-T V.18 [i.23] or any of its annexes for text telephony signals at the PSTN interface;
  2. ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using RTT that conforms to IETF RFC 4103 [i.13]. For ICT interoperating with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, the set of protocols specified in ETSI TS 126 114 [i.10], ETSI TS 122 173 [i.11] and ETSI TS 134 229 [i.12] describe how IETF RFC 4103 [i.13] would apply;
  3. ICT interoperating with other ICT using technologies other than a or b, above, using a relevant and applicable common specification for RTT exchange that is published and available for the environments in which they will be operating. This common specification shall include a method for indicating loss or corruption of characters;
  4. ICT interoperating with other ICT using a standard for RTT that has been introduced for use in any of the above environments, and is supported by all of the other active ICT that support voice and RTT in that environment.

NOTE 1: In practice, new standards are introduced as an alternative codec/protocol that is supported alongside the existing common standard and used when all end-to-end components support it while technology development, combined with other reasons including societal development and cost efficiency, may make others become obsolete.

NOTE 2: Where multiple technologies are used to provide voice communication, multiple interoperability mechanisms may be needed to ensure that all users are able to use RTT.

EXAMPLE: A conferencing system that supports voice communication through an internet connection might provide RTT over an internet connection using a proprietary RTT method (option c). However, regardless of whether the RTT method is proprietary or non-proprietary, if the conferencing system also offers telephony communication it will also need to support options a or b to ensure that RTT is supported over the telephony connection.

6.2.4 Real-time responsiveness

Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network supporting RTT within 1 second of the input entry.

NOTE 1: Input entry is considered to have occurred when sufficient user input has occurred for the ICT to establish which character(s) to send.

NOTE 2: Input entry will differ between systems where text is entered on a word-by-word basis (e.g. speech-to-text and predictive-text based systems) and systems where each character is separately generated.

6.2.4 Real-time text responsiveness

Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network supporting RTT within 1 second of the input entry.

NOTE 1: Input entry is considered to have occurred when sufficient user input has occurred for the ICT to establish which character(s) to send.

NOTE 2: Input entry will differ between systems where text is entered on a word-by-word basis (e.g. speech-to-text and predictive-text based systems) and systems where each character is separately generated.

6.2.4 RTT responsiveness

Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network or platform on which the ICT runs within 500 ms of the time that the smallest reliably composed unit of text entry is available to the ICT for transmission. Delays due to platform or network performance shall not be included in the 500 ms limit.

NOTE 1: For character by character input, the "smallest reliably composed unit of text entry" would be a character.

For word prediction it would be a word. For some voice recognition systems - the text may not exit the recognition software until an entire word (or phrase) has been spoken. In this case, the smallest reliably composed unit of text entry available to the ICT would be the word (or phrase).

NOTE 2: The 500 ms limit allows buffering of characters for this period before transmission so character by character transmission is not required unless the characters are generated more slowly than 1 per 500 ms.

NOTE 3: A delay of 300 ms, or less, produces a better impression of flow to the user.

Stylistic rewording

Functional change

Explanatory update

6.2.4 RTT responsiveness

Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network or platform on which the ICT runs within 500 ms of the time that the smallest reliably composed unit of text entry is available to the ICT for transmission. Delays due to platform or network performance shall not be included in the 500 ms limit.

NOTE 1: For character by character input, the "smallest reliably composed unit of text entry" would be a character. For word prediction it would be a word. For some voice recognition systems - the text may not exit the recognition software until an entire word (or phrase) has been spoken. In this case, the smallest reliably composed unit of text entry available to the ICT would be the word (or phrase).

NOTE 2: The 500 ms limit allows buffering of characters for this period before transmission so character by character transmission is not required unless the characters are generated more slowly than 1 per 500 ms.

NOTE 3: A delay of 300 ms, or less, produces a better impression of flow to the user.

6.4 Alternatives to voice-based services

Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT should offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.

NOTE: Solutions capable of handling audio, real-time text and video media could satisfy the above requirement.

6.4 Alternatives to voice-based services

Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT should offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.

NOTE: Solutions capable of handling audio, real-time text and video media could satisfy the above requirement.

6.4 Alternatives to voice-based services

Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT shall offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.

NOTE 1: Tasks that involve both operating the interface and perceiving the information would require that both the interface and information be accessible without use of speech or hearing.

NOTE 2: Solutions capable of handling audio, RTT and video media could satisfy the above requirement.

Functional change

Explanatory update

Stylistic rewording

6.4 Alternatives to voice-based services

Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT shall offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.

NOTE 1: Tasks that involve both operating the interface and perceiving the information would require that both the interface and information be accessible without use of speech or hearing.

NOTE 2: Solutions capable of handling audio, RTT and video media could satisfy the above requirement.

6.5.5 Visual indicator of audio with video

Where ICT provides two-way voice communication, and includes real-time video functionality, the ICT shall provide a real-time visual indicator of audio activity.

NOTE 1: The visual indicator may be a simple visual dot or LED, or other type of on/off indicator, that flickers to reflect audio activity.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

New requirement

6.5.5 Visual indicator of audio with video

Where ICT provides two-way voice communication, and includes real-time video functionality, the ICT shall provide a real-time visual indicator of audio activity.

NOTE 1: The visual indicator may be a simple visual dot or LED, or other type of on/off indicator, that flickers to reflect audio activity.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

6.5.6 Speaker identification with video (sign language) communication

Where ICT provides speaker identification for voice users, it shall provide a means for speaker identification for real-time signing and sign language users once the start of signing has been indicated.

NOTE 1: The speaker ID can be in the same location as for voice users for multiparty calls.

NOTE 2: This mechanism might be triggered manually by a user, or automatically where this is technically achievable.

New requirement

6.5.6 Speaker identification with video (sign language) communication

Where ICT provides speaker identification for voice users, it shall provide a means for speaker identification for real-time signing and sign language users once the start of signing has been indicated.

NOTE 1: The speaker ID can be in the same location as for voice users for multiparty calls.

NOTE 2: This mechanism might be triggered manually by a user, or automatically where this is technically achievable.

6.6 Alternatives to video-based services

Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:

  1. for audible information, without the use of hearing;
  2. for spoken commands, without the use of speech;
  3. for visual information, without the use of vision.

NOTE: Solutions capable of generating real-time captions or handling real-time text could satisfy the above requirement.

6.6 Alternatives to video-based services

Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:

  1. for audible information, without the use of hearing;
  2. for spoken commands, without the use of speech;
  3. for visual information, without the use of vision.

NOTE: Solutions capable of generating real-time captions or handling real-time text could satisfy the above requirement.

6.6 Alternatives to video-based services

Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:

  1. for audible information, without the use of hearing;
  2. for spoken commands, without the use of speech;
  3. for visual information, without the use of vision.

NOTE: Solutions capable of generating real-time captions or handling RTT could satisfy the above requirement.

Stylistic rewording

6.6 Alternatives to video-based services

Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:

  1. for audible information, without the use of hearing;
  2. for spoken commands, without the use of speech;
  3. for visual information, without the use of vision.

NOTE: Solutions capable of generating real-time captions or handling RTT could satisfy the above requirement.

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions.

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions.

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions as follows:

  • Captions in recorded material: within 100 ms of the time stamp of the caption
  • Live captions: within 100 ms of the availability of the caption to the player.
Functional change

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions as follows:

  • Captions in recorded material: within 100 ms of the time stamp of the caption.
  • Live captions: within 100 ms of the availability of the caption to the player.

7.1.4 Captions characteristics

Where ICT displays captions, it shall provide a way for the user to adapt the displayed characteristics of captions to their individual requirements, except where the captions are displayed as unmodifiable characters.

NOTE 1: Defining the background and foreground colour of subtitles, font type, size opacity of the background box of subtitles, and the contour or border of the fonts can contribute to meeting this requirement.

NOTE 2: Subtitles that are bitmap images are examples of unmodifiable characters.

New requirement

7.1.4 Captions characteristics

Where ICT displays captions, it shall provide a way for the user to adapt the displayed characteristics of captions to their individual requirements, except where the captions are displayed as unmodifiable characters.

NOTE 1: Defining the background and foreground colour of subtitles, font type, size opacity of the background box of subtitles, and the contour or border of the fonts can contribute to meeting this requirement.

NOTE 2: Subtitles that are bitmap images are examples of unmodifiable characters.

7.1.5 Spoken subtitles

Where ICT displays video with synchronized audio, it shall have a mode of operation to provide a spoken output of the available captions, except where the content of the displayed captions is not programmatically determinable.

NOTE 1: Being able to manage speech output range for spoken subtitles independently from general ICT speech is preferable for most users. That is possible when the audio file with spoken subtitle is delivered in a separate audio track and mixed in the end users device.

NOTE 2: Presenting the separate audio track with spoken subtitles in synchronization with the displayed subtitles/captions improves understandability of the subtitles.

NOTE 3: Providing subtitles/captions as separate text-streams, facilitates converting the respective texts into audio.

NOTE 4: Subtitles that are bitmap images are examples where the content of the displayed captions will not be programmatically determinable.

New requirement

7.1.5 Spoken subtitles

Where ICT displays video with synchronized audio, it shall have a mode of operation to provide a spoken output of the available captions, except where the content of the displayed captions is not programmatically determinable.

NOTE 1: Being able to manage speech output range for spoken subtitles independently from general ICT speech is preferable for most users. That is possible when the audio file with spoken subtitle is delivered in a separate audio track and mixed in the end users device. NOTE 2: Presenting the separate audio track with spoken subtitles in synchronization with the displayed subtitles/captions improves understandability of the subtitles.

NOTE 3: Providing subtitles/captions as separate text-streams, facilitates converting the respective texts into audio.

NOTE 4: Subtitles that are bitmap images are examples where the content of the displayed captions will not be programmatically determinable.

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.

NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.

NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.

NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.

NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.

NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.

NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.

NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.

NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

8.3.0 General

The present document defines the dimensions for accessing stationary ICT that can be placed in a built environment, but does not define the dimensions of the built environment in general.

The scope includes stationary ICT, of which floors and circulation spaces are "an integral part" (typically kiosks and cabins), and where there are external reach ranges relevant for operating the stationary ICT.

Clauses 8.3.2 to 8.3.4 specify mandatory limits for the maximum and minimum height of operable parts and displays.

Based on dimensions shown in figure 53 of ISO 21542:2011, it is recommended that the possible height range is reduced to:

  • minimum and maximum heights of operable parts: 800 mm and 1 100 mm respectively, and
  • minimum and maximum heights of displays: 1 200 mm and 1 400 mm respectively.
New requirement

8.3.0 General

The present document defines the dimensions for accessing stationary ICT that can be placed in a built environment, but does not define the dimensions of the built environment in general.

The scope includes stationary ICT, of which floors and circulation spaces are "an integral part" (typically kiosks and cabins), and where there are external reach ranges relevant for operating the stationary ICT.

Clauses 8.3.2 to 8.3.4 specify mandatory limits for the maximum and minimum height of operable parts and displays. Based on dimensions shown in Figure 53 of ISO 21542:2011, it is recommended that the possible height range is reduced to:

  • minimum and maximum heights of operable parts: 800 mm and 1 100 mm respectively, and
  • minimum and maximum heights of displays: 1 200 mm and 1 400 mm respectively.

8.3.2.1 Change in level

Where there is a change in floor level that is integral to the ICT then it should be ramped with a slope no steeper than 1:48.

Exceptions:

  1. If the change in floor level is less than or equal to 6,4 mm (¼ inch) the change may be vertical.
  2. If the change in floor level is less than or equal to 13 mm (½ inch) the change may have a slope not steeper than 1:2.

8.3.2.1 Change in level

Where there is a change in floor level that is integral to the ICT then it should be ramped with a slope no steeper than 1:48.

Exceptions:

  1. If the change in floor level is less than or equal to 6,4 mm (¼ inch) the change may be vertical.
  2. If the change in floor level is less than or equal to 13 mm (½ inch) the change may have a slope not steeper than 1:2.

8.3.4.1 Change in level

Where stationary ICT has a floor within it, then any change of floor level within it or entering it shall be ramped with a slope no steeper than 1:48.

Exceptions:

  1. If the change in floor level is less than or equal to 6,4 mm (¼ inch) the change may be vertical.
  2. If the change in floor level is less than or equal to 13 mm (½ inch) the change may have a slope not steeper than 1:2.

Numbering change

Stylistic rewording

Functional change

8.3.4.1 Change in level

Where stationary ICT has a floor within it, then any change of floor level within it or entering it shall be ramped with a

slope no steeper than 1:48.

Exceptions:

  1. If the change in floor level is less than or equal to 6,4 mm (¼ inch) the change may be vertical as shown in Figure 8.
  2. If the change in floor level is less than or equal to 13 mm (½ inch) the change may have a slope not steeper than 1:2.

8.3.2.3.1 General

Where the access space is integral to the ICT, at least one full side of the space should be unobstructed.

8.3.2.3.1 General

Where the access space is integral to the ICT, at least one full side of the space should be unobstructed.

8.3.4.3.1 General

Where stationary ICT has an access space inside it, at least one full side of the space shall be unobstructed.

Numbering change

Stylistic rewording

Functional change

8.3.4.3.1 General

Where stationary ICT has an access space inside it, at least one full side of the space shall be unobstructed.

8.3.2.3.2 Forward approach

Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space should be a minimum of 915 mm (36 inches) wide.

8.3.2.3.2 Forward approach

Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space should be a minimum of 915 mm (36 inches) wide.

8.3.4.3.2 Forward approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space shall be a minimum of 915 mm (36 inches) wide.

Numbering change

Stylistic rewording

Functional change

8.3.4.3.2 Forward approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space shall be a minimum of 915 mm (36 inches) wide.

8.3.2.3.3 Parallel approach

Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space should be a minimum of 1 525 mm (60 inches) wide.

8.3.2.3.3 Parallel approach

Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space should be a minimum of 1 525 mm (60 inches) wide.

8.3.4.3.3 Parallel approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space shall be a minimum of 1 525 mm (60 inches) wide.

Numbering change

Stylistic rewording

Functional change

8.3.4.3.3 Parallel approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space shall be a minimum of 1 525 mm (60 inches) wide.

8.3.5 Installation instructions

Where an ICT is intended to be installed, instructions should be made available which outline a method to install the ICT in a manner that ensures that the dimensions of the integral spaces of the ICT conform to clauses 8.3.2 to 8.3.4.

8.3.5 Installation instructions

Where an ICT is intended to be installed, instructions should be made available which outline a method to install the ICT in a manner that ensures that the dimensions of the integral spaces of the ICT conform to clauses 8.3.2 to 8.3.4.

8.3.6 Installation instructions

Installation instructions shall be made available for all stationary ICT. These instructions shall give guidance on how to install the ICT in a manner that takes into account applicable requirements for accessibility of the built environment as they apply to the installation of the ICT. Where there are no such requirements the instructions should require that the dimensions of the installed ICT conform to clauses 8.3.2 to 8.3.5 of the present document.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.6 Installation instructions

Installation instructions shall be made available for all stationary ICT. These instructions shall give guidance on how to install the ICT in a manner that takes into account applicable requirements for accessibility of the built environment as they apply to the installation of the ICT. Where there are no such requirements the instructions should require that the dimensions of the installed ICT conform to clauses 8.3.2 to 8.3.5 of the present document.

9.1.3.4 Orientation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.4 Orientation.

New requirement

9.1.3.4 Orientation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.4 Orientation.

9.1.3.4 Orientation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.4 Orientation.

9.1.3.5 Identify input purpose

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

New requirement

9.1.3.5 Identify input purpose

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

9.1.3.5 Identify input purpose

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

9.1.4.10 Reflow

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.10 Reflow.

New requirement

9.1.4.10 Reflow

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.10 Reflow.

9.1.4.10 Reflow

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.10 Reflow.

9.1.4.11 Non-text contrast

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

New requirement

9.1.4.11 Non-text contrast

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

9.1.4.11 Non-text contrast

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

9.1.4.12 Text spacing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

New requirement

9.1.4.12 Text spacing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

9.1.4.12 Text spacing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

9.1.4.13 Content on hover or focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

New requirement

9.1.4.13 Content on hover or focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

9.1.4.13 Content on hover or focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

9.2.1.4 Character key shortcuts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

New requirement

9.2.1.4 Character key shortcuts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

9.2.1.4 Character key shortcuts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

9.2.5.1 Pointer gestures

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

New requirement

9.2.5.1 Pointer gestures

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

9.2.5.1 Pointer gestures

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

9.2.5.2 Pointer cancellation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

New requirement

9.2.5.2 Pointer cancellation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

9.2.5.2 Pointer cancellation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

9.2.5.3 Label in name

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

New requirement

9.2.5.3 Label in name

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

9.2.5.3 Label in name

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

9.2.5.4 Motion actuation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

New requirement

9.2.5.4 Motion actuation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

9.2.5.4 Motion actuation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

9.4.1.3 Status messages

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

New requirement

9.4.1.3 Status messages

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

9.4.1.3 Status messages

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

9.5 WCAG 2.1 AAA Success Criteria

In addition to the Level AA success criteria, included in clauses 9.1 to 9.4, the Web Content Accessibility Guidelines include success criteria for Level AAA. These are listed in Table 9.1. Web authors and procurement accessibility specialists are encouraged to consider the WCAG 2.1 Level AAA success criteria that, when it is possible to apply them, may provide access beyond that required in the present document.

NOTE: The W3C states that "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content".

New requirement

9.5 WCAG 2.1 AAA Success Criteria

In addition to the Level AA success criteria, included in clauses 9.1 to 9.4, the Web Content Accessibility Guidelines include success criteria for Level AAA. These are listed in Table 9.1. Web authors and procurement accessibility specialists are encouraged to consider the WCAG 2.1 Level AAA success criteria that, when it is possible to apply them, may provide access beyond that required in the present document.

NOTE: The W3C states that "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content".

10.2.7 Info and relationships

Where ICT is a non-web document, it shall satisfy the success criterion.

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.1 Info and Relationships.

10.1.3.1 Info and relationships

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

Numbering change

10.1.3.1 Info and relationships

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

NOTE: Where documents contain non-standard structure types (roles), it is best practice to map them to a standard structure type as a fall-back solution for the reader.

Explanatory update

10.1.3.1 Info and relationships

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

NOTE: Where documents contain non-standard structure types (roles), it is best practice to map them to a standard structure type as a fall-back solution for the reader.

10.1.3.4 Orientation

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

New requirement

10.1.3.4 Orientation

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

10.1.3.4 Orientation

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

10.1.3.5 Identify input purpose

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

New requirement

10.1.3.5 Identify input purpose

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

10.1.3.5 Identify input purpose

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

10.1.4.10 Reflow

Where ICT is a non-web document, it shall satisfy the following success criterion.

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 1280 CSS pixels wide at 400% zoom. For documents which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024px 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.

New requirement

10.1.4.10 Reflow

Where ICT is a non-web document, it shall satisfy the following success criterion.

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 documents 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 pixels 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.

10.1.4.10 Reflow

Where ICT is a non-web document, it shall satisfy the success criterion 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 documents 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 pixels 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.

10.1.4.11 Non-text contrast

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

New requirement

10.1.4.11 Non-text contrast

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

10.1.4.11 Non-text contrast

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

10.1.4.12 Text spacing

Where ICT is a non-web document that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

New requirement

10.1.4.12 Text spacing

Where ICT is a non-web document that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

10.1.4.12 Text spacing

Where ICT is a non-web document that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

10.1.4.13 Content on hover or focus

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

New requirement

10.1.4.13 Content on hover or focus

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

10.1.4.13 Content on hover or focus

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

10.2.1.4 Character key shortcuts

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

New requirement

10.2.1.4 Character key shortcuts

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

10.2.1.4 Character key shortcuts

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

10.2.20 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

10.2.4.1 VoidNumbering change

10.2.4.1 Void

NOTE 1: The related web page requirement "Bypass blocks" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

NOTE 2: Although not a requirement, the ability to bypass blocks of content that are repeated within documents is generally considered best practice and addresses user needs.

Explanatory update

10.2.4.1 Void

NOTE 1: The related web page requirement "Bypass blocks" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

NOTE 2: Although not a requirement, the ability to bypass blocks of content that are repeated within documents is generally considered best practice and addresses user needs.

10.2.24 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

10.2.4.5 VoidNumbering change

10.2.4.5 Void

NOTE: The related web page requirement "Multiple ways" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

Explanatory update

10.2.4.5 Void

NOTE: The related web page requirement "Multiple ways" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

10.2.5.1 Pointer gestures

Where ICT is a non-web document, it shall satisfy the following success criterion.

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to documents that interpret pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

New requirement

10.2.5.1 Pointer gestures

Where ICT is a non-web document, it shall satisfy the following success criterion.

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to documents that interpret pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

10.2.5.1 Pointer gestures

Where ICT is a non-web document, it shall satisfy the success criterion All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to documents that interpret pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

10.2.5.2 Pointer cancellation

Where ICT is a non-web document, it shall satisfy the following success criterion.

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to a document that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

New requirement

10.2.5.2 Pointer cancellation

Where ICT is a non-web document, it shall satisfy the following success criterion.

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to a document that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

10.2.5.2 Pointer cancellation

Where ICT is a non-web document, it shall satisfy the success criterion. For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to a document that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

10.2.5.3 Label in name

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

New requirement

10.2.5.3 Label in name

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

10.2.5.3 Label in name

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

10.2.5.4 Motion actuation

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

New requirement

10.2.5.4 Motion actuation

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

10.2.5.4 Motion actuation

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

10.2.31 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

10.3.2.3 VoidNumbering change

10.3.2.3 Void

NOTE: The related web page requirement "Consistent navigation" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

Explanatory update

10.3.2.3 Void

NOTE: The related web page requirement "Consistent navigation" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

10.2.32 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

10.3.2.4 VoidNumbering change

10.3.2.4 Void

NOTE: The related web page requirement "Consistent identification" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

Explanatory update

10.3.2.4 Void

NOTE: The related web page requirement "Consistent identification" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

10.4.1.3 Void

10.4.1.3 Status messages

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

New requirement

10.4.1.3 Status messages

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

10.2.39 Caption positioning

Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.

10.5 Caption positioning

Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.

Numbering change

10.5 Caption positioning

Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.

10.5 Caption positioning

Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.

11.1.2.1.2.1 Pre-recorded audio-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the functionality of software that provides a user interface shall meet requirement 5.1.5 (Visual output for auditory information).

New requirement

11.1.2.1.2.1 Pre-recorded audio-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the functionality of software that provides a user interface shall meet requirement 5.1.5 (Visual output for auditory information).

11.1.2.1.2.1 Pre-recorded audio-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the functionality of software that provides a user interface shall meet requirement 5.1.5 (Visual output for auditory information).

11.1.2.1.2.2 Pre-recorded video-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

New requirement

11.1.2.1.2.2 Pre-recorded video-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

11.1.2.1.2.2 Pre-recorded video-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

11.2.1.6 Audio description (pre-recorded)

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion Audio description is provided for all pre-recorded video content in synchronized media.

NOTE 1: The WCAG 2.0 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.

NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.5 Audio Description (Pre-recorded) with the addition of note 1 above.

11.1.2.5 Audio description (pre-recorded)

Where ICT is non-web software that provides a user interface, 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.

Numbering change

11.1.2.5 Audio description (pre-recorded)

Where ICT is non-web software that provides a user interface, 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.

11.1.2.5 Audio description (pre-recorded)

Where ICT is non-web software that provides a user interface, 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.

11.1.2.3.1 Audio description or media alternative (pre-recorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, 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.

New requirement

11.1.2.3.1 Audio description or media alternative (pre-recorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, 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.

11.1.2.3.1 Audio description or media alternative (pre-recorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, 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.

11.1.2.3.2 Audio description or media alternative (pre-recorded - closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

New requirement

11.1.2.3.2 Audio description or media alternative (pre-recorded - closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

11.1.2.3.2 Audio description or media alternative (pre-recorded - closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

11.2.1.7 Info and relationships

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

NOTE 1: 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.3 Interoperability with assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.1 Info and Relationships with the addition of note 1 above.

11.1.3.1.1 Info and relationships (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships. 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).

New requirement

11.1.3.1.1 Info and relationships (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships. 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).

11.1.3.1.1 Info and relationships (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

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).

11.1.3.1.2 Info and relationships (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

New requirement

11.1.3.1.2 Info and relationships (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

11.1.3.1.2 Info and relationships (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

11.2.1.8 Meaningful sequence

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.2 Meaningful Sequence.

11.1.3.2.1 Meaningful sequence (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

Numbering change

11.1.3.2.1 Meaningful sequence (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

11.1.3.2.1 Meaningful sequence (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

11.1.3.2.2 Meaningful sequence (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

New requirement

11.1.3.2.2 Meaningful sequence (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

11.1.3.2.2 Meaningful sequence (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

11.1.3.4 Orientation

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

New requirement

11.1.3.4 Orientation

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

11.1.3.4 Orientation

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

11.1.3.5 Identify input purpose

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

New requirement

11.1.3.5.1 Identify input purpose (open functionality)

Where ICT is non-web software that provides a user interface and supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

Numbering change

Functional change

11.1.3.5.1 Identify input purpose (open functionality)

Where ICT is non-web software that provides a user interface and supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

11.1.3.5.2 Identify input purpose (closed functionality)

Where ICT is non-web software that provides a user interface and is closed to assistive technologies, in at least one mode of operation the ICT shall present to the user, in an audio form, the purpose of each input field collecting information about the user when the input field serves a purpose identified in the WCAG 2.1 Input Purposes for User Interface Components section

New requirement

11.1.3.5.2 Identify input purpose (closed functionality)

Where ICT is non-web software that provides a user interface and is closed to assistive technologies, in at least one mode of operation the ICT shall present to the user, in an audio form, the purpose of each input field collecting information about the user when the input field serves a purpose identified in the WCAG 2.1 Input Purposes for User Interface Components section.

11.2.1.13 Resize text

Where ICT is non-web software that provides a user interface and that supports access to enlargement features of platform or assistive technology, it shall satisfy the success criterion Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

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.

NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.4 Resize text with the addition of notes 1 and 2 above.

11.1.4.4.2 Resize text (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).

NOTE: Because the text rendering support in a closed environment may be more limited than the support found in user agents for the Web, meeting 11.1.4.4.2 in a closed environment may place a much heavier burden on the content author.

Numbering change

Functional change

11.1.4.4.2 Resize text (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).

NOTE: Because the text rendering support in a closed environment may be more limited than the support found in user agents for the Web, meeting the present clause in a closed environment may place a much heavier burden on the content author.

11.1.4.4.2 Resize text (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).

NOTE: Because the text rendering support in a closed environment may be more limited than the support found in user agents for the Web, meeting the present clause in a closed environment may place a much heavier burden on the content author.

11.2.1.14 Images of text

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion 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.

NOTE 1: Logotypes (text that is part of a logo or brand name) are considered essential.

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.5 Images of Text.

11.1.4.5.1 Images of text

(open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.

Numbering change

Functional change

Explanatory change

11.1.4.5.1 Images of text (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.

11.1.4.5.1 Images of text (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.

11.1.4.5.2 Images of text (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it does not need to meet the WCAG 2.1 Success Criterion 1.4.5 Images of Text because there is no need to impose a requirement on all closed functionality that text displayed on the screen actually be represented internally as text (as defined by WCAG 2.1), given that there is no interoperability with assistive technology.

New requirement

11.1.4.5.2 Images of text (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.6 (Speech output for non-text content).

Functional change

11.1.4.5.2 Images of text (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.6 (Speech output for non-text content).

11.1.4.10.1 Reflow (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the following success criterion.

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.

New requirement

11.1.4.10 Reflow

Where ICT is non-web software that provides a user interface it shall satisfy the following success criterion.

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.

Numbering change

Functional change

11.1.4.10 Reflow

Where ICT is non-web software that provides a user interface it shall satisfy the success criterion 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.

11.1.4.10.2 Reflow (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).

New requirementVoidVoid

11.1.4.11 Non-text contrast

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

New requirement

11.1.4.11 Non-text contrast

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

11.1.4.11 Non-text contrast

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

11.1.4.12 Text spacing

Where ICT is non-web software that provides a user interface and that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

New requirement

11.1.4.12 Text spacing

Where ICT is non-web software that provides a user interface and that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

11.1.4.12 Text spacing

Where ICT is non-web software that provides a user interface and that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

11.1.4.13 Content on hover or focus

Where ICT is a non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

New requirement

11.1.4.13 Content on hover or focus

Where ICT is a non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

11.1.4.13 Content on hover or focus

Where ICT is a non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

11.2.1.1.2 Keyboard (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

New requirement

11.2.1.1.2 Keyboard (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

11.2.1.1.2 Keyboard (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

11.2.1.4.1 Character key shortcuts (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

New requirement

11.2.1.4.1 Character key shortcuts (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

11.2.1.4.1 Character key shortcuts (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

11.2.1.4.2 Character key shortcuts (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

New requirement

11.2.1.4.2 Character key shortcuts (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

11.2.1.4.2 Character key shortcuts (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

11.2.1.20 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

11.2.4.1 Void

11.2.4.1 Void

NOTE 1: The related web page requirement "Bypass blocks" does not apply to single software programs, but to a specific definition of "sets of software programs" that are extremely rare.

NOTE 2: Although not a requirement, it is generally considered best practice, and to address user needs, to be able to bypass blocks of content that are repeated within software.

Stylistic update

11.2.4.1 Void

NOTE 1: The related web page requirement "Bypass blocks" does not apply to single software programs, but to a specific definition of "sets of software programs" that are extremely rare.

NOTE 2: Although not a requirement, it is generally considered best practice, and to address user needs, to be able to bypass blocks of content that are repeated within software.

11.2.1.21 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

11.2.4.2 Void

11.2.4.2 Void

NOTE 1: The related web page requirement "Page titled" does not apply to single software programs, but to a specific definition of "sets of software programs" that are extremely rare.

NOTE 2: Although the name of a software product could be a sufficient title if it describes the topic or purpose, software names are trademarked and trademark names cannot by law be descriptive names. It is not practical to make software names both unique and descriptive.

Stylistic update

11.2.4.2 Void

NOTE 1: The related web page requirement "Page titled" does not apply to single software programs, but to a specific definition of "sets of software programs" that are extremely rare.

NOTE 2: Although the name of a software product could be a sufficient title if it describes the topic or purpose, software names are trademarked and trademark names cannot by law be descriptive names. It is not practical to make software names both unique and descriptive.

11.3.1.1.2 Language of software (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.14 (Spoken languages).

New requirement

11.3.1.1.2 Language of software (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.14 (Spoken languages).

11.3.1.1.2 Language of software (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.14 (Spoken languages).

11.2.5.1 Pointer gestures

Where ICT is non-web software that provides a user interface, it shall satisfy the following success criterion.

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

New requirement

11.2.5.1 Pointer gestures

Where ICT is non-web software that provides a user interface, it shall satisfy the following success criterion.

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

11.2.5.1 Pointer gestures

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

11.2.5.2 Pointer cancellation

Where ICT is non-web software that provides a user interface, it shall satisfy the following success criterion.

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

New requirement

11.2.5.2 Pointer cancellation

Where ICT is non-web software that provides a user interface, it shall satisfy the following success criterion.

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

11.2.5.2 Pointer cancellation

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function.
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion.
  • Up Reversal: The up-event reverses any outcome of the preceding down-event.
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

11.2.5.3 Label in name

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

New requirement

11.2.5.3.1 Label in name (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

Numbering change

11.2.5.3.1 Label in name (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

11.2.5.3.2 Label in name (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it should meet requirement 5.1.3.3 (Auditory output correlation).

New requirement

11.2.5.3.2 Label in name (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it should meet requirement 5.1.3.3 (Auditory output correlation).

11.2.5.4 Motion actuation

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

New requirement

11.2.5.4 Motion actuation

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

11.2.5.4 Motion actuation

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

11.4.1.3.1 Status messages (open functionality)

Where ICT is non-web software, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

New requirement

11.4.1.3.1 Status messages (open functionality)

Where ICT is non-web software, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

11.4.1.3.2 Status messages (closed functionality)

Not applicable.

New requirement

11.4.1.3.2 Status messages (closed functionality)

Not applicable.

13.1.1 General (informative)

Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.

It is best practice to meet the applicable relay service requirements of ES 202 975.

13.1.1 General (informative)

Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.

It is best practice to meet the applicable relay service requirements of ETSI ES 202 975.

Explanatory update

13.1.1 General (informative)

Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.

It is best practice to meet the applicable relay service requirements of ETSI ES 202 975.

13.1.1 General (informative)

Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.

It is best practice to meet the applicable relay service requirements of ETSI ES 202 975 [i.5].

13.1.6 Speech to speech relay services

Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable speech or cognitively impaired telephone users and any other user to communicate by providing assistance between them.

13.1.6 Speech to speech relay services

Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable speech or cognitively impaired telephone users and any other user to communicate by providing assistance between them.

13.1.6 Speech to speech relay services

Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable telephone users who are speech impaired, have limited cognitive, language and learning abilities, as well as any other user, to communicate by providing assistance between them.

Stylistic rewording

Functional change

Explanatory update

13.1.6 Speech to speech relay services

Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable telephone users who are speech impaired, have limited cognitive, language and learning abilities, as well as any other user, to communicate by providing assistance between them.

13.2 Access to relay services

Where ICT systems support two-way communication and a set of relay services for such communication is specified, access to those relay services shall not be prevented for outgoing and incoming calls.

NOTE 1: Two-way communication may include voice, real-time text, or video, singly or in combinations supported by both the relay service and the ICT system.

NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access by persons with disabilities.

13.2 Access to relay services

Where ICT systems support two-way communication and a set of relay services for such communication is specified, access to those relay services shall not be prevented for outgoing and incoming calls.

NOTE 1: Two-way communication may include voice, real-time text, or video, singly or in combinations supported by both the relay service and the ICT system.

NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access by persons with disabilities.

13.2 Access to relay services

Where ICT systems support two-way communication, and the system is specified for use with relay services, access to those relay services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the relay service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access by persons with disabilities.

NOTE 2: The system may be specified as needing to work with relay services by, for example: procurers, regulators, or product specifications.

Explanatory update

Stylistic rewording

Functional change

13.2 Access to relay services

Where ICT systems support two-way communication, and the system is specified for use with relay services, access to those relay services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the relay service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access by persons with disabilities.

NOTE 2: The system may be specified as needing to work with relay services by, for example: procurers, regulators, or product specifications.

13.3 Access to emergency services

Where ICT systems support two-way communication and a set of emergency services for such communication is specified, access to those emergency services shall not be prevented for outgoing and incoming calls.

NOTE 1: Two–way communication may include voice, real-time text, or video, singly or in combinations supported by both the emergency service and the ICT system.

NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access to the emergency service by persons with disabilities.

13.3 Access to emergency services

Where ICT systems support two-way communication and a set of emergency services for such communication is specified, access to those emergency services shall not be prevented for outgoing and incoming calls.

NOTE 1: Two-way communication may include voice, real-time text, or video, singly or in combinations supported by both the emergency service and the ICT system.

NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access to the emergency service by persons with disabilities.

13.3 Access to emergency services

Where ICT systems support two-way communication, and the system is specified for use with emergency services, access to those emergency services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the emergency service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access to the emergency service by persons with disabilities.

NOTE 2: The system may be specified as needing to work with emergency services by, for example: procurers, regulators, or product specifications.

Explanatory update

Stylistic rewording

Functional change

13.3 Access to emergency services

Where ICT systems support two-way communication, and the system is specified for use with emergency services, access to those emergency services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the emergency service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access to the emergency service by persons with disabilities.

NOTE 2: The system may be specified as needing to work with emergency services by, for example: procurers, regulators, or product specifications.

List tables

End notes

  1. The functional performance criteria 302.7 and 302.8 of Section 508 and functional performance statements 4.2.7 and 4.2.8 of EN 301 549 inclusively cover the same requirements, despite being grouped slightly differently in each standard. Return to reference 1
  2. The functional performance criteria 302.7 and 302.8 of Section 508 and functional performance statements 4.2.7 and 4.2.8 of EN 301 549 inclusively cover the same requirements, despite being grouped slightly differently in each standard. Return to reference 2
  3. Section 508 specifies that the non-visual mode of operation must be speech output. Return to reference 3
  4. Section 508 specifies that the non-visual mode of operation must be speech output; EN 301 549 has a specific exception for “masked entry.” Return to reference 4
  5. EN 301 549 refers to specific standards for magnetic coupling. Return to reference 5
  6. EN 301 549 refers to specific standards for magnetic coupling. Return to reference 6
  7. Different approaches to calculating minimum text size. Section 508 assumes fixed distance between screen and eyes. EN 301 549 accounts for screens that are both far and near the eyes. Return to reference 7
  8. ICC A117.1-2009 section 703.7 contains some additional font type and line spacing requirements. Return to reference 8
  9. EN 301 549 has more specific privacy requirements. Return to reference 9
  10. EN 301 549 has more specific privacy requirements. Return to reference 10
  11. Section 508 refers to a specific keyboard implementation which may not be relevant for all languages. Return to reference 11
  12. Section 508 has additional requirements related to alphabetic overlay on numeric keys. Return to reference 12
  13. Some differences in approach to knee and toe clearance. Return to reference 13
  14. Some differences in approach to knee and toe clearance. Return to reference 14
  15. Some differences in approach to knee and toe clearance. Return to reference 15
  16. The EN 301 549 (2019, 2021) contains an error. “Where an obstacle is an integral part of the stationary ICT, the space under the obstacle that is between 230 mm (9 inches) and 685 mm (25 inches) above the floor is considered knee clearance and shall…” The 685 mm should have been converted to 26.969 inches. This document represents the EN standard’s original error. Return to reference 16
  17. Section 508 refers to 47 CFR 68.317 (a US regulation) whereas EN 301 549 refers to the specific level of volume gain required. Return to reference 17
  18. EN 301 549 has more specific requirements related to volume gain. Return to reference 18
  19. Each refer to relevant local standards. Return to reference 19
  20. Each refer to relevant local standards. Return to reference 20
  21. The EN 301 549 requirements are informative and refer to an upper frequency limit rather than the ITU standard. Return to reference 21
  22. EN 301 549 provides RTT requirements, discussed below. Return to reference 22
  23. EN 301 549 specifies “text form and at least one other modality” whereas Section 508 specifies “visible and audible.” Return to reference 23
  24. EN 301 549 contains more specific requirements. Return to reference 24
  25. EN 301 549 contains more specific requirements. Return to reference 25
  26. EN 301 549 contains more specific requirements. Return to reference 26
  27. EN 301 549 contains more specific requirements. Return to reference 27
  28. Section 508 refers to specific local standards related to Digital Television Tuners. Return to reference 28
  29. Section 508 focuses on operable parts whereas EN 301 549 focuses on the level of interaction. Return to reference 29
  30. Section 508 focuses on operable parts whereas EN 301 549 focuses on the level of interaction. Return to reference 30
  31. Section 508 specifically mentions keystrokes; whereas EN 301 549 is broader in scope and must include keystrokes. Return to reference 31
  32. Section 508 requires that timing be adjustable up to 2 seconds, whereas EN 301 549 requires time adjustable up to 0.5 seconds. Return to reference 32
  33. EN 301 549 treats timed response as a software issue. See EN 301 549 (2014) 11.2.1.17 (Timing Adjustable) and EN 301 549 (2018, 2019, 2021) 9.2.2.1 (Timing Adjustable). These clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 33
  34. EN 301 549 V1.1.1 (2014) and V2.1.2 (2018) provisions in the 407.8 series are recommendations (“should” versus “shall”). However, EN 301 549 V3.1.1 (2019) and EN 301 549 V3.2.1 (2021) provisions are requirements (“shall” versus “should”). Return to reference 34
  35. All versions of the EN 301 549 treats issues related to flashing and photosensitivity as a functional performance criteria (see 4.2.9) and a software criteria (see 11.2.1.19 (2014) and 9.2.3.1 for 2018, 2019, 2021) These clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 35
  36. EN 301 549 treats issues related to conveying information via multiple modalities as software issues (see 11.2.1.19 (2014) and 9.2.3.1 for 2018, 2019, 2021) These clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 36
  37. No corresponding provision in EN 301 549. Some aspects addressed in EN 301 549 (2014, 2018, 2019, 2021) sections 5.1.5, 7.1.1, 7.1.2, 7.3, 11.2.1.2, 11.2.1.3 and 11.2.1.5.The clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 37
  38. No corresponding provision in EN 301 549 (2014). Some aspects addressed in EN 301 549 (2014, 2018, 2019, 2021) sections 5.1.3, 7.2.2 and 11.3. The clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 38
  39. No corresponding provision in EN 301 549. Interoperability with assistive technology addressed in EN 301 549 (2014) 11.3. and 11.5.2.1 (2018, 2019, 2021) These clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 39
  40. No corresponding provision in EN 301 549 (2014), but 11.6.3 and 11.8.3 (2018, 2019, 2021) covers the same requirement without specifying PDF. Return to reference 40

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Mapping between Revised Section 508 and EN 301 549 (2014, 2018, 2019 and 2021)

As the EN 301 549 standards continue to evolve and release updates, this document shows the progression of the EN 301 549 standard from 2014 through the proceeding updates of 2018, 2019 and 2021. This information is important as the Government of Canada (GC) is moving towards adopting the EN 301 549 (2021) as its accessibility standard for ICT. The GC, as part of the solicitation process, may ask suppliers to provide accessibility conformance reports based on the Voluntary Product Accessibility Template (VPAT®). Each VPAT® is based on a specific technical standard – Revised Section 508, EN 301 549, or Web Content Accessibility Guidelines (WCAG). Suppliers, technical authorities and contracting authorities need to understand the differences between these standards to ensure that the accessibility requirements are properly addressed.

On this page

This document reproduces relevant ICT accessibility requirements from the EN 301 549 Harmonised European Standard "Accessibility requirements for ICT products and services" (© used under license from European Telecommunications Standards Institute 2014, 2018, 2019 and 2021. © Comité Européen de Normalisation 2014, 2018, 2019, 2021. © Comité Européen de Normalisation Électrotechnique 2014, 2018, 2019 and 2021. All rights reserved.)

Caveat

This document was created by the Shared Services Canada (SSC) Accessibility, Accommodations and Adaptive Computer Technology (AAACT) program in February 2020 and updated in October 2022. To the best of our knowledge, this document was accurate as of October 2022. SSC does not warrant any jurisdiction’s reliance on this work. If you have any questions about this document, please email the AAACT program.

Intended Audience

The intended audience is Technical and Contracting Authorities within SSC and the Government of Canada (GC), as well as Suppliers who are delivering Information and Communications Technology (ICT) products and services.

Background

This document deals with technical standards for ICT accessibility. The most common standards are the Web Content Accessibility Guidelines (WCAG), Revised Section 508 and EN 301 549 Harmonized European Standard for ICT Accessibility.

The Revised Section 508 (2017) provides the technical standard for the US government to procure accessible products and services. This standard is, by design, closely harmonized with the EN 301 549 (2014) – which drew its requirements largely from the original Section 508 standards and WCAG 2.0. Consequently, these standards are very similar but do contain key differences. The EN 301 549 has been updated four times since the release of the Revised Section 508, introducing further differences between the standards.

Purpose

The purpose of this document is to identify the similarities and differences between Revised Section 508 and the EN 301 549 standards.

As the EN 301 549 standards continue to evolve and release updates, this document shows the progression of the EN 301 549 standards from 2014 through the proceeding updates of 2018, 2019 and 2021. This information is important as the GC is moving towards adopting the EN 301 549 (2021) as its accessibility standard for ICT. The GC, as part of the solicitation process, may ask suppliers to provide accessibility conformance reports based on the Voluntary Product Accessibility Template (VPAT). Each VPAT is based on a specific technical standard – Revised Section 508, EN 301 549, or WCAG. Suppliers, technical authorities and contracting authorities need to understand the differences between these standards to ensure that the accessibility requirements are properly addressed.

Summary of differences

WCAG to Revised Section 508 / EN 301 549

WCAG, while technology-agnostic, is typically applicable to websites and web applications. For these products, specifying WCAG 2.0 level AA or 2.1 level AA as a technical standard may be sufficient. However, the other standards include additional requirements which may apply to web applications that provide any of the following features: documented accessibility features, authoring tools, two-way communication, video and conversion of information between electronic formats. The other standards also include requirements for support and documentation, which may apply to website or web application procurements.

Through the WCAG2ICT Task Force, the requirements of WCAG have been adapted to more precisely address the requirements for other kinds of ICT including non-web software and non-web documents. These adaptations have been integrated into Revised Section 508 and EN 301 549, so specifying those standards will result in clearer accessibility requirements for non-web ICT products than specifying WCAG would.

While Revised Section 508 and EN 301 549 include WCAG leveled requirements, these standards have a broader scope. For hardware ICT and ICT services, WCAG will not properly address accessibility requirements. If the functionality of the product or service may not be fully addressed by WCAG, GC procurements should specify the EN 301 549 standard.

Revised Section 508 to EN 301 549 (2014)

These standards are closely harmonized. Some requirements vary in specificity, with the EN 301 549 usually taking a more general approach. Revised Section 508 requirements may refer to specific US standards, while the EN 301 549 either includes the relevant specifications within the document or refers to international standards. Some general requirements of Revised Section 508 are only addressed in the Software chapter of the EN 301 549, so the Software requirements may need to be included even for hardware devices which have displays.

EN 301 549 (2014) to EN 301 549 (2018)

Primarily, WCAG-related chapters (9, 10 and 11) differ between these versions, along with several explanatory updates, stylistic rewordings, numbering changes, and functional changes. The 2014 version includes all WCAG 2.0 level A and AA success criteria, while the 2018 version is updated to directly reference all WCAG 2.1 level A and AA success criteria. (Although the 2018 and 2019 versions do not duplicate WCAG text, we have included the new requirements with the text in this document for clarity.) The numbering in WCAG-related chapters in the 2018 version directly follows WCAG 2.1 success criteria. For example, clause 9.2.3.1 of the EN 301 549 refers to WCAG success criterion 2.3.1.

EN 301 549 (2018) to EN 301 549 (2019)

The majority of changes are stylistic rewordings and additional explanatory notes. There are 14 new requirements, primarily relating to use with limited hearing. A few requirements from the 2018 version have been split up or consolidated. Requirements relating to physical access to ICT have been reworked into “8.3 Stationary ICT”. Numbering is otherwise consistent between versions.

EN 301 549 (2019) to EN 301 549 (2021)

The EN 301 549 V3.2.1 (2021) document was developed from EN 301 549 V2.1.2 (2018). There are no new requirements. The Annex F track changes table, has been added for future releases. Some clarification in 7.1.1 concerning captioning but numbering is otherwise consistent between versions. The numbering in WCAG-related chapters 9, 10 and 11 in the 2021 version directly follows WCAG 2.1 success criteria. For example, clause 9.2.3.1 of the EN 301 549 (2021) refers to WCAG success criterion 2.3.1. As stated in the footnotes, there are items that point to clauses that are not included in this document. They are only included if it is a new requirement and it points only to the WCAG guidelines.

Sources

Comparison Tables

Glossary

Stylistic rewording:
the text of the criterion modifies what is said, but does not modify what the criterion asks for, nor does it add new content or stipulations to the existing criterion
Functional change:
the text of the criterion significantly changes what the criterion is asking for, for example: the word “should” (denoting a recommendation) is replaced by the word “shall” (denoting a requirement)
Explanatory update:
the text has content or stipulations that clarify the purpose of the criterion without changing its purpose outright, such as specifying the source of a document
Numbering change:
the numbering is the criterion is updated due to either integration of WCAG numbering into the document, or changing the order in which they appear in the document for better flow and understanding
New requirement:
a criterion that does not exist in a previous version of the EN 301 549 document. Several new criteria were added in the 2019 version that do not appear in either the 2014 or 2018 version

Changes between versions of EN 301 549 are emphasized:

  1. For changes in hyperlinks the changes are reflected in bold, using the strong blue under style
  2. For changes in text the changes are reflected in bold, using the strong style
  3. For changes in the clause title the changes are reflected in bold, using the strong blue style
Select to see changes

List tables

List of tables

Chapter 2: Scoping Requirements

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

E207.2 WCAG Conformance

User interface components and content of platforms and applications shall conform to Level A and Level AA Success Criteria and Conformance Requirements specified for web pages in WCAG 2.0.

EXCEPTIONS:

  1. Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to E207.2.
  2. Non-Web software shall not be required to conform to the following four Success Criteria in WCAG 2.0: 2.4.1 Bypass Blocks; 2.4.5 Multiple Ways; 3.2.3 Consistent Navigation; and 3.2.4 Consistent Identification.
  3. Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in WCAG 2.0.

Chapters 9, 10, and 11 apply WCAG 2.0 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).

EN 301 549 Video Series

Stylistic rewordingChapters 9, 10, 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).Functional changeChapters 9, 10, 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).Chapters 9, 10, 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).

Chapter 3: Functional Performance Statements

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
302.1 Without vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

4.2.1 Usage without vision

Where ICT provides visual modes of operation, some users need ICT to provide at least one mode of operation that does not require vision.

NOTE: Audio and tactile user interfaces may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.1 Usage without vision

Where ICT provides visual modes of operation, some users need ICT to provide at least one mode of operation that does not require vision.

NOTE 1: A web page or application with a well formed semantic structure can allow users without vision to identify, navigate and interact with a visual user interface.

NOTE 2: Audio and tactile user interfaces may contribute towards meeting this clause.

Explanatory update

4.2.1 Usage without vision

Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that does not require vision. This is essential for users without vision and benefits many more users in different situations.

NOTE 1: A web page or application with a well formed semantic structure can allow users without vision to identify, navigate and interact with a visual user interface.

NOTE 2: Audio and tactile user interfaces may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.1 Usage without vision

Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that does not require vision. This is essential for users without vision and benefits many more users in different situations.

NOTE 1: A web page or application with a well formed semantic structure can allow users without vision to identify, navigate and interact with a visual user interface.

NOTE 2: Audio and tactile user interfaces may contribute towards meeting this clause.

302.2 With limited vision Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

4.2.2 Usage with limited vision

Where ICT provides visual modes of operation, some users will need the ICT to provide features that enable users to make better use of their limited vision.

NOTE 1: Magnification, reduction of required field of vision and control of contrast, brightness and intensity can contribute towards meeting this clause.

NOTE 2: Where significant features of the user interface are dependent on depth perception, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

NOTE 3: Users with limited vision may also benefit from non-visual access (see clause 4.2.1).

Stylistic rewording

Explanatory update

4.2.2 Usage with limited vision

Where ICT provides visual modes of operation, some users will need the ICT to provide features that enable users to make better use of their limited vision.

NOTE 1: Magnification, reduction of required field of vision and control of contrast, brightness and intensity can contribute towards meeting this clause.

NOTE 2: Where significant features of the user interface are dependent on depth perception, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

NOTE 3: Users with limited vision may also benefit from non-visual access (see clause 4.2.1).

4.2.2 Usage with limited vision

Where ICT provides visual modes of operation, the ICT provides features that enable users to make better use of their limited vision. This is essential for users with limited vision and benefits many more users in different situations.

NOTE 1: Magnification, reduction of required field of vision and control of contrast, brightness and intensity can contribute towards meeting this clause.

NOTE 2: Where significant features of the user interface are dependent on depth perception, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

NOTE 3: Users with limited vision may also benefit from non-visual access (see clause 4.2.1).

Stylistic rewording

Explanatory update

4.2.2 Usage with limited vision

Where ICT provides visual modes of operation, the ICT provides features that enable users to make better use of their limited vision. This is essential for users with limited vision and benefits many more users in different situations.

NOTE 1: Magnification, reduction of required field of vision and control of contrast, brightness and intensity can contribute towards meeting this clause.

NOTE 2: Where significant features of the user interface are dependent on depth perception, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

NOTE 3: Users with limited vision may also benefit from non-visual access (see clause 4.2.1).

302.3 Without Perception of Color

Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

4.2.3 Usage without perception of colour

Where ICT provides visual modes of operation, some users will need the ICT to provide a visual mode of operation that does not require user perception of colour.

NOTE: Where significant features of the user interface are colour-coded, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.3 Usage without perception of colour

Where ICT provides visual modes of operation, some users will need the ICT to provide a visual mode of operation that does not require user perception of colour.

NOTE: Where significant features of the user interface are colour-coded, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

4.2.3 Usage without perception of colour

Where ICT provides visual modes of operation, the ICT provides a visual mode of operation that does not require user perception of colour. This is essential for users with limited colour perception and benefits many more users in different situations.

NOTE: Where significant features of the user interface are colour-coded, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.3 Usage without perception of colour

Where ICT provides visual modes of operation, the ICT provides a visual mode of operation that does not require user perception of colour. This is essential for users with limited colour perception and benefits many more users in different situations.

NOTE: Where significant features of the user interface are colour-coded, the provision of additional methods of distinguishing between the features may contribute towards meeting this clause.

302.4 Without Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

4.2.4 Usage without hearing

Where ICT provides auditory modes of operation, some users need ICT to provide at least one mode of operation that does not require hearing.

NOTE: Visual and tactile user interfaces may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.4 Usage without hearing

Where ICT provides auditory modes of operation, some users need ICT to provide at least one mode of operation that does not require hearing.

NOTE: Visual and tactile user interfaces may contribute towards meeting this clause.

4.2.4 Usage without hearing

Where ICT provides auditory modes of operation, the ICT provides at least one mode of operation that does not require hearing. This is essential for users without hearing and benefits many more users in different situations.

NOTE: Visual and tactile user interfaces, including those based on sign language, may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.4 Usage without hearing

Where ICT provides auditory modes of operation, the ICT provides at least one mode of operation that does not require hearing. This is essential for users without hearing and benefits many more users in different situations.

NOTE: Visual and tactile user interfaces, including those based on sign language, may contribute towards meeting this clause.

302.5 With Limited Hearing

Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

4.2.5 Usage with limited hearing

Where ICT provides auditory modes of operation, some users will need the ICT to provide enhanced audio features.

NOTE 1: Enhancement of the audio clarity, reduction of background noise, increased range of volume and greater volume in the higher frequency range can contribute towards meeting this clause.

NOTE 2: Users with limited hearing may also benefit from non-hearing access (see clause 4.2.4).

Stylistic rewording

Explanatory update

4.2.5 Usage with limited hearing

Where ICT provides auditory modes of operation, some users will need the ICT to provide enhanced audio features.

NOTE 1: Enhancement of the audio clarity, reduction of background noise, increased range of volume and greater volume in the higher frequency range can contribute towards meeting this clause.

NOTE 2: Users with limited hearing may also benefit from non-hearing access (see clause 4.2.4).

4.2.5 Usage with limited hearing

Where ICT provides auditory modes of operation, the ICT provides enhanced audio features. This is essential for users with limited hearing and benefits many more users in different situations.

NOTE 1: Enhancement of the audio clarity, reduction of background noise, providing a joint monaural option, adjustment of balance of both audio channels, increased range of volume and greater volume in the higher frequency range can contribute towards meeting this clause.

NOTE 2: Allowing the use of Assistive Listening Devices, such as headsets with noise cancellation (connected by cable, Bluetooth or WLAN) can contribute towards meeting this clause.

NOTE 3: Users with limited hearing may also benefit from non-hearing access (see clause 4.2.4).

Stylistic rewording

Explanatory update

Functional change

4.2.5 Usage with limited hearing

Where ICT provides auditory modes of operation, the ICT provides enhanced audio features. This is essential for users with limited hearing and benefits many more users in different situations.

NOTE 1: Enhancement of the audio clarity, reduction of background noise, providing a joint monaural option, adjustment of balance of both audio channels, increased range of volume and greater volume in the higher frequency range can contribute towards meeting this clause.

NOTE 2: Allowing the use of Assistive Listening Devices, such as headsets with noise cancellation (connected by cable, Bluetooth or WLAN) can contribute towards meeting this clause.

NOTE 3: Users with limited hearing may also benefit from non-hearing access (see clause 4.2.4).

302.6 Without Speech Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

4.2.6 Usage without vocal capability

Where ICT requires vocal input from users, some users will need the ICT to provide at least one mode of operation that does not require them to generate vocal output.

NOTE 1: This clause covers the alternatives to the use of orally-generated sounds, including speech, whistles, clicks, etc.

NOTE 2: Keyboard, pen or touch user interfaces may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.6 Usage without vocal capability

Where ICT requires vocal input from users, some users will need the ICT to provide at least one mode of operation that does not require them to generate vocal output.

NOTE 1: This clause covers the alternatives to the use of orally-generated sounds, including speech, whistles, clicks, etc.

NOTE 2: Keyboard, pen or touch user interfaces may contribute towards meeting this clause.

4.2.6 Usage with no or limited vocal capability

Where ICT requires vocal input from users, the ICT provides at least one mode of operation that does not require them to generate vocal output. This is essential users with no or limited vocal capability and benefits many more users in different situations.

NOTE 1: Vocal output includes speech and other orally generated sounds, such as whistles and clicks.

NOTE 2: Keyboard, pen or touch user interfaces may contribute towards meeting this clause.

Functional change

Stylistic rewording

Explanatory update

4.2.6 Usage with no or limited vocal capability

Where ICT requires vocal input from users, the ICT provides at least one mode of operation that does not require them to generate vocal output. This is essential users with no or limited vocal capability and benefits many more users in different situations.

NOTE 1: Vocal output includes speech and other orally generated sounds, such as whistles and clicks.

NOTE 2: Keyboard, pen or touch user interfaces may contribute towards meeting this clause.

302.7 With Limited Manipulation

Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.1

4.2.7 Usage with limited manipulation or strength

Where ICT requires manual actions, some users will need the ICT to provide features that enable users to make use of the ICT through alternative actions not requiring manipulation or hand strength.

NOTE 1: Examples of operations that users may not be able to perform include those that require fine motor control, path dependant gestures, pinching, twisting of the wrist, tight grasping, or simultaneous manual actions.

NOTE 2: One-handed operation, sequential key entry and speech user interfaces may contribute towards meeting this clause.

NOTE 3: Some users have limited hand strength and may not be able to achieve the level of strength to perform an operation. Alternative user interface solutions that do not require hand strength may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.7 Usage with limited manipulation or strength

Where ICT requires manual actions, some users will need the ICT to provide features that enable users to make use of the ICT through alternative actions not requiring manipulation or hand strength.

NOTE 1: Examples of operations that users may not be able to perform include those that require fine motor control, path dependant gestures, pinching, twisting of the wrist, tight grasping, or simultaneous manual actions.

NOTE 2: One-handed operation, sequential key entry and speech user interfaces may contribute towards meeting this clause.

NOTE 3: Some users have limited hand strength and may not be able to achieve the level of strength to perform an operation. Alternative user interface solutions that do not require hand strength may contribute towards meeting this clause.

4.2.7 Usage with limited manipulation or strength

Where ICT requires manual actions, the ICT provides features that enable users to make use of the ICT through alternative actions not requiring manipulation, simultaneous action or hand strength. This is essential for users with limited manipulation or strength and benefits many more users in different situations.

NOTE 1: Examples of operations that users may not be able to perform include those that require fine motor control, path dependant gestures, pinching, twisting of the wrist, tight grasping, or simultaneous manual actions.

NOTE 2: One-handed operation, sequential key entry and speech user interfaces may contribute towards meeting this clause.

NOTE 3: Some users have limited hand strength and may not be able to achieve the level of strength to perform an operation. Alternative user interface solutions that do not require hand strength may contribute towards meeting this clause.

Stylistic rewording

Functional change

Explanatory update

4.2.7 Usage with limited manipulation or strength

Where ICT requires manual actions, the ICT provides features that enable users to make use of the ICT through alternative actions not requiring manipulation, simultaneous action or hand strength. This is essential for users with limited manipulation or strength and benefits many more users in different situations.

NOTE 1: Examples of operations that users may not be able to perform include those that require fine motor control, path dependant gestures, pinching, twisting of the wrist, tight grasping, or simultaneous manual actions.

NOTE 2: One-handed operation, sequential key entry and speech user interfaces may contribute towards meeting this clause.

NOTE 3: Some users have limited hand strength and may not be able to achieve the level of strength to perform an operation. Alternative user interface solutions that do not require hand strength may contribute towards meeting this clause.

302.8 With Limited Reach and Strength

Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.2

4.2.8 Usage with limited reach

Where ICT products are free-standing or installed, the operational elements will need to be within reach of all users.

NOTE: Considering the needs of wheelchair users and the range of user statures in the placing of operational elements of the user interface may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.8 Usage with limited reach

Where ICT products are free-standing or installed, the operational elements will need to be within reach of all users.

NOTE: Considering the needs of wheelchair users and the range of user statures in the placing of operational elements of the user interface may contribute towards meeting this clause.

4.2.8 Usage with limited reach

Where ICT products are free-standing or installed, all the elements required for operation will need to be within reach of all users. This is essential for users with limited reach and benefits many more users in different situations.

NOTE: Considering the needs of wheelchair users and the range of user statures in the placing of operational elements of the user interface may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.8 Usage with limited reach

Where ICT products are free-standing or installed, all the elements required for operation will need to be within reach of all users. This is essential for users with limited reach and benefits many more users in different situations.

NOTE: Considering the needs of wheelchair users and the range of user statures in the placing of operational elements of the user interface may contribute towards meeting this clause.

302.9 With Limited Language, Cognitive, and Learning Abilities

ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

4.2.10 Usage with limited cognition

Some users will need the ICT to provide features that make it simpler and easier to use.

NOTE 1: This clause is intended to include the needs of persons with limited cognitive, language and learning abilities.

NOTE 2: Adjustable timings, error indication and suggestion, and a logical focus order are examples of design features that may contribute towards meeting this clause.

Stylistic rewording

Explanatory update

4.2.10 Usage with limited cognition

Some users will need the ICT to provide features that make it simpler and easier to use.

NOTE 1: This clause is intended to include the needs of persons with limited cognitive, language and learning abilities.

NOTE 2: Adjustable timings, error indication and suggestion, and a logical focus order are examples of design features that may contribute towards meeting this clause.

4.2.10 Usage with limited cognition, language or learning

The ICT provides features and/or presentation that makes it simpler and easier to understand, operate and use. This is essential for users with limited cognition, language or learning, and benefits many more users in different situations.

NOTE 1: Adjustable timings, error indication and suggestion, and a logical focus order are examples of design features that may contribute towards meeting this clause.

NOTE 2: Providing an audio output of the text is an example of providing support for people with limited reading abilities.

NOTE 3: Providing spelling aid and word prediction of the text is an example of providing support for people with limited writing abilities.

NOTE 4: Interaction with content can be made easier, and less prone to errors, by presenting tasks in steps that are easy to follow.

Functional change

Stylistic rewording

Explanatory update

4.2.10 Usage with limited cognition, language or learning

The ICT provides features and/or presentation that makes it simpler and easier to understand, operate and use. This is essential for users with limited cognition, language or learning, and benefits many more users in different situations.

NOTE 1: Adjustable timings, error indication and suggestion, and a logical focus order are examples of design features that may contribute towards meeting this clause.

NOTE 2: Providing an audio output of the text is an example of providing support for people with limited reading abilities.

NOTE 3: Providing spelling aid and word prediction of the text is an example of providing support for people with limited writing abilities.

NOTE 4: Interaction with content can be made easier, and less prone to errors, by presenting tasks in steps that are easy to follow.

List tables

Chapter 4: Hardware

402 Closed Functionality

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

402.1 General

ICT with closed functionality shall be operable without requiring the user to attach or install assistive technology other than personal headsets or other audio couplers, and shall conform to 402.

5.1.2.2 Assistive technology

Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.7 as applicable. Personal headsets and induction loops shall not be classed as assistive technology for the purpose of this clause.

Stylistic rewording

Explanatory update

5.1.2.2 Assistive technology Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.6 as applicable. Personal headsets and induction loops shall not be classed as assistive technology for the purpose of this clause.Explanatory update

5.1.2.2 Assistive technology

Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.6 as applicable. Personal headsets and personal induction loops shall not be classed as assistive technology for the purpose of this clause.

Stylistic rewording

5.1.2.2 Assistive technology

Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.6 as applicable. Personal headsets and personal induction loops shall not be classed as assistive technology for the purpose of this clause.

402.2 Speech-Output Enabled

ICT with a display screen shall be speech-output enabled for full and independent use by individuals with vision impairments.3

EXCEPTIONS:

  1. Variable message signs conforming to 402.5 shall not be required to be speech-output enabled.
  2. Speech output shall not be required where ICT display screens only provide status indicators and those indicators conform to 409.
  3. Where speech output cannot be supported due to constraints in available memory or processor capability, ICT shall be permitted to conform to 409 in lieu of 402.2.
  4. Audible tones shall be permitted instead of speech output where the content of user input is not displayed as entered for security purposes, including, but not limited to, asterisks representing personal identification numbers.
  5. Speech output shall not be required for: the machine location; date and time of transaction; customer account number; and the machine identifier or label.
  6. Speech output shall not be required for advertisements and other similar information unless they convey information that can be used for the transaction being conducted.

5.1.3.1 General

Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.

NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form.

NOTE 2: The visual information needed to enable use of some functions may include operating instructions and orientation, transaction prompts, user input verification, error messages and non-text content.

Stylistic rewording

Explanatory update

5.1.3.1 General

Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.

NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form.

NOTE 2: The visual information needed to enable use of some functions may include operating instructions and orientation, transaction prompts, user input verification, error messages and non-text content.

5.1.3.1 Audio output of visual information

Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.

NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form such as braille for deaf-blind users.

NOTE 2: The visual information needed to enable use of some functions may include operating instructions and orientation, transaction prompts, user input verification, error messages and non-text content.

Explanatory update

5.1.3.1 Audio output of visual information

Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.

NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form such as braille for deaf-blind users.

NOTE 2: The visual information needed to enable use of some functions may include operating instructions and orientation, transaction prompts, user input verification, error messages and non-text content.

402.2.1 Information Displayed On-Screen

Speech output shall be provided for all information displayed on-screen.

5.1.3.6 Speech output for non-text content

Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in WCAG 2.0 Success Criterion 1.1.1.

Stylistic rewording

Explanatory update

5.1.3.6 Speech output for non-text content

Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1.

Functional change

5.1.3.6 Speech output for non-text content

Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in WCAG 2.1 Success Criterion 1.1.1.

5.1.3.6 Speech output for non-text content

Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in WCAG 2.1 [5] Success Criterion 1.1.1.

402.2.1 Information Displayed On-Screen Speech output shall be provided for all information displayed on-screen.

5.1.3.7 Speech output for video information

Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content.

NOTE: This speech output can take the form of an audio description or an auditory transcript of the video content.

Stylistic rewording

Explanatory update

5.1.3.7 Speech output for video information

Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content.

NOTE: This speech output can take the form of an audio description or an auditory transcript of the video content.

5.1.3.7 Speech output for video information

Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content.

NOTE: This speech output can take the form of an audio description or an auditory transcript of the video content.

5.1.3.7 Speech output for video information

Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content. NOTE: This speech output can take the form of an audio description or an auditory transcript of the video content.

402.2.1 Information Displayed On-Screen

Speech output shall be provided for all information displayed on-screen.4

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

Stylistic rewording

Explanatory update

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

402.2.2 Transactional Outputs

Where transactional outputs are provided, the speech output shall audibly provide all information necessary to verify a transaction.

5.1.3.16 Receipts, tickets, and transactional outputs

Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.

NOTE: The speech output may be provided by any element of the total ICT system.

Stylistic rewording

Explanatory update

5.1.3.16 Receipts, tickets, and transactional outputs

Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.

NOTE: The speech output may be provided by any element of the total ICT system.

5.1.3.16 Receipts, tickets, and transactional outputs

Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.

NOTE: The speech output may be provided by any element of the total ICT system.

5.1.3.16 Receipts, tickets, and transactional outputs

Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.

NOTE: The speech output may be provided by any element of the total ICT system.

402.2.3 Speech Delivery Type and Coordination Speech output shall be delivered through a mechanism that is readily available to all users, including, but not limited to, an industry standard connector or a telephone handset. Speech shall be recorded or digitized human, or synthesized. Speech output shall be coordinated with information displayed on the screen.

5.1.3.2 Auditory output delivery including speech

Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:

  1. either directly by a mechanism included in or provided with the ICT;
  2. or by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision.

NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in handset/headset, or other industry standard coupled peripheral.

NOTE 2: An industry standard connection could be a wireless connection.

NOTE 3: Some users may benefit from the provision of an inductive loop.

Stylistic rewording

Explanatory update

5.1.3.2 Auditory output delivery including speech

Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:

  1. either directly by a mechanism included in or provided with the ICT; or
  2. by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision.

NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in handset/headset, or other industry standard coupled peripheral.

NOTE 2: An industry standard connection could be a wireless connection.

NOTE 3: Some users may benefit from the provision of an inductive loop.

5.1.3.2 Auditory output delivery including speech

Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:

  1. either directly by a mechanism included in or provided with the ICT; or
  2. by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision.

NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in handset/headset, or other industry standard coupled peripheral.

NOTE 2: An industry standard connection could be a wireless connection.

NOTE 3: Some users may benefit from the provision of an inductive loop.

5.1.3.2 Auditory output delivery including speech

Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:

  1. either directly by a mechanism included in or provided with the ICT; or
  2. by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision.

NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in handset/headset, or other industry standard coupled peripheral.

NOTE 2: An industry standard connection could be a wireless connection.

NOTE 3: Some users may benefit from the provision of an inductive loop.

402.2.3 Speech Delivery Type and Coordination

Speech output shall be delivered through a mechanism that is readily available to all users, including, but not limited to, an industry standard connector or a telephone handset. Speech shall be recorded or digitized human, or synthesized. Speech output shall be coordinated with information displayed on the screen.

5.1.3.3 Auditory output correlation

Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

Stylistic rewording

Explanatory update

5.1.3.3 Auditory output correlation

Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

5.1.3.3 Auditory output correlation

Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

5.1.3.3 Auditory output correlation

Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

402.2.4 User Control

Speech output for any single function shall be automatically interrupted when a transaction is selected. Speech output shall be capable of being repeated and paused.

5.1.3.4 Speech output user control

Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.

NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.

NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to start from the beginning.

Stylistic rewording

Explanatory update

5.1.3.4 Speech output user control

Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.

NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.

NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to start from the beginning.

5.1.3.4 Speech output user control

Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.

NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.

NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to start from the beginning.

5.1.3.4 Speech output user control

Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.

NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.

NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to start from the beginning.

402.2.4 User Control

Speech output for any single function shall be automatically interrupted when a transaction is selected. Speech output shall be capable of being repeated and paused.

5.1.3.5 Speech output automatic interruption

Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.

NOTE: Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT may need to block all user action so that speech is not interrupted.

Stylistic rewording

Explanatory update

5.1.3.5 Speech output automatic interruption

Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.

NOTE: Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT may need to block all user action so that speech is not interrupted.

5.1.3.5 Speech output automatic interruption

Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.

NOTE: Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT may need to block all user action so that speech is not interrupted.

5.1.3.5 Speech output automatic interruption

Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.

NOTE: Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT may need to block all user action so that speech is not interrupted.

402.2.5 Braille Instructions

Where speech output is required by 402.2, braille instructions for initiating the speech mode of operation shall be provided. Braille shall be contracted and shall conform to 36 CFR part 1191, Appendix D, Section 703.3.1.

EXCEPTION: Devices for personal use shall not be required to conform to 402.2.5.

8.5 Tactile indication of speech mode

Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.

NOTE: The tactile indication could include Braille instructions.

Stylistic rewording

Explanatory update

Functional change

8.5 Tactile indication of speech mode

Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.

NOTE: The tactile indication could include Braille instructions.

8.5 Tactile indication of speech mode

Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.

NOTE: The tactile indication could include Braille instructions.

8.5 Tactile indication of speech mode

Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.

NOTE: The tactile indication could include Braille instructions.

402.3.1 Private Listening

Where ICT provides private listening, it shall provide a mode of operation for controlling the volume. Where ICT delivers output by an audio transducer typically held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.

5.1.3.11 Private listening volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.

Stylistic rewording

Explanatory update

5.1.3.11 Private listening volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.

5.1.3.11 Private listening volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.

5.1.3.11 Private listening volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.

402.3.1 Private Listening

Where ICT provides private listening, it shall provide a mode of operation for controlling the volume. Where ICT delivers output by an audio transducer typically held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.5

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETS 300 381, it shall provide a means of magnetic coupling which meets the requirements of ES 200 381-1.

NOTE: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

Stylistic rewording

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETSI ETS 300 381, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1.

NOTE: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1 and shall carry the "T" symbol specified in ETSI ETS 300 381.

NOTE 1: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

NOTE 2: Magnetic coupling is also known as inductive coupling for T-coil.

Stylistic rewording

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1 [2] and shall carry the "T" symbol specified in ETSI ETS 300 381 [1].

NOTE 1: ICT fulfilling the requirements of TIA-1083-A [i.24] is deemed to comply with the requirements of this clause. NOTE 2: Magnetic coupling is also known as inductive coupling for T-coil.

402.3.1 Private Listening

Where ICT provides private listening, it shall provide a mode of operation for controlling the volume. Where ICT delivers output by an audio transducer typically held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.6

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

Stylistic rewording

Explanatory update

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

Explanatory update

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2 [3].

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 [i.1] is deemed to comply with the requirements of this clause.

402.3.2 Non-private Listening

Where ICT provides non-private listening, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. A function shall be provided to automatically reset the volume to the default level after every use.

5.1.3.12 Speaker volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).

NOTE: For noisy environments, 65dBA may not be sufficient.

Stylistic rewording

5.1.3.12 Speaker volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).

NOTE: For noisy environments, 65 dBA may not be sufficient.

5.1.3.12 Speaker volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).

NOTE: For noisy environments, 65 dBA may not be sufficient.

5.1.3.12 Speaker volume

Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).

NOTE: For noisy environments, 65 dBA may not be sufficient.

402.3.2 Non-private Listening Where ICT provides non-private listening, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. A function shall be provided to automatically reset the volume to the default level after every use.

5.1.3.13 Volume reset

Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.

NOTE: A feature to disable the volume reset function may be provided in order to enable the single-user exception to be met.

Stylistic rewording

Explanatory update

5.1.3.13 Volume reset

Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.

NOTE: A feature to disable the volume reset function may be provided in order to enable the single-user exception to be met.

5.1.3.13 Volume reset

Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.

NOTE: A feature to disable the volume reset function may be provided in order to enable the single-user exception to be met.

5.1.3.13 Volume reset

Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.

NOTE: A feature to disable the volume reset function may be provided in order to enable the single-user exception to be met.

402.4 Characters on Display Screens

At least one mode of characters displayed on the screen shall be in a sans serif font. Where ICT does not provide a screen enlargement feature, characters shall be 3/16 inch (4.8 mm) high minimum based on the uppercase letter “I”. Characters shall contrast with their background with either light characters on a dark background or dark characters on a light background.7

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

Stylistic rewording

Explanatory update

Functional change

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE 1: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

402.5 Characters on Variable Message Signs. Characters on variable message signs shall conform to section 703.7 Variable Message Signs of ICC A117.1-2009 (incorporated by reference, see 702.6.1).8

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

Explanatory update

Functional change

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

5.1.4 Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.

The subtended angle, in degrees, may be calculated from:

Ψ = (180 x H) / (π x D)

Where:

  • ψ is the subtended angle in degrees
  • H is the height of the text
  • D is the viewing distance
  • D and H are expressed in the same units

NOTE 1: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.

List tables

403 Biometrics

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

403.1 General Biometrics shall not be the only means for user identification or control.

EXCEPTION: Where at least two biometric options that use different biological characteristics are provided, ICT shall be permitted to use biometrics as the only means of user identification or control.

5.3 Biometrics

Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.

NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.

NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals with disabilities possess at least one of the specified biological characteristics. Examples of dissimilar biological characteristics are fingerprints, eye retinal patterns, voice, and face.

Stylistic rewording

Explanatory update

5.3 Biometrics

Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.

NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.

NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals with disabilities possess at least one of the specified biological characteristics. Examples of dissimilar biological characteristics are fingerprints, eye retinal patterns, voice, and face.

5.3 Biometrics

Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.

NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.

NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals with disabilities possess at least one of the specified biological characteristics. Examples of dissimilar biological characteristics are fingerprints, eye retinal patterns, voice, and face.

5.3 Biometrics

Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.

NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.

NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals with disabilities possess at least one of the specified biological characteristics.

List tables

404 Preservation of Information Provided for Accessibility

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
404.1 General ICT that transmits or converts information or communication shall not remove non-proprietary information provided for accessibility or shall restore it upon delivery.

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

Stylistic rewording

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

List tables

405 Privacy

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

405.1 General

The same degree of privacy of input and output shall be provided to all individuals. When speech output required by 402.2 is enabled, the screen shall not blank automatically.9

5.1.3.9 Private access to personal data

Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.

NOTE 1: This requirement does not apply in cases where data is not defined as being private according to the applicable privacy policy or where there is no applicable privacy policy.

NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

Stylistic rewording

Explanatory update

5.1.3.9 Private access to personal data

Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.

NOTE 1: This requirement does not apply in cases where data is not defined as being private according to the applicable privacy policy or where there is no applicable privacy policy.

NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.9 Private access to personal data

Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.

NOTE 1: This requirement does not apply in cases where data is not defined as being private according to the applicable privacy policy or where there is no applicable privacy policy.

NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.9 Private access to personal data

Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.

NOTE 1: This requirement does not apply in cases where data is not defined as being private according to the applicable privacy policy or where there is no applicable privacy policy.

NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

405.1 General The same degree of privacy of input and output shall be provided to all individuals. When speech output required by 402.2 is enabled, the screen shall not blank automatically.10

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

Stylistic rewording

Explanatory update

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

5.1.3.8 Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.

NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.

NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.

List tables

406 Standard Connections

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
406.1 General Where data connections used for input and output are provided, at least one of each type of connection shall conform to industry standard non-proprietary formats.

8.1.2 Standard connections

Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.

NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the use of standard connections on ICT.

NOTE 2: The word connection applies to both physical and wireless connections.

NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.

Stylistic rewording

Explanatory update

8.1.2 Standard connections

Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.

NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the use of standard connections on ICT.

NOTE 2: The word connection applies to both physical and wireless connections.

NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.

8.1.2 Standard connections

Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.

NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the use of standard connections on ICT.

NOTE 2: The word connection applies to both physical and wireless connections.

NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.

8.1.2 Standard connections

Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.

NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the use of standard connections on ICT.

NOTE 2: The word connection applies to both physical and wireless connections.

NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.

List tables

407 Operable Parts

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

407.3.1 Tactilely Discernible

Input controls shall be operable by touch and tactilely discernible without activation.

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

Stylistic rewording

Explanatory update

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

407.3.1 Tactilely Discernible

Input controls shall be operable by touch and tactilely discernible without activation.

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

Stylistic rewording

Explanatory update

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and the status of that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

Explanatory update

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and the status of that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

407.3.2 Alphabetic Keys Where provided, individual alphabetic keys shall be arranged in a QWERTY-based keyboard layout and the “F” and “J” keys shall be tactilely distinct from the other keys.11

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

Stylistic rewording

Explanatory update

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

5.5.2 Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.

NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.

407.3.3 Numeric Keys

Where provided, numeric keys shall be arranged in a 12-key ascending or descending keypad layout. The number five key shall be tactilely distinct from the other keys. Where the ICT provides an alphabetic overlay on numeric keys, the relationships between letters and digits shall conform to ITU-T Recommendation E.161 (incorporated by reference, see 702.7.1).12

8.4.1 Numeric keys

Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.

NOTE: Recommendation ITU-T E.161 describes the 12-key telephone keypad layout and provides further details of the form of tactile markers.

Stylistic rewording

Explanatory update

8.4.1 Numeric keys

Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.

NOTE: Recommendation ITU-T E.161 describes the 12-key telephone keypad layout and provides further details of the form of tactile markers.

8.4.1 Numeric keys

Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.

NOTE: Recommendation ITU-T E.161 describes the 12-key telephone keypad layout and provides further details of the form of tactile markers.

8.4.1 Numeric keys

Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.

NOTE: Recommendation ITU-T E.161 [i.20] describes the 12-key telephone keypad layout and provides further details of the form of tactile markers.

407.4 Key Repeat

Where a keyboard with key repeat is provided, the delay before the key repeat feature is activated shall be fixed at, or adjustable to, 2 seconds minimum.

5.7: Key repeat

Where ICT with key repeat is provided and the key repeat cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

Stylistic rewording

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

Stylistic rewording

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

407.6 Operation

At least one mode of operation shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate operable parts shall be 5 pounds (22.2 N) maximum.

5.5.1 Means of operation

Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.

Stylistic rewording

Explanatory update

5.5.1 Means of operation

Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.

5.5.1 Means of operation

Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.

5.5.1 Means of operation

Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.

407.6 Operation At least one mode of operation shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate operable parts shall be 5 pounds (22.2 N) maximum.

8.4.2.1 Means of Operation of mechanical parts

Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.

Stylistic rewording

Explanatory update

8.4.2.1 Means of operation of mechanical parts

Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.

8.4.2.1 Means of operation of mechanical parts

Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.

8.4.2.1 Means of operation of mechanical parts

Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.

407.6 Operation At least one mode of operation shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate operable parts shall be 5 pounds (22.2 N) maximum.

8.4.2.2 Force of operation of mechanical parts

Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.

Stylistic rewording

Explanatory update

8.4.2.2 Force of operation of mechanical parts

Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.

8.4.2.2 Force of operation of mechanical parts

Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.

NOTE: ISO 21542:2011: Building Construction - Accessibility and Usability of the Built Environment recommends a value between 2,5 and 5 Newtons.

Explanatory update

8.4.2.2 Force of operation of mechanical parts

Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.

NOTE: ISO 21542:2011 [i.34]: Building Construction - Accessibility and Usability of the Built Environment recommends a value between 2,5 and 5 Newtons.

407.7 Tickets, Fare Cards, and Keycards

Where tickets, fare cards, or keycards are provided, they shall have an orientation that is tactilely discernible if orientation is important to further use of the ticket, fare card, or keycard.

8.4.3 Keys, tickets and fare cards

Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.

NOTE: ETS 300 767 defines suitable tactile indications for plastic cards.

Stylistic rewording

Explanatory update

8.4.3 Keys, tickets and fare cards

Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.

NOTE: ETSI ETS 300 767 defines suitable tactile indications for plastic cards.

Explanatory update

8.4.3 Keys, tickets and fare cards

Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.

NOTE: ETSI ETS 300 767 defines suitable tactile indications for plastic cards.

8.4.3 Keys, tickets and fare cards

Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.

NOTE: ETSI ETS 300 767 [i.6] defines suitable tactile indications for plastic cards.

407.8.1.1 Vertical Plane for Side Reach

Where a side reach is provided, the vertical reference plane shall be 48 inches (1220 mm) long minimum.

8.3.2.2 Clear floor or ground space

Where the operating area is integral to the ICT, it should provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

Stylistic rewording

Explanatory update

8.3.2.2 Clear floor or ground space

Where the operating area is integral to the ICT, it should provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

8.3.4.2 Clear floor or ground space

Where stationary ICT has an operating area within it, it shall provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

Numbering change

Stylistic rewording

Functional change

8.3.4.2 Clear floor or ground space

Where stationary ICT has an operating area within it, it shall provide a clear floor area that has the minimum

dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

407.8.1.2 Vertical Plane for Forward Reach Where a forward reach is provided, the vertical reference plane shall be 30 inches (760 mm) long minimum.

8.3.2.2 Clear floor or ground space

Where the operating area is integral to the ICT, it should provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

Stylistic rewording

Explanatory update

8.3.2.2 Clear floor or ground space

Where the operating area is integral to the ICT, it should provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

8.3.4.2 Clear floor or ground space

Where stationary ICT has an operating area within it, it shall provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

Numbering change

Stylistic rewording

Functional change

8.3.4.2 Clear floor or ground space

Where stationary ICT has an operating area within it, it shall provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.

407.8.2.1 Unobstructed Side Reach

Where the operable part is located 10 inches (255 mm) or less beyond the vertical reference plane, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.

8.3.3.2.1 Unobstructed high side reach

Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.2.1 Unobstructed high side reach

Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space.

8.3.3.1 Unobstructed high side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.3.1 Unobstructed high side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space.

407.8.2.1 Unobstructed Side Reach Where the operable part is located 10 inches (255 mm) or less beyond the vertical reference plane, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.

8.3.3.2.2 Unobstructed low side reach

Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.2.2 Unobstructed low side reach

Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space.

8.3.3.2 Unobstructed low side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

Explanatory update

8.3.3.2 Unobstructed low side reach

Where the side reach is unobstructed or obstructed by an element that is an integral part of the stationary ICT and which is less than 255 mm (10 inches), at least one of each type of operable part shall be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space.

407.8.2.2 Obstructed Side Reach

Where the operable part is located more than 10 inches (255 mm), but not more than 24 inches (610 mm), beyond the vertical reference plane, the height of the operable part shall be 46 inches (1170 mm) high maximum and 15 inches (380 mm) high minimum above the floor. The operable part shall not be located more than 24 inches (610 mm) beyond the vertical reference plane.

8.3.3.2.3.1 Obstructed (<= 255 mm) side reach

Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is less than or equal to 255 mm (10 inches), the high side reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.2.3.1 Obstructed (<= 255 mm) side reach

Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is less than or equal to 255 mm (10 inches), the high side reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor of the access space.

8.3.3.3.1 Obstructed (<= 255 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is less than or equal to 255 mm (10 inches), the high side reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.3.3.1 Obstructed (≤ 255 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is less than or equal to 255 mm (10 inches), the high side reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor of the access space.

407.8.2.2 Obstructed Side Reach

Where the operable part is located more than 10 inches (255 mm), but not more than 24 inches (610 mm), beyond the vertical reference plane, the height of the operable part shall be 46 inches (1170 mm) high maximum and 15 inches (380 mm) high minimum above the floor. The operable part shall not be located more than 24 inches (610 mm) beyond the vertical reference plane.

8.3.3.2.3.2 Obstructed (<= 610 mm) side reach

Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is greater than 255 mm (10 inches) and 610 mm (24 inches) maximum, the high side reach to all essential controls should be no higher than 1 170 mm (46 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.2.3.2 Obstructed (<= 610 mm) side reach

Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is greater than 255 mm (10 inches) with a maximum depth of 610 mm (24 inches), the high side reach to all essential controls should be no higher than 1 170 mm (46 inches) above the floor of the access space.

Stylistic rewording

8.3.3.3.2 Obstructed (<= 610 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is greater than 255 mm (10 inches) with a maximum depth of 610 mm (24 inches), the high side reach to at least one of each type of operable part shall be no higher than 1 170 mm (46 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

Explanatory update

8.3.3.3.2 Obstructed (≤ 610 mm) side reach

Where stationary ICT has an obstruction which is an integral part of the ICT, the height of the obstruction shall be less than 865 mm (34 inches). Where the depth of the obstruction is greater than 255 mm (10 inches) with a maximum depth of 610 mm (24 inches), the high side reach to at least one of each type of operable part shall be no higher than 1 170 mm (46 inches) above the floor of the access space.

407.8.3 Forward Reach

Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

8.3.3.1.1 Unobstructed high forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no higher than 1 220 mm (48 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.1 Unobstructed high forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no higher than 1 220 mm (48 inches) above the floor of the access space.

8.3.2.1 Unobstructed high forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no higher than 1 220 mm (48 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

8.3.2.1 Unobstructed high forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no higher than 1 220 mm (48 inches) above the floor of the access space.

407.8.3 Forward Reach

Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

8.3.3.1.2 Unobstructed low forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no lower than 380 mm (15 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.2 Unobstructed low forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no lower than 380 mm (15 inches) above the floor of the access space.

8.3.2.2 Unobstructed low forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no lower than 380 mm (15 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

8.3.2.2 Unobstructed low forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no lower than 380 mm (15 inches) above the floor of the access space.

407.8.3 Forward Reach

Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory

Functional change

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

407.8.3 Forward Reach

Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

407.8.3.1 Unobstructed Forward Reach Where the operable part is located at the leading edge of the maximum protrusion within the length of the vertical reference plane of the ICT, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.

8.3.3.1.1 Unobstructed high forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no higher than 1 220 mm (48 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.1.1 Unobstructed high forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no higher than 1 220 mm (48 inches) above the floor of the access space.

8.3.2.1 Unobstructed high forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no higher than 1 220 mm (48 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

8.3.2.1 Unobstructed high forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no higher than 1 220 mm (48 inches) above the floor of the access space.

407.8.3.1 Unobstructed Forward Reach Where the operable part is located at the leading edge of the maximum protrusion within the length of the vertical reference plane of the ICT, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.

8.3.3.1.2 Unobstructed low forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no lower than 380 mm (15 inches) above the floor of the access space.

Stylistic rewording

Explanatory update

8.3.3.1.2 Unobstructed low forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no lower than 380 mm (15 inches) above the floor of the access space.

8.3.2.2 Unobstructed low forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no lower than 380 mm (15 inches) above the floor of the access space.

Numbering change

Stylistic rewording

Functional change

8.3.2.2 Unobstructed low forward reach

Where no part of the stationary ICT obstructs the forward reach, at least one of each type of operable part shall be located no lower than 380 mm (15 inches) above the floor of the access space.

407.8.3.2 Obstructed Forward Reach Where the operable part is located beyond the leading edge of the maximum protrusion within the length of the vertical reference plane, the operable part shall conform to 407.8.3.2. The maximum allowable forward reach to an operable part shall be 25 inches (635 mm).

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory

Functional change

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

407.8.3.2 Obstructed Forward Reach Where the operable part is located beyond the leading edge of the maximum protrusion within the length of the vertical reference plane, the operable part shall conform to 407.8.3.2. The maximum allowable forward reach to an operable part shall be 25 inches (635 mm).

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach The height of the operable part shall conform to Table 407.8.3.2.1.

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.2 Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory

Functional change

8.3.2.3.2 Obstructed (< 510 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is less than 510 mm (20 inches), the forward reach to at least one of each type of operable part shall be no higher than 1 220 mm (48 inches) above the floor contact of the ICT.

407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach The height of the operable part shall conform to Table 407.8.3.2.1.

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Stylistic rewording

Explanatory update

Functional change

8.3.3.1.3.3 Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.2.3.3 Obstructed (< 635 mm) forward reach

Where the stationary ICT has an obstruction which is an integral part of the ICT and which is not less than 510 mm (20 inches) but is less than 635 mm (25 inches) maximum, the forward reach to at least one of each type of operable part shall be no higher than 1 120 mm (44 inches) above the floor contact of the ICT.

407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach

Knee and toe space under ICT shall be 27 inches (685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30 inches (760 mm) wide minimum and shall be clear of obstructions.

EXCEPTIONS:

  1. Toe space shall be permitted to provide a clear height of 9 inches (230 mm) above the floor and a clear depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT.
  2. At a depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT, space between 9 inches (230 MM) and 27 inches (685 mm) minimum above the floor shall be permitted to reduce at a rate of 1 inch (25 mm) in depth for every 6 inches (150 mm) in height.13

8.3.2.4 Knee and toe clearance width

Where the space under an obstacle that is integral to the ICT is part of access space, the clearance should be at least 760 mm (30 inches) wide.

Stylistic rewording

Explanatory update

8.3.2.4 Knee and toe clearance width

Where the space under an obstacle that is integral to the ICT is part of access space, the clearance should be at least 760 mm (30 inches) wide.

8.3.2.4 Knee and toe clearance width

Where the space under an obstacle that is an integral part of the stationary ICT is part of access space, the clearance shall be at least 760 mm (30 inches) wide.

Stylistic rewording

Functional change

8.3.2.4 Knee and toe clearance width

Where the space under an obstacle that is an integral part of the stationary ICT is part of access space, the clearance shall be at least 760 mm (30 inches) wide.

407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach Knee and toe space under ICT shall be 27 inches (685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30 inches (760 mm) wide minimum and shall be clear of obstructions.

EXCEPTIONS:

  1. Toe space shall be permitted to provide a clear height of 9 inches (230 mm) above the floor and a clear depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT.
  2. At a depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT, space between 9 inches (230 mm) and 27 inches (685 mm) minimum above the floor shall be permitted to reduce at a rate of 1 inch (25 mm) in depth for every 6 inches (150 mm) in height.14

8.3.2.5 Toe clearance

Where an obstacle is integral to the ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and should:

  1. extend 635 mm (25 inches) maximum under the whole obstacle;
  2. provide a space at least 430 mm (17 inches) deep and 230 mm above the floor under the obstacle;
  3. extend no more than150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

Stylistic rewording

Explanatory update

Functional change

8.3.2.5 Toe clearance

Where an obstacle is integral to the ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and should:

  1. extend 635 mm (25 inches) maximum under the whole obstacle;
  2. provide a space at least 430 mm (17 inches) deep and 230 mm above the floor under the obstacle;
  3. extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

8.3.2.5 Toe clearance

Where an obstacle is an integral part of the stationary ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and shall:

  1. extend 635 mm (25 inches) maximum under the whole obstacle;
  2. provide a space at least 430 mm (17 inches) deep and 230 mm (9 inches) above the floor under the obstacle;
  3. extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

Stylistic rewording

Functional change

Explanatory update

8.3.2.5 Toe clearance

Where an obstacle is an integral part of the stationary ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and shall:

  1. extend 635 mm (25 inches) maximum under the whole obstacle;
  2. provide a space at least 430 mm (17 inches) deep and 230 mm (9 inches) above the floor under the obstacle;
  3. extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach Knee and toe space under ICT shall be 27 inches (685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30 inches (760 mm) wide minimum and shall be clear of obstructions.

EXCEPTIONS:

  1. Toe space shall be permitted to provide a clear height of 9 inches (230 mm) above the floor and a clear depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT.
  2. At a depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT, space between 9 inches (230 MM) and 27 inches (685 mm) minimum above the floor shall be permitted to reduce at a rate of 1 inch (25 mm) in depth for every 6 inches (150 mm) in height.15

8.3.2.6 Knee clearance

Where an obstacle is integral to the ICT, the space under the obstacle that is between 230 mm and 685 mm above the floor is considered knee clearance and should:

  1. extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  2. extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  3. extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;
  4. be between 230 mm (9 inches) and 685 mm (27 inches) above the floor be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.

Stylistic rewording

Explanatory update

Functional change

8.3.2.6 Knee clearance

Where an obstacle is integral to the ICT, the space under the obstacle that is between 230 mm and 685 mm above the floor is considered knee clearance and should:

  1. extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  2. extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  3. extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;
  4. d) be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.
Stylistic rewording

8.3.2.6 Knee clearance

Where an obstacle is an integral part of the stationary ICT, the space under the obstacle that is between 230 mm (9 inches) and 685 mm (25 inches)16 above the floor is considered knee clearance and shall:

  1. extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  2. extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  3. extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;
  4. d) be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.

Stylistic rewording

Explanatory update

Functional change

8.3.2.6 Knee clearance

Where an obstacle is an integral part of the stationary ICT, the space under the obstacle that is between 230 mm (9 inches) and 685 mm (25 inches) above the floor is considered knee clearance and shall:

  1. extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  2. extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;
  3. extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;
  4. d) be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.

List tables

408 Display Screen

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
408.2 Visibility Where stationary ICT provides one or more display screens, at least one of each type of display screen shall be visible from a point located 40 inches (1015 mm) above the floor space where the display screen is viewed.

8.3.4 Visibility

Where the operating area is integral to the ICT, and a display screen is provided, information on the screen should be legible from a point located 1 015 mm (40 inches) above the centre of the floor of the operating area (as defined in clause 8.3.2.2).

NOTE: The intent of this provision is that the information on the screen can be read by users with normal vision and appropriate language skills, when seated in a wheelchair.

Stylistic rewording

Explanatory update

8.3.4 Visibility

Where the operating area is integral to the ICT, and a display screen is provided, information on the screen should be legible from a point located 1 015 mm (40 inches) above the centre of the floor of the operating area (as defined in clause 8.3.2.2).

NOTE: The intent of this provision is that the information on the screen can be read by users with normal vision and appropriate language skills, when seated in a wheelchair.

8.3.5 Visibility

Where stationary ICT provides one or more display screens , at least one of each type of display screen shall be positioned such that the information on the screen is legible from a point located 1 015 mm (40 inches) above the centre of the floor of the operating area).

NOTE: The intent of this requirement is that the information on the screen can be read by users with normal vision and appropriate language skills, when seated in a wheelchair.

Numbering change

Stylistic rewording

Functional change

8.3.5 Visibility

Where stationary ICT provides one or more display screens, at least one of each type of display screen shall be positioned such that the information on the screen is legible from a point located 1 015 mm (40 inches) above the centre of the floor of the operating area).

NOTE: The intent of this requirement is that the information on the screen can be read by users with normal vision and appropriate language skills, when seated in a wheelchair.

List tables

409 Status Indicators

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

409.1 General

Where provided, status indicators shall be discernible visually and by touch or sound.

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

Stylistic rewording

Explanatory update

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and the status of that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

Explanatory update

5.6.1 Tactile or auditory status

Where ICT has a locking or toggle control and the status of that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

409.1 General Where provided, status indicators shall be discernible visually and by touch or sound.

5.6.2 Visual status

Where ICT has a locking or toggle control and the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example of making the status of a control determinable is a visual status indicator on a keyboard.

Stylistic rewording

Explanatory update

5.6.2 Visual status

Where ICT has a locking or toggle control and the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example of making the status of a control determinable is a visual status indicator on a keyboard.

5.6.2 Visual status

Where ICT has a locking or toggle control and the status of the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example of making the status of a control determinable is a visual status indicator on a keyboard.

Explanatory update

5.6.2 Visual status

Where ICT has a locking or toggle control and the status of the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.

NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example of making the status of a control determinable is a visual status indicator on a keyboard.

List tables

410 Color Coding

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
410.1 General Where provided, color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

8.1.3 Colour

Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Stylistic rewording

8.1.3 Colour

Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

8.1.3 Colour

Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

8.1.3 Colour

Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

List tables

412 ICT with Two-Way Voice Communication

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

412.2.1 Volume Gain for Wireline Telephones

Volume gain conforming to 47 CFR 68.317 shall be provided on analog and digital wireline telephones.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

Stylistic rewording

Explanatory update

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

412.2.1 Volume Gain for Wireline Telephones

Volume gain conforming to 47 CFR 68.317 shall be provided on analog and digital wireline telephones.17

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

Stylistic rewording

Explanatory update

Functional change

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

412.2.2 Volume Gain for Non-Wireline ICT

A method for increasing volume shall be provided for non-wireline ICT.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

Stylistic rewording

Explanatory update

Functional change

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

8.2.1.1 Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.

NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 are deemed to comply with this requirement.

412.2.2 Volume Gain for Non-Wireline ICT

A method for increasing volume shall be provided for non-wireline ICT.18

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

Stylistic rewording

Explanatory update

Functional change

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

8.2.1.2 Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

412.3.1 Wireless Handsets

ICT in the form of wireless handsets shall conform to ANSI/IEEE C63.19-2011 (incorporated by reference, see 702.5.1).19

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

Stylistic rewording

Explanatory update

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

Explanatory update

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2.

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

8.2.2.2 Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2

NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 is deemed to comply with the requirements of this clause.

412.3.2 Wireline Handsets

ICT in the form of wireline handsets, including cordless handsets, shall conform to TIA-1083-B (incorporated by reference, see 702.9.1).20

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETS 300 381, it shall provide a means of magnetic coupling which meets the requirements of ES 200 381-1.

NOTE: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

Stylistic rewording

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETSI ETS 300 381, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1.

NOTE: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1 and shall carry the "T" symbol specified in ETSI ETS 300 381.

NOTE 1: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause.

NOTE 2: Magnetic coupling is also known as inductive coupling for T-coil.

Stylistic rewording

Explanatory update

8.2.2.1 Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear, it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1 and shall carry the "T" symbol specified in ETSI ETS 300 381.

NOTE 1: ICT fulfilling the requirements of TIA-1083-A is deemed to comply with the requirements of this clause. NOTE 2: Magnetic coupling is also known as inductive coupling for T-coil.

412.4 Digital Encoding of Speech

ICT in IP-based networks shall transmit and receive speech that is digitally encoded in the manner specified by ITU-T Recommendation G.722.2 (incorporated by reference, see 702.7.2) or IETF RFC 6716 (incorporated by reference, see 702.8.1).21

6.1: Audio bandwidth for speech (informative recommendation)

Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT should be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7 000 Hz.

NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 is widely used.

NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation ITU-T G.722.2 are sometimes used so as to avoid transcoding.

Stylistic rewording

Explanatory update

Functional change

6.1 Audio bandwidth for speech

Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT shall be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7 000 Hz.

NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 is widely used.

NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation ITU-T G.722.2 are sometimes used so as to avoid transcoding.

Functional change

6.1 Audio bandwidth for speech

Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT shall be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7 000 Hz.

NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 is widely used.

NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation ITU-T G.722.2 are sometimes used so as to avoid transcoding.

6.1 Audio bandwidth for speech

Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT shall be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7 000 Hz.

NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 is widely used.

NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation ITU-T G.722.2 are sometimes used so as to avoid transcoding.

412.5 Real-Time Text Functionality [Reserved].22See RTT requirements in EN 301 549 V1.1.1 (2014) Chapter 6, below.See RTT requirements in EN 301 549 V2.1.2 (2018) Chapter 6, below.See RTT requirements in EN 301 549 V3.1.1 (2019) Chapter 6, below.See RTT requirements in EN 301 549 V3.2.1 (2021) Chapter 6, below.
412.6 Caller ID Where provided, caller identification and similar tele-communications functions shall be visible and audible.23

6.3: Caller ID

Where ICT provides caller identification and similar tele-communications functions are provided, the caller identification and similar tele-communications functions shall be available in text form and in at least one other modality.

Stylistic rewording

Explanatory update

Functional change

6.3 Caller ID

Where ICT provides caller identification or similar tele-communications functions are provided, the caller identification and similar tele-communications functions shall be available in text form and in at least one other modality.

6.3 Caller ID

Where ICT provides caller identification or similar tele-communications functions, the caller identification and similar tele-communications functions shall be available in text form as well as being programmatically determinable, unless the functionality is closed.

Functional change

6.3 Caller ID

Where ICT provides caller identification or similar telecommunications functions, the caller identification and similar telecommunications functions shall be available in text form as well as being programmatically determinable, unless the functionality is closed.

412.7 Video Communication Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.24

6.5.1 General (informative)

Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with Common Intermediate Format (CIF) resolution, a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.

When the resolution is reduced to Quarter Common Intermediate Format (QCIF) and the frame rate drops to 12 frames per second the communication is still usable with some restrictions.

A lower resolution causes less disturbance to the perception of sign language and lip-reading than that caused by a lower frame rate.

Delay can be a problem in video communication. Overall delay values below 0,4 s are preferred, with an increase in preference down to 0,1 s. Values over 0,8 s are felt to hinder a good sign conversation. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.

Stylistic rewording

Explanatory update

Functional change

6.5.1 General (informative)

Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with Common Intermediate Format (CIF) resolution, a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.

When the resolution is reduced to Quarter Common Intermediate Format (QCIF) and the frame rate drops to 12 frames per second the communication is still usable with some restrictions.

A lower resolution causes less disturbance to the perception of sign language and lip-reading than that caused by a lower frame rate.

Delay can be a problem in video communication. Overall delay values below 0,4 s are preferred, with an increase in preference down to 0,1 s. Values over 0,8 s are felt to hinder a good sign conversation. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.

6.5.1 General (informative)

Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with a resolution of at least Quarter Video Graphics Array (QVGA, 320 x 240), a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.

Increasing the resolution and frame rate further improves both sign language (especially finger spelling) and lip-reading, with frame rate being more important than resolution.

Time differences between audio and video (asynchronicity) can have a great impact onlip-reading - with video that lags behind audio having greater negative effect.

End-to-end latency can be a problem in video (sign) communication. Overall delay values below 400 ms are preferred, with an increase in preference down to 100 ms. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.

NOTE: Recommendation ITU-T F.703 defines and gives requirements for Total Conversation that relate to the integration of audio, RTT and video in a single user connection.

Functional change

Explanatory update

Stylistic rewording

6.5.1 General (informative)

Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with a resolution of at least Quarter Video Graphics Array (QVGA, 320 x 240), a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.

Increasing the resolution and frame rate further improves both sign language (especially finger spelling) and lipreading, with frame rate being more important than resolution.

Time differences between audio and video (asynchronicity) can have a great impact onlip-reading - with video that lags behind audio having greater negative effect.

End-to-end latency can be a problem in video (sign) communication. Overall delay values below 400 ms are preferred, with an increase in preference down to 100 ms. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.

NOTE: Recommendation ITU-T F.703 defines and gives requirements for Total Conversation that relate to the integration of audio, RTT and video in a single user connection.

412.7 Video Communication Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.25

6.5.2 Resolution

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support at least QCIF resolution;

b) should preferably support at least CIF resolution.

Stylistic rewording

Explanatory update

Functional change

6.5.2 Resolution

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support at least QCIF resolution;

b) should preferably support at least CIF resolution.

6.5.2 Resolution

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support at least QVGA resolution;

b) should preferably support at least VGA resolution.

Functional update

6.5.2 Resolution

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support at least QVGA resolution;

b) should preferably support at least VGA resolution.

412.7 Video Communication Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.26

6.5.3 Frame rate

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support a frame rate of at least 12 frames per second (FPS);

b) should preferably support a frame rate of at least 20 frames per second (FPS) with or without sign language in the video stream.

Stylistic rewording

Explanatory update

Functional change

6.5.3 Frame rate

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support a frame rate of at least 12 frames per second (FPS);

b) should preferably support a frame rate of at least 20 frames per second (FPS) with or without sign language in the video stream.

6.5.3 Frame rate

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support a frame rate of at least 20 frames per second (FPS);

b) should preferably support a frame rate of at least 30 frames per second (FPS) with or without sign language in the video stream.

Functional update

6.5.3 Frame rate

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:

a) shall support a frame rate of at least 20 Frames Per Second (FPS);

b) should preferably support a frame rate of at least 30 Frames Per Second (FPS) with or without sign language in the video stream.

Stylistic change
412.7 Video Communication Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.27

6.5.4 Synchronization between audio and video

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT should ensure a maximum time difference of 100 ms between the speech and video presented to the user.

Stylistic rewording

Explanatory update

Functional change

6.5.4 Synchronization between audio and video

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT should ensure a maximum time difference of 100 ms between the speech and video presented to the user.

6.5.4 Synchronization between audio and video

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT shall ensure a maximum time difference of 100 ms between the speech and video presented to the user.

NOTE: Recent research shows that, if audio leads the video, the intelligibility suffers much more than the reverse.

Functional change

Explanatory update

6.5.4 Synchronization between audio and video

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT shall ensure a maximum time difference of 100 ms between the speech and video presented to the user.

NOTE: Recent research shows that, if audio leads the video, the intelligibility suffers much more than the reverse.

List tables

413 Closed Caption Processing Technologies

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
413.1.1 Decoding and Display of Closed Captions Players and displays shall decode closed caption data and support display of captions.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

Stylistic rewording

Explanatory update

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

Functional change

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

NOTE 3: Clause 7.1.1 refers to the ability of the player to display captions. Clauses 9.1.2.2, 10.1.2.2 and 11.1.2.2 refer to the provision of captions for the content (the video).

Explanatory update
413.1.2 Pass-Through of Closed Caption Data Cabling and ancillary equipment shall pass through caption data.

5.4: Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

Stylistic rewording

Explanatory update

Functional change

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.

413.1.2 Pass-Through of Closed Caption Data Cabling and ancillary equipment shall pass through caption data.

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

Stylistic rewording

Explanatory update

Functional change

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

List tables

414 Audio Description Processing Technologies

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

414.1.1 Digital Television Tuners

Digital television tuners shall provide audio description processing that conforms to ATSC A/53 Digital Television Standard, Part 5 (2014) (incorporated by reference, see 702.2.1). Digital television tuners shall provide processing of audio description when encoded as a Visually Impaired (VI) associated audio service that is provided as a complete program mix containing audio description according to the ATSC A/53 standard.28

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

Stylistic rewording

Explanatory update

Functional change

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

414.1.2 Other ICT

ICT other than digital television tuners shall provide audio description processing.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

Stylistic rewording

Explanatory update

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

List tables

415 User Controls for Captions and Audio Descriptions

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

415.1.1 Caption Controls

Where ICT provides operable parts for volume control, ICT shall also provide operable parts for caption selection.29

7.3: User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

Stylistic rewording

Explanatory update

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

415.1.2 Audio Description Controls

Where ICT provides operable parts for program selection, ICT shall also provide operable parts for the selection of audio description.30

7.3: User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

Stylistic rewording

Explanatory update

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

List tables

Chapter 5: Software

501 General

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

501.1 Scope

The requirements of Chapter 5 shall apply to software where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

EXCEPTION: Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

Chapters 9, 10, and 11 apply WCAG 2.0 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).

Explanatory update

Stylistic rewording

Chapters 9, 10, and 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).Functional changeChapters 9, 10, and 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).Chapters 9, 10, and 11 apply WCAG 2.1 Level A and Level AA Success Criteria to Web content (Chapter 9), Documents (Chapter 10), and Non-Web Software (Chapter 11).

List tables

502 Interoperability with Assistive Technology

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
502.2.1 User Control of Accessibility Features Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features.

11.4.1 User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

Stylistic rewording

11.6.1 User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

Numbering change

11.6.1 User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

11.6.1 User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

502.2.2 No Disruption of Accessibility Features Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.

11.4.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

Stylistic rewording

Explanatory update

11.6.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

Numbering change

11.6.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

11.6.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

502.3 Accessibility Services

Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms hall expose the underlying platform accessibility services or implement other documented accessibility services.

11.3.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Platform software should support requirements 11.3.2.5 to 11.3.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.3.2.5 to 11.3.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.3.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality of software providing user interfaces when using platform services.

NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 3: User interface services that provide accessibility support by default are considered to be part of the services provided to conform to this clause (i.e. the service for creating a new user interface element provides role, state, boundary, name and description).

NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

NOTE 5: Within specific programming environments, the technical attributes associated with the user interface properties described in clauses 11.3.2.5 to 11.3.2.17 might have different names than those used within the clauses.

Stylistic rewording

Explanatory update

11.5.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Platform software should support requirements 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality of software providing user interfaces when using platform services.

NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 3: User interface services that provide accessibility support by default are considered to be part of the services provided to conform to this clause (e.g. the service for creating a new user interface element provides role, state, boundary, name and description).

NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

NOTE 5: Within specific programming environments, the technical attributes associated with the user interface properties described in clauses 11.5.2.5 to 11.5.2.17 might have different names than those used within the clauses.

Numbering change

Stylistic rewording

11.5.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Where a user interface concept corresponding to one of the clauses 11.5.2.5 to 11.5.2.17 is supported within the software environment, the platform software should support that requirement. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality of software providing user interfaces when using platform services.

NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 3: User interface services that provide accessibility support by default are considered to be part of the services provided to conform to this clause (e.g. the service for creating a new user interface element provides role, state, boundary, name and description).

NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

NOTE 5: Within specific programming environments, the technical attributes associated with the user interface properties described in clauses 11.5.2.5 to 11.5.2.17 might have different names than those used within the clauses.

Stylistic rewording

11.5.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Where a user interface concept corresponding to one of the clauses 11.5.2.5 to 11.5.2.17 is supported within the software environment, the platform software should support that requirement. For example, selection attributes from clause 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality of software providing user interfaces when using platform services.

NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 3: User interface services that provide accessibility support by default are considered to be part of the services provided to conform to this clause (e.g. the service for creating a new user interface element provides role, state, boundary, name and description).

NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

NOTE 5: Within specific programming environments, the technical attributes associated with the user interface properties described in clauses 11.5.2.5 to 11.5.2.17 might have different names than those used within the clauses.

502.3 Accessibility Services

Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms hall expose the underlying platform accessibility services or implement other documented accessibility services.

11.3.2.2 Platform accessibility service support for assistive technologies

Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.

Platform software should support the requirements of clauses 11.3.2.5 to 11.3.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.3.2.5 to 11.3.2.17 is not supported within the software environment, these requirement are not applicable. For example, selection attributes from 11.3.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.

NOTE 2: The definition of platform in 3.1 applies to software that provides services to other software, including but not limited to, operating systems, internet browsers, virtual machines.

NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 4: Typically these services belong to the same set of services that are described in clause 11.3.2.1.

NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

Stylistic rewording

Explanatory update

11.5.2.2 Platform accessibility service support for assistive technologies

Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.

Platform software should support the requirements of clauses 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirement are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.

NOTE 2: The definition of platform in clause 3.1 applies to software that provides services to other software, including but not limited to, operating systems, web browsers, virtual machines.

NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 4: Typically these services belong to the same set of services that are described in clause 11.5.2.1.

NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

Numbering change

Stylistic rewording

11.5.2.2 Platform accessibility service support for assistive technologies

Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.

Where a user interface concept corresponding to one of the clauses 11.5.2.5 to 11.5.2.17 is supported within the software environment, the platform software should support that requirement. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.

NOTE 2: The definition of platform in clause 3.1 applies to software that provides services to other software, including but not limited to, operating systems, web browsers, virtual machines.

NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 4: Typically these services belong to the same set of services that are described in clause 11.5.2.1.

NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

Stylistic rewording

11.5.2.2 Platform accessibility service support for assistive technologies

Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.

Where a user interface concept corresponding to one of the clauses 11.5.2.5 to 11.5.2.17 is supported within the software environment, the platform software should support that requirement. For example, selection attributes from clause 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.

NOTE 2: The definition of platform in clause 3.1 applies to software that provides services to other software, including but not limited to, operating systems, web browsers, virtual machines.

NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.

NOTE 4: Typically these services belong to the same set of services that are described in clause 11.5.2.1.

NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.

502.3.1 Object Information

The object role, state(s), properties, boundary, name, and description shall be programmatically determinable.

11.3.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

Numbering change

11.5.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

11.5.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

502.3.2 Modification of Object Information States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology.

11.3.2.16 Modifications of states and properties

When permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Stylistic rewording

Explanatory update

Functional change

11.5.2.16 Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Numbering change

Stylistic rewording

11.5.2.16 Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.16 Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

502.3.3 Row, Column, and Headers

If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable.

11.3.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

Numbering change

11.5.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

11.5.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

502.3.4 Values Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable.

11.3.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.3.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

Numbering change

11.5.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

11.5.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

502.3.5 Modification of Values

Values that can be set by the user shall be capable of being set programmatically, including through assistive technology.

11.3.2.17 Modifications of values and text

When permitted by security requirements, software that provides a user interface shall, by using the services as described in 11.3.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Stylistic rewording

Explanatory update

Functional change

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Numbering change

Stylistic rewording

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

502.3.6 Label Relationships Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable.

11.3.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.3.2.3, so that this information is programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.

Numbering change

11.5.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.

11.5.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.

502.3.7 Hierarchical Relationships Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable.

11.3.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

Numbering change

11.5.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

11.5.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

502.3.8 Text

The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable.

11.3.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

Numbering change

11.5.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

11.5.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

502.3.9 Modification of Text

Text that can be set by the user shall be capable of being set programmatically, including through assistive technology.

11.3.2.17 Modifications of values and text

When permitted by security requirements, software that provides a user interface shall, by using the services as described in 11.3.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Stylistic rewording

Explanatory update

Functional change

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Numbering change

Stylistic rewording

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

502.3.10 List of Actions

A list of all actions that can be executed on an object shall be programmatically determinable.

11.3.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

Numbering change

11.5.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

11.5.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

502.3.11 Actions on Objects

Applications shall allow assistive technology to programmatically execute available actions on objects.

11.3.2.12 Execution of available actions

When permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow the programmatic execution of the actions exposed according to clause 11.3.2.11 by assistive technologies.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Stylistic rewording

Explanatory update

Functional change

11.5.2.12 Execution of available actions

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Numbering change

Stylistic rewording

11.5.2.12 Execution of available actions

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.12 Execution of available actions

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

502.3.12 Focus Cursor

Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components.

11.3.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

Stylistic rewording

Explanatory update

11.5.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

Numbering change

11.5.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

11.5.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

502.3.13 Modification of Focus Cursor Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.

11.3.2.14 Modification of focus and selection attributes

When permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Stylistic rewording

Explanatory update

Functional change

11.5.2.14 Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Numbering change

Stylistic rewording

11.5.2.14 Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.14 Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

502.3.14 Event Notification Notification of events relevant to user interactions, including but not limited to, changes in the component’s state(s), value, name, description, or boundary, shall be available to assistive technology.

11.3.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in 11.3.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.3.2.5 to 11.3.2.11 and 11.3.2.13.

Stylistic rewording

Explanatory update

11.5.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

Numbering change

Stylistic rewording

11.5.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

11.5.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

502.4 Platform Accessibility Features

Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:

See A-G, below.See A-G, below.See A-G, below.See A-G, below.
  1. Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;31

5.9: Simultaneous user actions

Where ICT uses simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.

NOTE: Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or having to touch a surface with more than one finger are examples of simultaneous user actions.

Stylistic rewording

Explanatory update

5.9 Simultaneous user actions

Where ICT uses simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.

NOTE: Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or having to touch a surface with more than one finger are examples of simultaneous user actions.

5.9 Simultaneous user actions

Where ICT has a mode of operation requiring simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.

NOTE: Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or having to touch a surface with more than one finger are examples of simultaneous user actions.

Stylistic rewording

5.9 Simultaneous user actions

Where ICT has a mode of operation requiring simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.

NOTE: Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or having to touch a surface with more than one finger are examples of simultaneous user actions.

  1. Section 9.3.4 Provide adjustment of delay before key acceptance;

5.7: Key repeat

Where ICT with key repeat is provided and the key repeat cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

Stylistic rewording

Explanatory update

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

Stylistic rewording

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

5.7 Key repeat

Where ICT has a key repeat function that cannot be turned off:

a) the delay before the key repeat shall be adjustable to at least 2 seconds; and

b) the key repeat rate shall be adjustable down to one character per 2 seconds.

  1. Section 9.3.5 Provide adjustment of same-key double-strike acceptance;32

5.8: Double-strike key acceptance

Where a keyboard or keypad is provided, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.

Stylistic rewording

Explanatory update

5.8 Double-strike key acceptance

Where ICT has a keyboard or keypad, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.

Stylistic rewording

5.8 Double-strike key acceptance

Where ICT has a keyboard or keypad, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.

5.8 Double-strike key acceptance

Where ICT has a keyboard or keypad, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.

  1. Section 10.7.1 Display any captions provided.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

Stylistic rewording

Explanatory update

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

Functional change

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

NOTE 3: Clause 7.1.1 refers to the ability of the player to display captions. Clauses 9.1.2.2, 10.1.2.2 and 11.1.2.2 refer to the provision of captions for the content (the video).

Explanatory change

List tables

503 Applications

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

503.2 User Preferences Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.

EXCEPTION: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2.

11.5 User preferences

Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for colour, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms.

NOTE: Software that is isolated from its underlying platform has no access to user settings in the platform and thus cannot adhere to them.

Stylistic rewording

Explanatory update

11.7 User preferences

Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for colour, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms.

NOTE: Software that is isolated from its underlying platform has no access to user settings in the platform and thus cannot adhere to them.

Numbering change

11.7 User preferences

Where software is not designed to be isolated from its platform, and provides a user interface, that user interface shall follow the values of the user preferences for platform settings for: units of measurement, colour, contrast, font type, font size, and focus cursor except where they are overridden by the user.

NOTE 1: Software that is isolated from its underlying platform has no access to user settings in the platform and thus cannot adhere to them.

NOTE 2: For web content, the underlying platform is the user agent.

NOTE 3: This does not preclude the software from having additional values for a setting as long as there is one mode where the application will follow the system settings even if more restricted.

Stylistic rewording

Functional change

11.7 User preferences

Where software is not designed to be isolated from its platform, and provides a user interface, that user interface shall follow the values of the user preferences for platform settings for: units of measurement, colour, contrast, font type, font size, and focus cursor except where they are overridden by the user.

NOTE 1: Software that is isolated from its underlying platform has no access to user settings in the platform and thus cannot adhere to them.

NOTE 2: For web content, the underlying platform is the user agent.

NOTE 3: This does not preclude the software from having additional values for a setting as long as there is one mode where the application will follow the system settings even if more restricted.

503.3 Alternative User Interfaces Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.

11.3.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.3.2.1 and 11.3.2.2.

NOTE 2: Assistive technology can also use other documented accessibility services.

Stylistic rewording

Explanatory update

11.5.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

NOTE 2: Assistive technology can also use other documented accessibility services.

Numbering change

11.5.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

NOTE 2: Assistive technology can also use other documented accessibility services.

11.5.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

NOTE 2: Assistive technology can also use other documented accessibility services.

503.4 User Controls for Captions and Audio Description Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

Stylistic rewording

Explanatory update

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

Functional change

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

NOTE 1: Captions may contain information about timing, colour and positioning. This caption data is necessary for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

NOTE 2: If a Braille device is connected, the ICT should provide an option to display captions on the Braille device.

NOTE 3: Clause 7.1.1 refers to the ability of the player to display captions. Clauses 9.1.2.2, 10.1.2.2 and 11.1.2.2 refer to the provision of captions for the content (the video).

Explanatory update
503.4.1 Caption Controls Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

Stylistic rewording

Explanatory update

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

503.4.2 Audio Description Controls Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

Stylistic rewording

Explanatory update

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.

NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

List tables

504 Authoring Tools

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
504.1 General Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.11.6.1 Content technology Authoring tools shall conform to clauses 11.6.2 to 11.6.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.Stylistic rewording

11.8.1 Content technology

Authoring tools shall conform to clauses 11.8.2 to 11.8.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.

Numbering change11.8.1 Content technology Authoring tools shall conform to clauses 11.8.2 to 11.8.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.

11.8.1 Content technology

Authoring tools shall conform to clauses 11.8.2 to 11.8.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.

504.2 Content Creation or Editing Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility.

EXCEPTION: Authoring tools shall not be required to conform to 504.2 when used to directly edit plain text source code.

11.6.2 Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

NOTE: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

Stylistic rewording

Explanatory update

11.8.2 Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

NOTE: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

Numbering change

11.8.2 Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

NOTE: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

11.8.2 Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

NOTE: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format.

11.6.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

Stylistic rewording

Explanatory update

11.8.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

Numbering change

11.8.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

11.8.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

504.3 Prompts Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for supported features and, as applicable, to file formats supported by the authoring tool.

11.6.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web content) or 10 (Documents) as applicable, then the authoring tool shall provide repair suggestion(s).

NOTE: This does not preclude automated and semi-automated repair which is possible (and encouraged) for many types of content accessibility problems.

Stylistic rewording

Explanatory update

Functional change

11.8.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

NOTE: This does not preclude automated and semi-automated repair which is possible (and encouraged) for many types of content accessibility problems.

Numbering change

Stylistic rewording

11.8.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

NOTE: This does not preclude automated and semi-automated repair which is possible (and encouraged) for many types of content accessibility problems.

11.8.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

NOTE: This does not preclude automated and semi-automated repair which is possible (and encouraged) for many types of content accessibility problems.

504.4 Templates Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool.

11.6.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web content) or 10 (Documents) as applicable shall be available and identified as such.

Stylistic rewording

Explanatory update

11.8.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.

Numbering change

Stylistic rewording

11.8.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.

11.8.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.

List tables

Chapter 6: Support Documentation and Services

602 Support Documentation

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
602.2 Accessibility and Compatibility Features Documentation shall list and explain how to use the accessibility and compatibility features required by Chapters 4 and 5. Documentation shall include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

12.1.1 Accessibility and compatibility features

Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

Stylistic rewording

Explanatory update

12.1.1 Accessibility and compatibility features

Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

12.1.1 Accessibility and compatibility features

Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.

NOTE 1: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

NOTE 2: It is best practice to use WebSchemas/Accessibility 2.0 to provide meta data on the accessibility of the ICT.

NOTE 3: The accessibility statement and help pages are both examples of the provision of product information.

Functional change

12.1.1 Accessibility and compatibility features

Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.

NOTE 1: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

NOTE 2: It is best practice to use WebSchemas/Accessibility 2.0 [i.38] to provide meta data on the accessibility of the ICT.

NOTE 3: The accessibility statement and help pages are both examples of the provision of product information.

602.3 Electronic Support Documentation Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9, or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which is accessible.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

Stylistic rewording

Explanatory update

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9, or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which is accessible.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9; or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic, printed or audio) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with limited cognitive, language and learning abilities).

NOTE 3: Where documentation is incorporated into the ICT, the documentation falls under the requirements for accessibility in the present document.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

Functional change

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9; or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic, printed or audio) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with limited cognitive, language and learning abilities).

NOTE 3: Where documentation is incorporated into the ICT, the documentation falls under the requirements for accessibility in the present document.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

602.4 Alternate Formats for Non-Electronic Support Documentation Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9, or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which is accessible.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

Stylistic rewording

Explanatory update

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9, or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic or printed) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).

NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which is accessible.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9; or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic, printed or audio) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with limited cognitive, language and learning abilities).

NOTE 3: Where documentation is incorporated into the ICT, the documentation falls under the requirements for accessibility in the present document.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

Functional change

12.1.2 Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:

  1. a Web format that conforms to the requirements of clause 9; or
  2. a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic, printed or audio) that are not accessible.

NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with limited cognitive, language and learning abilities).

NOTE 3: Where documentation is incorporated into the ICT, the documentation falls under the requirements for accessibility in the present document.

NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

List tables

603 Support Services

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
603.1 General ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.

12.2.1 General (informative)

ICT support services include, but are not limited to: help desks, call centres, technical support, relay services and training services.

Stylistic rewording

12.2.1 General (informative)

ICT support services include, but are not limited to: help desks, call centres, technical support, relay services and training services.

12.2.1 General (informative)

ICT support services include, but are not limited to: help desks, call centres, technical support, relay services and training services.

12.2.1 General (informative)

ICT support services include, but are not limited to: help desks, call centres, technical support, relay services and training services.

603.2 Information on Accessibility and Compatibility Features

ICT support services shall include information on the accessibility and compatibility features required by 602.2.

12.2.2 Information on accessibility and compatibility features

ICT support services shall provide information on the accessibility and compatibility features that are included in the product documentation.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

Stylistic rewording

Explanatory update

12.2.2 Information on accessibility and compatibility features

ICT support services shall provide information on the accessibility and compatibility features that are included in the product documentation.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

12.2.2 Information on accessibility and compatibility features

ICT support services shall provide information on the accessibility and compatibility features that are mentioned in the product documentation.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

12.2.2 Information on accessibility and compatibility features

ICT support services shall provide information on the accessibility and compatibility features that are mentioned in the product documentation.

NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

603.3 Accommodation of Communication Needs

Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities.

12.2.3 Effective communication

ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.

Stylistic rewording

Explanatory update

12.2.3 Effective communication

ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.

12.2.3 Effective communication

ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.

12.2.3 Effective communication

ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.

List tables

Provisions Not Mapped

Revised Section 508

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021

402.3 Volume

ICT that delivers sound, including speech output required by 402.2, shall provide volume control and output amplification conforming to 402.3.

EXCEPTION: ICT conforming to 412.2 shall not be required to conform to 402.3.

407.1 General Where provided, operable parts used in the normal operation of ICT shall conform to 407.
407.2 Contrast Where provided, keys and controls shall contrast visually from background surfaces. Characters and symbols shall contrast visually from background surfaces with either light characters or symbols on a dark background or dark characters or symbols on a light background.

407.3 Input Controls

At least one input control conforming to 407.3 shall be provided for each function.

EXCEPTION: Devices for personal use with input controls that are audibly discernable without activation and operable by touch shall not be required to conform to 407.3.

407.5 Timed Response

Where a timed response is required, the user shall be alerted visually, as well as by touch or sound, and shall be given the opportunity to indicate that more time is needed.33

407.8 Reach Height and Depth At least one of each type of operable part of stationary ICT shall be at a height conforming to 407.8.2 or 407.8.3 according to its position established by the vertical reference plane specified in 407.8.1 for a side reach or a forward reach. Operable parts used with speech output required by 402.2 shall not be the only type of operable part complying with 407.8 unless that part is the only operable part of its type.34
407.8.1 Vertical Reference Plane Operable parts shall be positioned for a side reach or a forward reach determined with respect to a vertical reference plane. The vertical reference plane shall be located in conformance to 407.8.2 or 407.8.3.

407.8.2 Side Reach

Operable parts of ICT providing a side reach shall conform to 407.8.2.1 or 407.8.2.2. The vertical reference plane shall be centered on the operable part and placed at the leading edge of the maximum protrusion of the ICT within the length of the vertical reference plane. Where a side reach requires a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

408.1 General Where provided, display screens shall conform to 408.

408.3 Flashing Where ICT emits lights in flashes, there shall be no more than three flashes in any one-second period.

EXCEPTION: Flashes that do not exceed the general flash and red flash thresholds defined in WCAG 2.0 (incorporated by reference, see 702.10.1) are not required to conform to 408.3. 35

411.1 General Where provided, audible signals or cues shall not be used as the only means of conveying information, indicating an action, or prompting a response.36

412.1 General

ICT that provides two-way voice communication shall conform to 412.

412.2 Volume Gain

ICT that provides two-way voice communication shall conform to 412.2.1 or 412.2.2.

412.3 Interference Reduction and Magnetic Coupling Where ICT delivers output by a handset or other type of audio transducer that is typically held up to the ear, ICT shall reduce interference with hearing technologies and provide a means for effective magnetic wireless coupling in conformance with 412.3.1 or 412.3.2.

412.8 Legacy TTY Support

ICT equipment or systems with two-way voice communication that do not themselves provide TTY functionality shall conform to 412.8.

412.8.1 TTY Connectability

ICT shall include a standard non-acoustic connection point for TTYs.

412.8.2 Voice and Hearing Carry Over

ICT shall provide a microphone capable of being turned on and off to allow the user to intermix speech with TTY use.

412.8.3 Signal Compatibility

ICT shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols where the system interoperates with the Public Switched Telephone Network (PSTN).

412.8.4 Voice Mail and Other Messaging Systems

Where provided, voice mail, auto-attendant, interactive voice response, and caller identification systems shall be usable with a TTY.

413.1 General

Where ICT displays or processes video with synchronized audio, ICT shall provide closed caption processing technology that conforms to 413.1.1 or 413.1.2.

414.1 General Where ICT displays or processes video with synchronized audio, ICT shall provide audio description processing technology conforming to 414.1.1 or 414.1.2.

415.1 General Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 415.1.

EXCEPTION: Devices for personal use shall not be required to conform to 415.1 provided that captions and audio descriptions can be enabled through system-wide platform settings.

502.1 General Software shall interoperate with assistive technology and shall conform to 502.

EXCEPTION: ICT conforming to 402 shall not be required to conform to 502.

502.4 Platform Accessibility Features

Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:

  1. Section 10.6.7 Allow users to choose visual alternative for audio output;37

502.4 Platform Accessibility Features

Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:

  1. Section 10.6.8 Synchronize audio equivalents for visual events;38

502.4 Platform Accessibility Features

Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:

  1. Section 10.6.9 Provide speech output services;39

504.2.2 PDF Export

Authoring tools capable of exporting PDF files that conform to ISO 32000-1:2008 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1) (incorporated by reference, see 702.3.1).40

List tables

EN 301 549

Revised Section 508EN 301 549 V1.1.1 (2014)508 to 2014EN 301 549 V2.1.2 (2018)2014 to 2018EN 301 549 V3.1.1 (2019)2018 to 2019EN 301 549 V3.2.1 (2021)2019 to 2021
­­­

4.2.11 Privacy

Where ICT provides features that are provided for accessibility, some users will need their privacy to be maintained when using those ICT features that are provided for accessibility. NOTE: Enabling the connection of personal headsets for private listening, not providing a spoken version of characters being masked and enabling user control of legal, financial and personal data are examples of design features that may contribute towards meeting this clause.

4.2.11 Privacy

Where ICT provides features that are provided for accessibility, some users will need their privacy to be maintained when using those ICT features that are provided for accessibility. NOTE: Enabling the connection of personal headsets for private listening, not providing a spoken version of characters being masked and enabling user control of legal, financial and personal data are examples of design features that may contribute towards meeting this clause.

4.2.11 Privacy

Where ICT provides features for accessibility, the ICT maintains the privacy of users of these features at the same level as other users.

NOTE: Enabling the connection of personal headsets for private listening, not providing a spoken version of characters being masked and enabling user control of legal, financial and personal data are examples of design features that may contribute towards meeting this clause.

4.2.11 Privacy

Where ICT provides features for accessibility, the ICT maintains the privacy of users of these features at the same level as other users.

NOTE: Enabling the connection of personal headsets for private listening, not providing a spoken version of characters being masked and enabling user control of legal, financial and personal data are examples of design features that may contribute towards meeting this clause.

4.2.9 Minimize photosensitive seizure triggers

Where ICT provides visual modes of operation, some users need ICT to provide at least one mode of operation that minimizes the potential for triggering photosensitive seizures.

NOTE: Limiting the area and number of flashes per second may contribute towards meeting this clause.

4.2.9 Minimize photosensitive seizure triggers

Where ICT provides visual modes of operation, some users need ICT to provide at least one mode of operation that minimizes the potential for triggering photosensitive seizures.

NOTE: Limiting the area and number of flashes per second may contribute towards meeting this clause.

4.2.9 Minimize photosensitive seizure triggers

Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that minimizes the potential for triggering photosensitive seizures. This is essential for users with photosensitive seizure triggers.

NOTE: Limiting the area and number of flashes per second may contribute towards meeting this clause.

4.2.9 Minimize photosensitive seizure triggers

Where ICT provides visual modes of operation, the ICT provides at least one mode of operation that minimizes the potential for triggering photosensitive seizures. This is essential for users with photosensitive seizure triggers.

NOTE: Limiting the area and number of flashes per second may contribute towards meeting this clause.

5.1.2.1 Closed functionality

Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.

NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to the requirements of clause 5.1.

NOTE 2: The requirements within this clause replace those in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. This may be because they relate to compatibility with assistive technology or to the ability for the user to adjust system accessibility settings in products with closed functionality (e.g. products that prevent access to the system settings control panel).

5.1.2.1 Closed functionality

Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.

NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to the requirements of clause 5.1.

NOTE 2: The requirements within this clause replace those in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. This may be because they relate to compatibility with assistive technology or to the ability for the user to adjust system accessibility settings in products with closed functionality (e.g. products that prevent access to the system settings control panel).

5.1.2.1 Closed functionality

Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.

NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to the requirements of clause 5.1.

NOTE 2: The requirements within this clause replace those in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. This may be because they relate to compatibility with assistive technology or to the ability for the user to adjust system accessibility settings in products with closed functionality (e.g. products that prevent access to the system settings control panel).

5.1.2.1 Closed functionality

Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.

NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to the requirements of clause 5.1.

NOTE 2: The requirements within this clause replace those in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. This may be because they relate to compatibility with assistive technology or to the ability for the user to adjust system accessibility settings in products with closed functionality (e.g. products that prevent access to the system settings control panel).

5.1.3.10 Non-interfering audio output

Where auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.

5.1.3.10 Non-interfering audio output

Where auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.

5.1.3.10 Non-interfering audio output

Where auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.

5.1.3.10 Non-interfering audio output

Where auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.

5.1.3.14 Spoken languages

Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:

  1. for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text;
  2. where the content is generated externally and not under the control of the ICT vendor, clause 5.1.3.14 shall not be required to apply for languages not supported by the ICT's speech synthesizer;
  3. for displayed languages that cannot be selected using non-visual access;
  4. where the user explicitly selects a speech language that is different from the language of the displayed content.

5.1.3.14 Spoken languages

Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:

  1. for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text;
  2. where the content is generated externally and not under the control of the ICT vendor, clause 5.1.3.14 shall not be required to apply for languages not supported by the ICT's speech synthesizer;
  3. for displayed languages that cannot be selected using non-visual access;
  4. where the user explicitly selects a speech language that is different from the language of the displayed content.

5.1.3.14 Spoken languages

Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:

  1. for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text;
  2. where the content is generated externally and not under the control of the ICT vendor, the present clause shall not be required to apply for languages not supported by the ICT's speech synthesizer;
  3. for displayed languages that cannot be selected using non-visual access;
  4. where the user explicitly selects a speech language that is different from the language of the displayed content.
Stylistic rewording

5.1.3.14 Spoken languages

Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:

  1. for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text;
  2. where the content is generated externally and not under the control of the ICT vendor, the present clause shall not be required to apply for languages not supported by the ICT's speech synthesizer;
  3. for displayed languages that cannot be selected using non-visual access;
  4. where the user explicitly selects a speech language that is different from the language of the displayed content.

5.1.3.15 Non-visual error identification

Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.

5.1.3.15 Non-visual error identification

Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.

5.1.3.15 Non-visual error identification

Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.

5.1.3.15 Non-visual error identification

Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.

5.1.5 Visual output for auditory information

Where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the pre-recorded auditory output.

NOTE: This visual information can take the form of captions or text transcripts.

5.1.5 Visual output for auditory information

Where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the pre-recorded auditory output.

NOTE: This visual information can take the form of captions or text transcripts.

5.1.5 Visual output for auditory information

Where auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the auditory output.

NOTE: This visual information can take the form of captions or text transcripts.

Stylistic rewording

5.1.5 Visual output for auditory information

Where auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the auditory output.

NOTE: This visual information can take the form of captions or text transcripts.

5.1.6.1 Closed functionality

Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.

5.1.6.1 Closed functionality

Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.

5.1.6.1 Closed functionality

Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.

5.1.6.1 Closed functionality

Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.

5.1.6.2 Input focus

Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.

5.1.6.2 Input focus

Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.

5.1.6.2 Input focus

Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.

5.1.6.2 Input focus

Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.

5.1.7 Access without speech

Where speech is needed to operate closed functions of ICT, the ICT shall provide at least one mode of operation using an alternative input mechanism that does not require speech.

New requirement

5.1.7 Access without speech

Where speech is needed to operate closed functions of ICT, the ICT shall provide at least one mode of operation using an alternative input mechanism that does not require speech.

6.2.1.1 RTT communication

Where ICT supports two-way voice communication in a specified context of use, the ICT shall allow a user to communicate with another user by RTT.

NOTE 1: The RTT capability can be provided as a factory default or added later.

NOTE 2: Provision of RTT may require additional service provision, additional hardware and/or software which may be provided separately or together.

6.2.1.1 RTT communication

Where ICT supports two-way voice communication in a specified context of use, the ICT shall allow a user to communicate with another user by RTT.

NOTE 1: The RTT capability can be provided as a factory default or added later.

NOTE 2: Provision of RTT may require additional service provision, additional hardware and/or software which may be provided separately or together.

6.2.1.1 RTT communication

Where ICT is in a mode that provides a means for two-way voice communication, the ICT shall provide a means for two-way RTT communication, except where this would require design changes to add input or output hardware to the ICT.

NOTE 1: This requirement includes those products which do not have physical display or text entry capabilities but have the capability to connect to devices that do have such capabilities. It also includes intermediate ICT between the endpoints of the communication.

NOTE 2: There is no requirement to add: a hardware display, a hardware keyboard, or hardware to support the ability to connect to a display or keyboard, wired or wirelessly, if this hardware would not normally be provided.

NOTE 3: For the purposes of interoperability, support of Recommendation ITU-T T.140 is widely used.

Stylistic rewording

Functional change

Explanatory update

6.2.1.1 RTT communication

Where ICT is in a mode that provides a means for two-way voice communication, the ICT shall provide a means for two-way RTT communication, except where this would require design changes to add input or output hardware to the ICT.

NOTE 1: This requirement includes those products which do not have physical display or text entry capabilities but have the capability to connect to devices that do have such capabilities. It also includes intermediate ICT between the endpoints of the communication.

NOTE 2: There is no requirement to add: a hardware display, a hardware keyboard, or hardware to support the ability to connect to a display or keyboard, wired or wirelessly, if this hardware would not normally be provided.

NOTE 3: For the purposes of interoperability, support of Recommendation ITU-T T.140 is widely used.

6.2.1.2 Concurrent voice and text

Where ICT supports two-way voice communication in a specified context of use, and enables a user to communicate with another user by RTT, it shall provide a mechanism to select a mode of operation which allows concurrent voice and text.

NOTE: The availability of voice and RTT running concurrently can allow the RTT to replace or support voice and transfer additional information such as numbers, currency amounts and spelling of names.

6.2.1.2 Concurrent voice and text

Where ICT supports two-way voice communication in a specified context of use, and enables a user to communicate with another user by RTT, it shall provide a mechanism to select a mode of operation which allows concurrent voice and text.

NOTE: The availability of voice and RTT running concurrently can allow the RTT to replace or support voice and transfer additional information such as numbers, currency amounts and spelling of names.

6.2.1.2 Concurrent voice and text

Where ICT provides a means for two-way voice communication and for users to communicate by RTT, it shall allow concurrent voice and text through a single user connection.

NOTE 1: With many-party communication, as in a conference system, it is allowed (but not required or necessarily recommended) that RTT be handled in a single display field and that "turn-taking" be necessary to avoid confusion (in the same way that turn-taking is required for those presenting/talking with voice).

NOTE 2: With many-party communication, best practice is for hand-raising for voice users and RTT users to be handled in the same way, so that voice and RTT users are in the same queue.

NOTE 3: With a many-party conference system that has chat as one of its features - the RTT (like the voice) would typically be separate from the chat so that RTT use does not interfere with chat (i.e. people can be messaging in the chat field while the person is presenting/talking with RTT - in the same manner that people message using the chat feature while people are talking with voice). RTT users would then use RTT for presenting and use the Chat feature to message while others are presenting (via Voice or RTT).

NOTE 4: The availability of voice and RTT running concurrently (and separately from chat) can also allow the RTT field to support text captioning when someone is speaking (and it is therefore not being used for RTT since it is not the RTT user's turn to speak).

NOTE 5: Where both server-side software and local hardware and software are required to provide voice communication, where neither part can support voice communication without the other and are sold as a unit for the voice communication function, the local and server-side components are considered a single product.

Stylistic rewording

Functional change

Explanatory update

6.2.1.2 Concurrent voice and text

Where ICT provides a means for two-way voice communication and for users to communicate by RTT, it shall allow concurrent voice and text through a single user connection.

NOTE 1: With many-party communication, as in a conference system, it is allowed (but not required or necessarily recommended) that RTT be handled in a single display field and that "turn-taking" be necessary to avoid confusion (in the same way that turn-taking is required for those presenting/talking with voice).

NOTE 2: With many-party communication, best practice is for hand-raising for voice users and RTT users to be handled in the same way, so that voice and RTT users are in the same queue.

NOTE 3: With a many-party conference system that has chat as one of its features - the RTT (like the voice) would typically be separate from the chat so that RTT use does not interfere with chat (i.e. people can be messaging in the chat field while the person is presenting/talking with RTT - in the same manner that people message using the chat feature while people are talking with voice). RTT users would then use RTT for presenting and use the Chat feature to message while others are presenting (via Voice or RTT).

NOTE 4: The availability of voice and RTT running concurrently (and separately from chat) can also allow the RTT field to support text captioning when someone is speaking (and it is therefore not being used for RTT since it is not the RTT user's turn to speak).

NOTE 5: Where both server-side software and local hardware and software are required to provide voice communication, where neither part can support voice communication without the other and are sold as a unit for the voice communication function, the local and server-side components are considered a single product.

6.2.2.1 Visually distinguishable display

Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from and separated from received text.

6.2.2.1 Visually distinguishable display

Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from and separated from received text.

6.2.2.1 Visually distinguishable display

Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from, and separated from, received text.

NOTE: The ability of the user to choose between having the send and receive text be displayed in-line or separately, and with options to select, allows users to display RTT in a form that works best for them. This would allow Braille users to use a single field and take turns and have text appear in the sequential way that they may need or prefer.

Explanatory update

6.2.2.1 Visually distinguishable display

Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from, and separated from, received text.

NOTE: The ability of the user to choose between having the send and receive text be displayed in-line or separately, and with options to select, allows users to display RTT in a form that works best for them. This would allow Braille users to use a single field and take turns and have text appear in the sequential way that they may need or prefer.

6.2.2.2 Programmatically determinable send and receive direction

Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted text shall be programmatically determinable, unless the RTT has closed functionality.

NOTE: The intent of clause 6.2.2.2 is to enable screen readers to be able to distinguish between incoming text and outgoing text when used with RTT functionality.

6.2.2.2 Programmatically determinable send and receive direction

Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted text shall be programmatically determinable, unless the RTT has closed functionality.

NOTE: The intent of this clause is to enable screen readers to be able to distinguish between incoming text and outgoing text when used with RTT functionality.

Stylistic rewording

6.2.2.2 Programmatically determinable send and receive direction

Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted/received text shall be programmatically determinable, unless the RTT is implemented as closed functionality.

NOTE: This enables screen readers to distinguish between incoming text and outgoing text when used with RTT functionality.

Functional change

Stylistic rewording

6.2.2.2 Programmatically determinable send and receive direction

Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted/received text shall be programmatically determinable, unless the RTT is implemented as closed functionality.

NOTE: This enables screen readers to distinguish between incoming text and outgoing text when used with RTT functionality.

6.2.2.3 Speaker identification

Where ICT has RTT capabilities, and provides speaker identification for voice, the ICT shall provide speaker identification for RTT.

NOTE: This is necessary to enable both voice and RTT participants to know who is currently communicating, whether it be in RTT or voice.

New requirement

6.2.2.3 Speaker identification

Where ICT has RTT capabilities, and provides speaker identification for voice, the ICT shall provide speaker identification for RTT.

NOTE: This is necessary to enable both voice and RTT participants to know who is currently communicating, whether it be in RTT or voice.

6.2.2.4 Visual indicator of Audio with RTT

Where ICT provides two-way voice communication, and has RTT capabilities, the ICT shall provide a real-time visual indicator of audio activity on the display.

NOTE 1: The visual indicator may be a simple character position on the display that flickers on and off to reflect audio activity, or presentation of the information in another way that can be both visible to sighted users and passed on to deaf-blind users who are using a braille display.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

New requirement

6.2.2.4 Visual indicator of Audio with RTT

Where ICT provides two-way voice communication, and has RTT capabilities, the ICT shall provide a real-time visual indicator of audio activity on the display.

NOTE 1: The visual indicator may be a simple character position on the display that flickers on and off to reflect audio activity, or presentation of the information in another way that can be both visible to sighted users and passed on to deaf-blind users who are using a braille display.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

6.2.3 Interoperability

Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by 6.2.1.1) they shall support at least one of the four RTT interoperability mechanisms described below:

  1. ICT interoperating over the Public Switched Telephone Network (PSTN), with other ICT that directly connects to the PSTN as described in Recommendation ITU-T V.18 or any of its annexes for text telephony signals at the PSTN interface;
  2. ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using real-time text that conforms to RFC 4103;
  3. ICT interoperating with other ICT using RTT that conforms with the IP Multimedia Sub-System (IMS) set of protocols specified in TS 126 114, TS 122 173 and TS 134 229;
  4. ICT interoperating with other ICT using a relevant and applicable common specification for RTT exchange that is published and available. This common specification shall include a method for indicating loss or corruption of characters.

6.2.3 Interoperability

Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by clause 6.2.1.1) they shall support at least one of the four RTT interoperability mechanisms described below:

  1. ICT interoperating over the Public Switched Telephone Network (PSTN), with other ICT that directly connects to the PSTN as described in Recommendation ITU-T V.18 or any of its annexes for text telephony signals at the PSTN interface;
  2. ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using real-time text that conforms to IETF RFC 4103;
  3. ICT interoperating with other ICT using RTT that conforms with the IP Multimedia Sub-System (IMS) set of protocols specified in ETSI TS 126 114, ETSI TS 122 173 and ETSI TS 134 229;
  4. ICT interoperating with other ICT using a relevant and applicable common specification for RTT exchange that is published and available. This common specification shall include a method for indicating loss or corruption of characters.

Stylistic rewording

Explanatory update

6.2.3 Interoperability

Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by clause 6.2.1.1) they shall support the applicable RTT interoperability mechanisms described below:

  1. ICT interoperating with other ICT directly connected to the Public Switched Telephone Network (PSTN), using Recommendation ITU-T V.18 or any of its annexes for text telephony signals at the PSTN interface;
  2. ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using RTT that conforms to IETF RFC 4103. For ICT interoperating with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, the set of protocols specified in ETSI TS 126 114, ETSI TS 122 173 and ETSI TS 134 229 describe how IETF RFC 4103 would apply;
  3. ICT interoperating with other ICT using technologies other than a or b, above, using a relevant and applicable common specification for RTT exchange that is published and available for the environments in which they will be operating. This common specification shall include a method for indicating loss or corruption of characters.
  4. ICT interoperating with other ICT using a standard for RTT that has been introduced for use in any of the above environments, and is supported by all of the other active ICT that support voice and RTT in that environment.

NOTE 1: In practice, new standards are introduced as an alternative codec/protocol that is supported alongside the existing common standard and used when all end-to-end components support it while technology development, combined with other reasons including societal development and cost efficiency, may make others become obsolete.

NOTE 2: Where multiple technologies are used to provide voice communication, multiple interoperability mechanisms may be needed to ensure that all users are able to use RTT.

EXAMPLE: A conferencing system that supports voice communication through an internet connection might provide RTT over an internet connection using a proprietary RTT method (option c). However, regardless of whether the RTT method is proprietary or non-proprietary, if the conferencing system also offers telephony communication it will also need to support options a or b to ensure that RTT is supported over the telephony connection.

Stylistic rewording

Explanatory update

Functional change

6.2.3 Interoperability

Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by clause 6.2.1.1) they shall support the applicable RTT interoperability mechanisms described below:

  1. ICT interoperating with other ICT directly connected to the Public Switched Telephone Network (PSTN), using Recommendation ITU-T V.18 [i.23] or any of its annexes for text telephony signals at the PSTN interface;
  2. ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using RTT that conforms to IETF RFC 4103 [i.13]. For ICT interoperating with other ICT using the IP Multimedia Sub-System (IMS) to implement VOIP, the set of protocols specified in ETSI TS 126 114 [i.10], ETSI TS 122 173 [i.11] and ETSI TS 134 229 [i.12] describe how IETF RFC 4103 [i.13] would apply;
  3. ICT interoperating with other ICT using technologies other than a or b, above, using a relevant and applicable common specification for RTT exchange that is published and available for the environments in which they will be operating. This common specification shall include a method for indicating loss or corruption of characters;
  4. ICT interoperating with other ICT using a standard for RTT that has been introduced for use in any of the above environments, and is supported by all of the other active ICT that support voice and RTT in that environment.

NOTE 1: In practice, new standards are introduced as an alternative codec/protocol that is supported alongside the existing common standard and used when all end-to-end components support it while technology development, combined with other reasons including societal development and cost efficiency, may make others become obsolete.

NOTE 2: Where multiple technologies are used to provide voice communication, multiple interoperability mechanisms may be needed to ensure that all users are able to use RTT.

EXAMPLE: A conferencing system that supports voice communication through an internet connection might provide RTT over an internet connection using a proprietary RTT method (option c). However, regardless of whether the RTT method is proprietary or non-proprietary, if the conferencing system also offers telephony communication it will also need to support options a or b to ensure that RTT is supported over the telephony connection.

6.2.4 Real-time responsiveness

Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network supporting RTT within 1 second of the input entry.

NOTE 1: Input entry is considered to have occurred when sufficient user input has occurred for the ICT to establish which character(s) to send.

NOTE 2: Input entry will differ between systems where text is entered on a word-by-word basis (e.g. speech-to-text and predictive-text based systems) and systems where each character is separately generated.

6.2.4 Real-time text responsiveness

Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network supporting RTT within 1 second of the input entry.

NOTE 1: Input entry is considered to have occurred when sufficient user input has occurred for the ICT to establish which character(s) to send.

NOTE 2: Input entry will differ between systems where text is entered on a word-by-word basis (e.g. speech-to-text and predictive-text based systems) and systems where each character is separately generated.

6.2.4 RTT responsiveness

Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network or platform on which the ICT runs within 500 ms of the time that the smallest reliably composed unit of text entry is available to the ICT for transmission. Delays due to platform or network performance shall not be included in the 500 ms limit.

NOTE 1: For character by character input, the "smallest reliably composed unit of text entry" would be a character.

For word prediction it would be a word. For some voice recognition systems - the text may not exit the recognition software until an entire word (or phrase) has been spoken. In this case, the smallest reliably composed unit of text entry available to the ICT would be the word (or phrase).

NOTE 2: The 500 ms limit allows buffering of characters for this period before transmission so character by character transmission is not required unless the characters are generated more slowly than 1 per 500 ms.

NOTE 3: A delay of 300 ms, or less, produces a better impression of flow to the user.

Stylistic rewording

Functional change

Explanatory update

6.2.4 RTT responsiveness

Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network or platform on which the ICT runs within 500 ms of the time that the smallest reliably composed unit of text entry is available to the ICT for transmission. Delays due to platform or network performance shall not be included in the 500 ms limit.

NOTE 1: For character by character input, the "smallest reliably composed unit of text entry" would be a character. For word prediction it would be a word. For some voice recognition systems - the text may not exit the recognition software until an entire word (or phrase) has been spoken. In this case, the smallest reliably composed unit of text entry available to the ICT would be the word (or phrase).

NOTE 2: The 500 ms limit allows buffering of characters for this period before transmission so character by character transmission is not required unless the characters are generated more slowly than 1 per 500 ms.

NOTE 3: A delay of 300 ms, or less, produces a better impression of flow to the user.

6.4 Alternatives to voice-based services

Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT should offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.

NOTE: Solutions capable of handling audio, real-time text and video media could satisfy the above requirement.

6.4 Alternatives to voice-based services

Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT should offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.

NOTE: Solutions capable of handling audio, real-time text and video media could satisfy the above requirement.

6.4 Alternatives to voice-based services

Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT shall offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.

NOTE 1: Tasks that involve both operating the interface and perceiving the information would require that both the interface and information be accessible without use of speech or hearing.

NOTE 2: Solutions capable of handling audio, RTT and video media could satisfy the above requirement.

Functional change

Explanatory update

Stylistic rewording

6.4 Alternatives to voice-based services

Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT shall offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.

NOTE 1: Tasks that involve both operating the interface and perceiving the information would require that both the interface and information be accessible without use of speech or hearing.

NOTE 2: Solutions capable of handling audio, RTT and video media could satisfy the above requirement.

6.5.5 Visual indicator of audio with video

Where ICT provides two-way voice communication, and includes real-time video functionality, the ICT shall provide a real-time visual indicator of audio activity.

NOTE 1: The visual indicator may be a simple visual dot or LED, or other type of on/off indicator, that flickers to reflect audio activity.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

New requirement

6.5.5 Visual indicator of audio with video

Where ICT provides two-way voice communication, and includes real-time video functionality, the ICT shall provide a real-time visual indicator of audio activity.

NOTE 1: The visual indicator may be a simple visual dot or LED, or other type of on/off indicator, that flickers to reflect audio activity.

NOTE 2: Without this indication a person who lacks the ability to hear does not know when someone is talking.

6.5.6 Speaker identification with video (sign language) communication

Where ICT provides speaker identification for voice users, it shall provide a means for speaker identification for real-time signing and sign language users once the start of signing has been indicated.

NOTE 1: The speaker ID can be in the same location as for voice users for multiparty calls.

NOTE 2: This mechanism might be triggered manually by a user, or automatically where this is technically achievable.

New requirement

6.5.6 Speaker identification with video (sign language) communication

Where ICT provides speaker identification for voice users, it shall provide a means for speaker identification for real-time signing and sign language users once the start of signing has been indicated.

NOTE 1: The speaker ID can be in the same location as for voice users for multiparty calls.

NOTE 2: This mechanism might be triggered manually by a user, or automatically where this is technically achievable.

6.6 Alternatives to video-based services

Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:

  1. for audible information, without the use of hearing;
  2. for spoken commands, without the use of speech;
  3. for visual information, without the use of vision.

NOTE: Solutions capable of generating real-time captions or handling real-time text could satisfy the above requirement.

6.6 Alternatives to video-based services

Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:

  1. for audible information, without the use of hearing;
  2. for spoken commands, without the use of speech;
  3. for visual information, without the use of vision.

NOTE: Solutions capable of generating real-time captions or handling real-time text could satisfy the above requirement.

6.6 Alternatives to video-based services

Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:

  1. for audible information, without the use of hearing;
  2. for spoken commands, without the use of speech;
  3. for visual information, without the use of vision.

NOTE: Solutions capable of generating real-time captions or handling RTT could satisfy the above requirement.

Stylistic rewording

6.6 Alternatives to video-based services

Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:

  1. for audible information, without the use of hearing;
  2. for spoken commands, without the use of speech;
  3. for visual information, without the use of vision.

NOTE: Solutions capable of generating real-time captions or handling RTT could satisfy the above requirement.

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions.

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions.

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions as follows:

  • Captions in recorded material: within 100 ms of the time stamp of the caption
  • Live captions: within 100 ms of the availability of the caption to the player.
Functional change

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions as follows:

  • Captions in recorded material: within 100 ms of the time stamp of the caption.
  • Live captions: within 100 ms of the availability of the caption to the player.

7.1.4 Captions characteristics

Where ICT displays captions, it shall provide a way for the user to adapt the displayed characteristics of captions to their individual requirements, except where the captions are displayed as unmodifiable characters.

NOTE 1: Defining the background and foreground colour of subtitles, font type, size opacity of the background box of subtitles, and the contour or border of the fonts can contribute to meeting this requirement.

NOTE 2: Subtitles that are bitmap images are examples of unmodifiable characters.

New requirement

7.1.4 Captions characteristics

Where ICT displays captions, it shall provide a way for the user to adapt the displayed characteristics of captions to their individual requirements, except where the captions are displayed as unmodifiable characters.

NOTE 1: Defining the background and foreground colour of subtitles, font type, size opacity of the background box of subtitles, and the contour or border of the fonts can contribute to meeting this requirement.

NOTE 2: Subtitles that are bitmap images are examples of unmodifiable characters.

7.1.5 Spoken subtitles

Where ICT displays video with synchronized audio, it shall have a mode of operation to provide a spoken output of the available captions, except where the content of the displayed captions is not programmatically determinable.

NOTE 1: Being able to manage speech output range for spoken subtitles independently from general ICT speech is preferable for most users. That is possible when the audio file with spoken subtitle is delivered in a separate audio track and mixed in the end users device.

NOTE 2: Presenting the separate audio track with spoken subtitles in synchronization with the displayed subtitles/captions improves understandability of the subtitles.

NOTE 3: Providing subtitles/captions as separate text-streams, facilitates converting the respective texts into audio.

NOTE 4: Subtitles that are bitmap images are examples where the content of the displayed captions will not be programmatically determinable.

New requirement

7.1.5 Spoken subtitles

Where ICT displays video with synchronized audio, it shall have a mode of operation to provide a spoken output of the available captions, except where the content of the displayed captions is not programmatically determinable.

NOTE 1: Being able to manage speech output range for spoken subtitles independently from general ICT speech is preferable for most users. That is possible when the audio file with spoken subtitle is delivered in a separate audio track and mixed in the end users device. NOTE 2: Presenting the separate audio track with spoken subtitles in synchronization with the displayed subtitles/captions improves understandability of the subtitles.

NOTE 3: Providing subtitles/captions as separate text-streams, facilitates converting the respective texts into audio.

NOTE 4: Subtitles that are bitmap images are examples where the content of the displayed captions will not be programmatically determinable.

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.

NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.

NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.

NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.

NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.

NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.

NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.

NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.

NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

8.3.0 General

The present document defines the dimensions for accessing stationary ICT that can be placed in a built environment, but does not define the dimensions of the built environment in general.

The scope includes stationary ICT, of which floors and circulation spaces are "an integral part" (typically kiosks and cabins), and where there are external reach ranges relevant for operating the stationary ICT.

Clauses 8.3.2 to 8.3.4 specify mandatory limits for the maximum and minimum height of operable parts and displays.

Based on dimensions shown in figure 53 of ISO 21542:2011, it is recommended that the possible height range is reduced to:

  • minimum and maximum heights of operable parts: 800 mm and 1 100 mm respectively, and
  • minimum and maximum heights of displays: 1 200 mm and 1 400 mm respectively.
New requirement

8.3.0 General

The present document defines the dimensions for accessing stationary ICT that can be placed in a built environment, but does not define the dimensions of the built environment in general.

The scope includes stationary ICT, of which floors and circulation spaces are "an integral part" (typically kiosks and cabins), and where there are external reach ranges relevant for operating the stationary ICT.

Clauses 8.3.2 to 8.3.4 specify mandatory limits for the maximum and minimum height of operable parts and displays. Based on dimensions shown in Figure 53 of ISO 21542:2011, it is recommended that the possible height range is reduced to:

  • minimum and maximum heights of operable parts: 800 mm and 1 100 mm respectively, and
  • minimum and maximum heights of displays: 1 200 mm and 1 400 mm respectively.

8.3.2.1 Change in level

Where there is a change in floor level that is integral to the ICT then it should be ramped with a slope no steeper than 1:48.

Exceptions:

  1. If the change in floor level is less than or equal to 6,4 mm (¼ inch) the change may be vertical.
  2. If the change in floor level is less than or equal to 13 mm (½ inch) the change may have a slope not steeper than 1:2.

8.3.2.1 Change in level

Where there is a change in floor level that is integral to the ICT then it should be ramped with a slope no steeper than 1:48.

Exceptions:

  1. If the change in floor level is less than or equal to 6,4 mm (¼ inch) the change may be vertical.
  2. If the change in floor level is less than or equal to 13 mm (½ inch) the change may have a slope not steeper than 1:2.

8.3.4.1 Change in level

Where stationary ICT has a floor within it, then any change of floor level within it or entering it shall be ramped with a slope no steeper than 1:48.

Exceptions:

  1. If the change in floor level is less than or equal to 6,4 mm (¼ inch) the change may be vertical.
  2. If the change in floor level is less than or equal to 13 mm (½ inch) the change may have a slope not steeper than 1:2.

Numbering change

Stylistic rewording

Functional change

8.3.4.1 Change in level

Where stationary ICT has a floor within it, then any change of floor level within it or entering it shall be ramped with a

slope no steeper than 1:48.

Exceptions:

  1. If the change in floor level is less than or equal to 6,4 mm (¼ inch) the change may be vertical as shown in Figure 8.
  2. If the change in floor level is less than or equal to 13 mm (½ inch) the change may have a slope not steeper than 1:2.

8.3.2.3.1 General

Where the access space is integral to the ICT, at least one full side of the space should be unobstructed.

8.3.2.3.1 General

Where the access space is integral to the ICT, at least one full side of the space should be unobstructed.

8.3.4.3.1 General

Where stationary ICT has an access space inside it, at least one full side of the space shall be unobstructed.

Numbering change

Stylistic rewording

Functional change

8.3.4.3.1 General

Where stationary ICT has an access space inside it, at least one full side of the space shall be unobstructed.

8.3.2.3.2 Forward approach

Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space should be a minimum of 915 mm (36 inches) wide.

8.3.2.3.2 Forward approach

Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space should be a minimum of 915 mm (36 inches) wide.

8.3.4.3.2 Forward approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space shall be a minimum of 915 mm (36 inches) wide.

Numbering change

Stylistic rewording

Functional change

8.3.4.3.2 Forward approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space shall be a minimum of 915 mm (36 inches) wide.

8.3.2.3.3 Parallel approach

Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space should be a minimum of 1 525 mm (60 inches) wide.

8.3.2.3.3 Parallel approach

Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space should be a minimum of 1 525 mm (60 inches) wide.

8.3.4.3.3 Parallel approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space shall be a minimum of 1 525 mm (60 inches) wide.

Numbering change

Stylistic rewording

Functional change

8.3.4.3.3 Parallel approach

Where the operating area is inside an alcove within the stationary ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space shall be a minimum of 1 525 mm (60 inches) wide.

8.3.5 Installation instructions

Where an ICT is intended to be installed, instructions should be made available which outline a method to install the ICT in a manner that ensures that the dimensions of the integral spaces of the ICT conform to clauses 8.3.2 to 8.3.4.

8.3.5 Installation instructions

Where an ICT is intended to be installed, instructions should be made available which outline a method to install the ICT in a manner that ensures that the dimensions of the integral spaces of the ICT conform to clauses 8.3.2 to 8.3.4.

8.3.6 Installation instructions

Installation instructions shall be made available for all stationary ICT. These instructions shall give guidance on how to install the ICT in a manner that takes into account applicable requirements for accessibility of the built environment as they apply to the installation of the ICT. Where there are no such requirements the instructions should require that the dimensions of the installed ICT conform to clauses 8.3.2 to 8.3.5 of the present document.

Numbering change

Stylistic rewording

Explanatory update

Functional change

8.3.6 Installation instructions

Installation instructions shall be made available for all stationary ICT. These instructions shall give guidance on how to install the ICT in a manner that takes into account applicable requirements for accessibility of the built environment as they apply to the installation of the ICT. Where there are no such requirements the instructions should require that the dimensions of the installed ICT conform to clauses 8.3.2 to 8.3.5 of the present document.

9.1.3.4 Orientation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.4 Orientation.

New requirement

9.1.3.4 Orientation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.4 Orientation.

9.1.3.4 Orientation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.4 Orientation.

9.1.3.5 Identify input purpose

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

New requirement

9.1.3.5 Identify input purpose

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

9.1.3.5 Identify input purpose

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

9.1.4.10 Reflow

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.10 Reflow.

New requirement

9.1.4.10 Reflow

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.10 Reflow.

9.1.4.10 Reflow

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.10 Reflow.

9.1.4.11 Non-text contrast

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

New requirement

9.1.4.11 Non-text contrast

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

9.1.4.11 Non-text contrast

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

9.1.4.12 Text spacing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

New requirement

9.1.4.12 Text spacing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

9.1.4.12 Text spacing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

9.1.4.13 Content on hover or focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

New requirement

9.1.4.13 Content on hover or focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

9.1.4.13 Content on hover or focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

9.2.1.4 Character key shortcuts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

New requirement

9.2.1.4 Character key shortcuts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

9.2.1.4 Character key shortcuts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

9.2.5.1 Pointer gestures

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

New requirement

9.2.5.1 Pointer gestures

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

9.2.5.1 Pointer gestures

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

9.2.5.2 Pointer cancellation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

New requirement

9.2.5.2 Pointer cancellation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

9.2.5.2 Pointer cancellation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

9.2.5.3 Label in name

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

New requirement

9.2.5.3 Label in name

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

9.2.5.3 Label in name

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

9.2.5.4 Motion actuation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

New requirement

9.2.5.4 Motion actuation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

9.2.5.4 Motion actuation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

9.4.1.3 Status messages

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

New requirement

9.4.1.3 Status messages

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

9.4.1.3 Status messages

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

9.5 WCAG 2.1 AAA Success Criteria

In addition to the Level AA success criteria, included in clauses 9.1 to 9.4, the Web Content Accessibility Guidelines include success criteria for Level AAA. These are listed in Table 9.1. Web authors and procurement accessibility specialists are encouraged to consider the WCAG 2.1 Level AAA success criteria that, when it is possible to apply them, may provide access beyond that required in the present document.

NOTE: The W3C states that "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content".

New requirement

9.5 WCAG 2.1 AAA Success Criteria

In addition to the Level AA success criteria, included in clauses 9.1 to 9.4, the Web Content Accessibility Guidelines include success criteria for Level AAA. These are listed in Table 9.1. Web authors and procurement accessibility specialists are encouraged to consider the WCAG 2.1 Level AAA success criteria that, when it is possible to apply them, may provide access beyond that required in the present document.

NOTE: The W3C states that "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content".

10.2.7 Info and relationships

Where ICT is a non-web document, it shall satisfy the success criterion.

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.1 Info and Relationships.

10.1.3.1 Info and relationships

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

Numbering change

10.1.3.1 Info and relationships

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

NOTE: Where documents contain non-standard structure types (roles), it is best practice to map them to a standard structure type as a fall-back solution for the reader.

Explanatory update

10.1.3.1 Info and relationships

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

NOTE: Where documents contain non-standard structure types (roles), it is best practice to map them to a standard structure type as a fall-back solution for the reader.

10.1.3.4 Orientation

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

New requirement

10.1.3.4 Orientation

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

10.1.3.4 Orientation

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

10.1.3.5 Identify input purpose

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

New requirement

10.1.3.5 Identify input purpose

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

10.1.3.5 Identify input purpose

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

10.1.4.10 Reflow

Where ICT is a non-web document, it shall satisfy the following success criterion.

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 1280 CSS pixels wide at 400% zoom. For documents which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024px 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.

New requirement

10.1.4.10 Reflow

Where ICT is a non-web document, it shall satisfy the following success criterion.

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 documents 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 pixels 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.

10.1.4.10 Reflow

Where ICT is a non-web document, it shall satisfy the success criterion 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 documents 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 pixels 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.

10.1.4.11 Non-text contrast

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

New requirement

10.1.4.11 Non-text contrast

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

10.1.4.11 Non-text contrast

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

10.1.4.12 Text spacing

Where ICT is a non-web document that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

New requirement

10.1.4.12 Text spacing

Where ICT is a non-web document that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

10.1.4.12 Text spacing

Where ICT is a non-web document that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

10.1.4.13 Content on hover or focus

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

New requirement

10.1.4.13 Content on hover or focus

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

10.1.4.13 Content on hover or focus

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

10.2.1.4 Character key shortcuts

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

New requirement

10.2.1.4 Character key shortcuts

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

10.2.1.4 Character key shortcuts

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

10.2.20 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

10.2.4.1 VoidNumbering change

10.2.4.1 Void

NOTE 1: The related web page requirement "Bypass blocks" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

NOTE 2: Although not a requirement, the ability to bypass blocks of content that are repeated within documents is generally considered best practice and addresses user needs.

Explanatory update

10.2.4.1 Void

NOTE 1: The related web page requirement "Bypass blocks" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

NOTE 2: Although not a requirement, the ability to bypass blocks of content that are repeated within documents is generally considered best practice and addresses user needs.

10.2.24 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

10.2.4.5 VoidNumbering change

10.2.4.5 Void

NOTE: The related web page requirement "Multiple ways" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

Explanatory update

10.2.4.5 Void

NOTE: The related web page requirement "Multiple ways" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

10.2.5.1 Pointer gestures

Where ICT is a non-web document, it shall satisfy the following success criterion.

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to documents that interpret pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

New requirement

10.2.5.1 Pointer gestures

Where ICT is a non-web document, it shall satisfy the following success criterion.

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to documents that interpret pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

10.2.5.1 Pointer gestures

Where ICT is a non-web document, it shall satisfy the success criterion All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to documents that interpret pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

10.2.5.2 Pointer cancellation

Where ICT is a non-web document, it shall satisfy the following success criterion.

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to a document that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

New requirement

10.2.5.2 Pointer cancellation

Where ICT is a non-web document, it shall satisfy the following success criterion.

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to a document that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

10.2.5.2 Pointer cancellation

Where ICT is a non-web document, it shall satisfy the success criterion. For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to a document that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

10.2.5.3 Label in name

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

New requirement

10.2.5.3 Label in name

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

10.2.5.3 Label in name

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

10.2.5.4 Motion actuation

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

New requirement

10.2.5.4 Motion actuation

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

10.2.5.4 Motion actuation

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

10.2.31 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

10.3.2.3 VoidNumbering change

10.3.2.3 Void

NOTE: The related web page requirement "Consistent navigation" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

Explanatory update

10.3.2.3 Void

NOTE: The related web page requirement "Consistent navigation" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

10.2.32 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

10.3.2.4 VoidNumbering change

10.3.2.4 Void

NOTE: The related web page requirement "Consistent identification" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

Explanatory update

10.3.2.4 Void

NOTE: The related web page requirement "Consistent identification" does not apply to single documents, but to a specific definition of "sets of documents" that are rare.

10.4.1.3 Void

10.4.1.3 Status messages

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

New requirement

10.4.1.3 Status messages

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

10.2.39 Caption positioning

Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.

10.5 Caption positioning

Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.

Numbering change

10.5 Caption positioning

Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.

10.5 Caption positioning

Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.

11.1.2.1.2.1 Pre-recorded audio-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the functionality of software that provides a user interface shall meet requirement 5.1.5 (Visual output for auditory information).

New requirement

11.1.2.1.2.1 Pre-recorded audio-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the functionality of software that provides a user interface shall meet requirement 5.1.5 (Visual output for auditory information).

11.1.2.1.2.1 Pre-recorded audio-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the functionality of software that provides a user interface shall meet requirement 5.1.5 (Visual output for auditory information).

11.1.2.1.2.2 Pre-recorded video-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

New requirement

11.1.2.1.2.2 Pre-recorded video-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

11.1.2.1.2.2 Pre-recorded video-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

11.2.1.6 Audio description (pre-recorded)

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion Audio description is provided for all pre-recorded video content in synchronized media.

NOTE 1: The WCAG 2.0 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.

NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.5 Audio Description (Pre-recorded) with the addition of note 1 above.

11.1.2.5 Audio description (pre-recorded)

Where ICT is non-web software that provides a user interface, 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.

Numbering change

11.1.2.5 Audio description (pre-recorded)

Where ICT is non-web software that provides a user interface, 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.

11.1.2.5 Audio description (pre-recorded)

Where ICT is non-web software that provides a user interface, 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.

11.1.2.3.1 Audio description or media alternative (pre-recorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, 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.

New requirement

11.1.2.3.1 Audio description or media alternative (pre-recorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, 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.

11.1.2.3.1 Audio description or media alternative (pre-recorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, 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.

11.1.2.3.2 Audio description or media alternative (pre-recorded - closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

New requirement

11.1.2.3.2 Audio description or media alternative (pre-recorded - closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

11.1.2.3.2 Audio description or media alternative (pre-recorded - closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

11.2.1.7 Info and relationships

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

NOTE 1: 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.3 Interoperability with assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.1 Info and Relationships with the addition of note 1 above.

11.1.3.1.1 Info and relationships (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships. 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).

New requirement

11.1.3.1.1 Info and relationships (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships. 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).

11.1.3.1.1 Info and relationships (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

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).

11.1.3.1.2 Info and relationships (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

New requirement

11.1.3.1.2 Info and relationships (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

11.1.3.1.2 Info and relationships (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

11.2.1.8 Meaningful sequence

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.2 Meaningful Sequence.

11.1.3.2.1 Meaningful sequence (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

Numbering change

11.1.3.2.1 Meaningful sequence (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

11.1.3.2.1 Meaningful sequence (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

11.1.3.2.2 Meaningful sequence (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

New requirement

11.1.3.2.2 Meaningful sequence (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

11.1.3.2.2 Meaningful sequence (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.

NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.

NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.

11.1.3.4 Orientation

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

New requirement

11.1.3.4 Orientation

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

11.1.3.4 Orientation

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

11.1.3.5 Identify input purpose

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

New requirement

11.1.3.5.1 Identify input purpose (open functionality)

Where ICT is non-web software that provides a user interface and supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

Numbering change

Functional change

11.1.3.5.1 Identify input purpose (open functionality)

Where ICT is non-web software that provides a user interface and supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

11.1.3.5.2 Identify input purpose (closed functionality)

Where ICT is non-web software that provides a user interface and is closed to assistive technologies, in at least one mode of operation the ICT shall present to the user, in an audio form, the purpose of each input field collecting information about the user when the input field serves a purpose identified in the WCAG 2.1 Input Purposes for User Interface Components section

New requirement

11.1.3.5.2 Identify input purpose (closed functionality)

Where ICT is non-web software that provides a user interface and is closed to assistive technologies, in at least one mode of operation the ICT shall present to the user, in an audio form, the purpose of each input field collecting information about the user when the input field serves a purpose identified in the WCAG 2.1 Input Purposes for User Interface Components section.

11.2.1.13 Resize text

Where ICT is non-web software that provides a user interface and that supports access to enlargement features of platform or assistive technology, it shall satisfy the success criterion Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

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.

NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.4 Resize text with the addition of notes 1 and 2 above.

11.1.4.4.2 Resize text (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).

NOTE: Because the text rendering support in a closed environment may be more limited than the support found in user agents for the Web, meeting 11.1.4.4.2 in a closed environment may place a much heavier burden on the content author.

Numbering change

Functional change

11.1.4.4.2 Resize text (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).

NOTE: Because the text rendering support in a closed environment may be more limited than the support found in user agents for the Web, meeting the present clause in a closed environment may place a much heavier burden on the content author.

11.1.4.4.2 Resize text (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).

NOTE: Because the text rendering support in a closed environment may be more limited than the support found in user agents for the Web, meeting the present clause in a closed environment may place a much heavier burden on the content author.

11.2.1.14 Images of text

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion 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.

NOTE 1: Logotypes (text that is part of a logo or brand name) are considered essential.

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.5 Images of Text.

11.1.4.5.1 Images of text

(open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.

Numbering change

Functional change

Explanatory change

11.1.4.5.1 Images of text (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.

11.1.4.5.1 Images of text (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.

11.1.4.5.2 Images of text (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it does not need to meet the WCAG 2.1 Success Criterion 1.4.5 Images of Text because there is no need to impose a requirement on all closed functionality that text displayed on the screen actually be represented internally as text (as defined by WCAG 2.1), given that there is no interoperability with assistive technology.

New requirement

11.1.4.5.2 Images of text (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.6 (Speech output for non-text content).

Functional change

11.1.4.5.2 Images of text (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.6 (Speech output for non-text content).

11.1.4.10.1 Reflow (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the following success criterion.

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.

New requirement

11.1.4.10 Reflow

Where ICT is non-web software that provides a user interface it shall satisfy the following success criterion.

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.

Numbering change

Functional change

11.1.4.10 Reflow

Where ICT is non-web software that provides a user interface it shall satisfy the success criterion 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.

11.1.4.10.2 Reflow (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).

New requirementVoidVoid

11.1.4.11 Non-text contrast

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

New requirement

11.1.4.11 Non-text contrast

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

11.1.4.11 Non-text contrast

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

11.1.4.12 Text spacing

Where ICT is non-web software that provides a user interface and that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

New requirement

11.1.4.12 Text spacing

Where ICT is non-web software that provides a user interface and that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

11.1.4.12 Text spacing

Where ICT is non-web software that provides a user interface and that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

11.1.4.13 Content on hover or focus

Where ICT is a non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

New requirement

11.1.4.13 Content on hover or focus

Where ICT is a non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

11.1.4.13 Content on hover or focus

Where ICT is a non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus.

11.2.1.1.2 Keyboard (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

New requirement

11.2.1.1.2 Keyboard (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

11.2.1.1.2 Keyboard (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

11.2.1.4.1 Character key shortcuts (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

New requirement

11.2.1.4.1 Character key shortcuts (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

11.2.1.4.1 Character key shortcuts (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

11.2.1.4.2 Character key shortcuts (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

New requirement

11.2.1.4.2 Character key shortcuts (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

11.2.1.4.2 Character key shortcuts (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

11.2.1.20 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

11.2.4.1 Void

11.2.4.1 Void

NOTE 1: The related web page requirement "Bypass blocks" does not apply to single software programs, but to a specific definition of "sets of software programs" that are extremely rare.

NOTE 2: Although not a requirement, it is generally considered best practice, and to address user needs, to be able to bypass blocks of content that are repeated within software.

Stylistic update

11.2.4.1 Void

NOTE 1: The related web page requirement "Bypass blocks" does not apply to single software programs, but to a specific definition of "sets of software programs" that are extremely rare.

NOTE 2: Although not a requirement, it is generally considered best practice, and to address user needs, to be able to bypass blocks of content that are repeated within software.

11.2.1.21 Empty clause

This clause contains no requirements. It is included to align the numbering of related sub-clauses in clauses 9.2, 10.2 and 11.2.

11.2.4.2 Void

11.2.4.2 Void

NOTE 1: The related web page requirement "Page titled" does not apply to single software programs, but to a specific definition of "sets of software programs" that are extremely rare.

NOTE 2: Although the name of a software product could be a sufficient title if it describes the topic or purpose, software names are trademarked and trademark names cannot by law be descriptive names. It is not practical to make software names both unique and descriptive.

Stylistic update

11.2.4.2 Void

NOTE 1: The related web page requirement "Page titled" does not apply to single software programs, but to a specific definition of "sets of software programs" that are extremely rare.

NOTE 2: Although the name of a software product could be a sufficient title if it describes the topic or purpose, software names are trademarked and trademark names cannot by law be descriptive names. It is not practical to make software names both unique and descriptive.

11.3.1.1.2 Language of software (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.14 (Spoken languages).

New requirement

11.3.1.1.2 Language of software (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.14 (Spoken languages).

11.3.1.1.2 Language of software (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.14 (Spoken languages).

11.2.5.1 Pointer gestures

Where ICT is non-web software that provides a user interface, it shall satisfy the following success criterion.

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

New requirement

11.2.5.1 Pointer gestures

Where ICT is non-web software that provides a user interface, it shall satisfy the following success criterion.

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

11.2.5.1 Pointer gestures

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

NOTE 1: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing the original WCAG 2.1 note with note 1 above.

11.2.5.2 Pointer cancellation

Where ICT is non-web software that provides a user interface, it shall satisfy the following success criterion.

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

New requirement

11.2.5.2 Pointer cancellation

Where ICT is non-web software that provides a user interface, it shall satisfy the following success criterion.

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

11.2.5.2 Pointer cancellation

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function.
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion.
  • Up Reversal: The up-event reverses any outcome of the preceding down-event.
  • Essential: Completing the function on the down-event is essential.

NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.

NOTE 2: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation replacing the original WCAG 2.1 note with notes 1 and 2 above.

11.2.5.3 Label in name

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

New requirement

11.2.5.3.1 Label in name (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

Numbering change

11.2.5.3.1 Label in name (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

11.2.5.3.2 Label in name (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it should meet requirement 5.1.3.3 (Auditory output correlation).

New requirement

11.2.5.3.2 Label in name (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it should meet requirement 5.1.3.3 (Auditory output correlation).

11.2.5.4 Motion actuation

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

New requirement

11.2.5.4 Motion actuation

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

11.2.5.4 Motion actuation

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

11.4.1.3.1 Status messages (open functionality)

Where ICT is non-web software, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

New requirement

11.4.1.3.1 Status messages (open functionality)

Where ICT is non-web software, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

11.4.1.3.2 Status messages (closed functionality)

Not applicable.

New requirement

11.4.1.3.2 Status messages (closed functionality)

Not applicable.

13.1.1 General (informative)

Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.

It is best practice to meet the applicable relay service requirements of ES 202 975.

13.1.1 General (informative)

Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.

It is best practice to meet the applicable relay service requirements of ETSI ES 202 975.

Explanatory update

13.1.1 General (informative)

Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.

It is best practice to meet the applicable relay service requirements of ETSI ES 202 975.

13.1.1 General (informative)

Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.

It is best practice to meet the applicable relay service requirements of ETSI ES 202 975 [i.5].

13.1.6 Speech to speech relay services

Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable speech or cognitively impaired telephone users and any other user to communicate by providing assistance between them.

13.1.6 Speech to speech relay services

Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable speech or cognitively impaired telephone users and any other user to communicate by providing assistance between them.

13.1.6 Speech to speech relay services

Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable telephone users who are speech impaired, have limited cognitive, language and learning abilities, as well as any other user, to communicate by providing assistance between them.

Stylistic rewording

Functional change

Explanatory update

13.1.6 Speech to speech relay services

Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable telephone users who are speech impaired, have limited cognitive, language and learning abilities, as well as any other user, to communicate by providing assistance between them.

13.2 Access to relay services

Where ICT systems support two-way communication and a set of relay services for such communication is specified, access to those relay services shall not be prevented for outgoing and incoming calls.

NOTE 1: Two-way communication may include voice, real-time text, or video, singly or in combinations supported by both the relay service and the ICT system.

NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access by persons with disabilities.

13.2 Access to relay services

Where ICT systems support two-way communication and a set of relay services for such communication is specified, access to those relay services shall not be prevented for outgoing and incoming calls.

NOTE 1: Two-way communication may include voice, real-time text, or video, singly or in combinations supported by both the relay service and the ICT system.

NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access by persons with disabilities.

13.2 Access to relay services

Where ICT systems support two-way communication, and the system is specified for use with relay services, access to those relay services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the relay service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access by persons with disabilities.

NOTE 2: The system may be specified as needing to work with relay services by, for example: procurers, regulators, or product specifications.

Explanatory update

Stylistic rewording

Functional change

13.2 Access to relay services

Where ICT systems support two-way communication, and the system is specified for use with relay services, access to those relay services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the relay service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access by persons with disabilities.

NOTE 2: The system may be specified as needing to work with relay services by, for example: procurers, regulators, or product specifications.

13.3 Access to emergency services

Where ICT systems support two-way communication and a set of emergency services for such communication is specified, access to those emergency services shall not be prevented for outgoing and incoming calls.

NOTE 1: Two–way communication may include voice, real-time text, or video, singly or in combinations supported by both the emergency service and the ICT system.

NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access to the emergency service by persons with disabilities.

13.3 Access to emergency services

Where ICT systems support two-way communication and a set of emergency services for such communication is specified, access to those emergency services shall not be prevented for outgoing and incoming calls.

NOTE 1: Two-way communication may include voice, real-time text, or video, singly or in combinations supported by both the emergency service and the ICT system.

NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access to the emergency service by persons with disabilities.

13.3 Access to emergency services

Where ICT systems support two-way communication, and the system is specified for use with emergency services, access to those emergency services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the emergency service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access to the emergency service by persons with disabilities.

NOTE 2: The system may be specified as needing to work with emergency services by, for example: procurers, regulators, or product specifications.

Explanatory update

Stylistic rewording

Functional change

13.3 Access to emergency services

Where ICT systems support two-way communication, and the system is specified for use with emergency services, access to those emergency services shall not be prevented for outgoing and incoming calls involving: voice, RTT, or video, either individually or in combinations supported by both the emergency service and the ICT system.

NOTE 1: The purpose of this requirement is to achieve functionally equivalent communication access to the emergency service by persons with disabilities.

NOTE 2: The system may be specified as needing to work with emergency services by, for example: procurers, regulators, or product specifications.

List tables

End notes

  1. The functional performance criteria 302.7 and 302.8 of Section 508 and functional performance statements 4.2.7 and 4.2.8 of EN 301 549 inclusively cover the same requirements, despite being grouped slightly differently in each standard. Return to reference 1
  2. The functional performance criteria 302.7 and 302.8 of Section 508 and functional performance statements 4.2.7 and 4.2.8 of EN 301 549 inclusively cover the same requirements, despite being grouped slightly differently in each standard. Return to reference 2
  3. Section 508 specifies that the non-visual mode of operation must be speech output. Return to reference 3
  4. Section 508 specifies that the non-visual mode of operation must be speech output; EN 301 549 has a specific exception for “masked entry.” Return to reference 4
  5. EN 301 549 refers to specific standards for magnetic coupling. Return to reference 5
  6. EN 301 549 refers to specific standards for magnetic coupling. Return to reference 6
  7. Different approaches to calculating minimum text size. Section 508 assumes fixed distance between screen and eyes. EN 301 549 accounts for screens that are both far and near the eyes. Return to reference 7
  8. ICC A117.1-2009 section 703.7 contains some additional font type and line spacing requirements. Return to reference 8
  9. EN 301 549 has more specific privacy requirements. Return to reference 9
  10. EN 301 549 has more specific privacy requirements. Return to reference 10
  11. Section 508 refers to a specific keyboard implementation which may not be relevant for all languages. Return to reference 11
  12. Section 508 has additional requirements related to alphabetic overlay on numeric keys. Return to reference 12
  13. Some differences in approach to knee and toe clearance. Return to reference 13
  14. Some differences in approach to knee and toe clearance. Return to reference 14
  15. Some differences in approach to knee and toe clearance. Return to reference 15
  16. The EN 301 549 (2019, 2021) contains an error. “Where an obstacle is an integral part of the stationary ICT, the space under the obstacle that is between 230 mm (9 inches) and 685 mm (25 inches) above the floor is considered knee clearance and shall…” The 685 mm should have been converted to 26.969 inches. This document represents the EN standard’s original error. Return to reference 16
  17. Section 508 refers to 47 CFR 68.317 (a US regulation) whereas EN 301 549 refers to the specific level of volume gain required. Return to reference 17
  18. EN 301 549 has more specific requirements related to volume gain. Return to reference 18
  19. Each refer to relevant local standards. Return to reference 19
  20. Each refer to relevant local standards. Return to reference 20
  21. The EN 301 549 requirements are informative and refer to an upper frequency limit rather than the ITU standard. Return to reference 21
  22. EN 301 549 provides RTT requirements, discussed below. Return to reference 22
  23. EN 301 549 specifies “text form and at least one other modality” whereas Section 508 specifies “visible and audible.” Return to reference 23
  24. EN 301 549 contains more specific requirements. Return to reference 24
  25. EN 301 549 contains more specific requirements. Return to reference 25
  26. EN 301 549 contains more specific requirements. Return to reference 26
  27. EN 301 549 contains more specific requirements. Return to reference 27
  28. Section 508 refers to specific local standards related to Digital Television Tuners. Return to reference 28
  29. Section 508 focuses on operable parts whereas EN 301 549 focuses on the level of interaction. Return to reference 29
  30. Section 508 focuses on operable parts whereas EN 301 549 focuses on the level of interaction. Return to reference 30
  31. Section 508 specifically mentions keystrokes; whereas EN 301 549 is broader in scope and must include keystrokes. Return to reference 31
  32. Section 508 requires that timing be adjustable up to 2 seconds, whereas EN 301 549 requires time adjustable up to 0.5 seconds. Return to reference 32
  33. EN 301 549 treats timed response as a software issue. See EN 301 549 (2014) 11.2.1.17 (Timing Adjustable) and EN 301 549 (2018, 2019, 2021) 9.2.2.1 (Timing Adjustable). These clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 33
  34. EN 301 549 V1.1.1 (2014) and V2.1.2 (2018) provisions in the 407.8 series are recommendations (“should” versus “shall”). However, EN 301 549 V3.1.1 (2019) and EN 301 549 V3.2.1 (2021) provisions are requirements (“shall” versus “should”). Return to reference 34
  35. All versions of the EN 301 549 treats issues related to flashing and photosensitivity as a functional performance criteria (see 4.2.9) and a software criteria (see 11.2.1.19 (2014) and 9.2.3.1 for 2018, 2019, 2021) These clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 35
  36. EN 301 549 treats issues related to conveying information via multiple modalities as software issues (see 11.2.1.19 (2014) and 9.2.3.1 for 2018, 2019, 2021) These clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 36
  37. No corresponding provision in EN 301 549. Some aspects addressed in EN 301 549 (2014, 2018, 2019, 2021) sections 5.1.5, 7.1.1, 7.1.2, 7.3, 11.2.1.2, 11.2.1.3 and 11.2.1.5.The clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 37
  38. No corresponding provision in EN 301 549 (2014). Some aspects addressed in EN 301 549 (2014, 2018, 2019, 2021) sections 5.1.3, 7.2.2 and 11.3. The clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 38
  39. No corresponding provision in EN 301 549. Interoperability with assistive technology addressed in EN 301 549 (2014) 11.3. and 11.5.2.1 (2018, 2019, 2021) These clauses are not included in this document if they point only to WCAG and are not new requirements. Return to reference 39
  40. No corresponding provision in EN 301 549 (2014), but 11.6.3 and 11.8.3 (2018, 2019, 2021) covers the same requirement without specifying PDF. Return to reference 40

Page details

Date modified:
\ No newline at end of file diff --git a/en/microsoft-document-compliance-checklist/index.html b/en/microsoft-document-compliance-checklist/index.html index f412ea2b9..53a1d22e0 100644 --- a/en/microsoft-document-compliance-checklist/index.html +++ b/en/microsoft-document-compliance-checklist/index.html @@ -1,4 +1,4 @@ -Microsoft Document Compliance Checklist - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Microsoft Document Compliance Checklist

Here you can find different questions to help you to know if your Word document is accessible or not.

Microsoft Document Compliance Checklist ( Word, 56 KB)

Below are questions that will help you establish if your Microsoft Office document is accessible. We provide the Success Criteria in reference with WCAG 2.1: How to Meet WCAG - Quick Reference and the Canada.ca Content Style Guide.

Remember to answer NA (not application) if a question is not relevant to your document. For example, there are no table of content in Excel documents.

If you answer ‘No’ to one of the following questions, then your document IS NOT accessible.

A. General information

B. Color

D. Images

E. Tables

F. Lists

G. Headings

H. Other elements

Resources

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Microsoft Document Compliance Checklist

Here you can find different questions to help you to know if your Word document is accessible or not.

Microsoft Document Compliance Checklist ( Word, 56 KB)

Below are questions that will help you establish if your Microsoft Office document is accessible. We provide the Success Criteria in reference with WCAG 2.1: How to Meet WCAG - Quick Reference and the Canada.ca Content Style Guide.

Remember to answer NA (not application) if a question is not relevant to your document. For example, there are no table of content in Excel documents.

If you answer ‘No’ to one of the following questions, then your document IS NOT accessible.

A. General information

B. Color

D. Images

E. Tables

F. Lists

G. Headings

H. Other elements

Resources

Page details

Date modified:
\ No newline at end of file diff --git a/en/page-list-table/index.html b/en/page-list-table/index.html index 82b5f5fda..5d952cd02 100644 --- a/en/page-list-table/index.html +++ b/en/page-list-table/index.html @@ -9,4 +9,4 @@ w.gtag('js', new Date()); w.gtag('config', 'G-SM9MSHWDVN'); } - })(window);

Language selection

Government of Canada / Government of Canada

Search

Page list table

List of all the pages found on the Digital Accessibility Toolkit website.

Definitions of labels

Definitions of labels

Subjects

accessibilityFundamentals
Accessibility Fundamentals
howTos
How to’s
resourcesAndTools
Resources and Tools
learningAndDevelopment
Learning and Development
accessibilityInTheGovernmentOfCanada
Digital accessibility in the Government of Canada
aboutUs
About Us

Topics

aboutDisabilities
Most Common Types of Disability
globalAccessibilityStandards
Global Accessibility Standards
createDocument
Create document
createEmails
Create emails
createForms
Create forms
createWebContent
Create web content
designCourse
Design a course
designingAccessible
Designing accessible services
accessibleVirtualEvents
Accessible virtual events
testYourProducts
Test your products
accessibilityAct
Accessibility Act
procurement
Procurement
accessibilityStandards
Accessibility standards
communityDirectory
Community Directory
aboutTheDigitalTheAccessibilityToolkitProject
About the Digital the accessibility toolkit project
contactUs
Contact us
accessibilityInYourRole
Accessibility in your role
mainAbout
About us section on homepage
office2016
How to create accessible documents in Office 2016
microsoft365
How to create accessible documents in Microsoft 365
Visible columns
TitleOther language linkTopicsSubjectsLink to file
Accessible Excel workbooks in Office 2016French version of Accessible Excel workbooks in Office 2016createDocument office2016howTos/src/pages/en/ms-office/2016/accessible-excel-workbooks-in-office-2016.md
Accessible PowerPoint presentations in Office 2016French version of Accessible PowerPoint presentations in Office 2016createDocument office2016howTos/src/pages/en/ms-office/2016/accessible-powerpoint-presentations-in-office-2016.md
Accessible Word documents in Office 2016French version of Accessible Word documents in Office 2016createDocument office2016howTos/src/pages/en/ms-office/2016/accessible-word-documents-in-office-2016.md
Captioning ChecklistFrench version of Captioning ChecklistcreateWebContenthowTos/src/pages/en/captioning-checklist.md
Designing accessible imagesFrench version of Designing accessible images/src/pages/en/designing-accessible-images.md
Digital Accessibility ToolkitFrench version of Digital Accessibility Toolkit/src/main/en/index.njk
Introduction to accessibility requirements for audio-videoFrench version of Introduction to accessibility requirements for audio-videocreateWebContenthowTos/src/pages/en/introduction-to-accessibility-requirements-for-audio-video.md
Language of Audio/Video ContentFrench version of Language of Audio/Video ContentcreateWebContenthowTos/src/pages/en/language-of-audio-video-content.md
Live BroadcastFrench version of Live BroadcastcreateWebContenthowTos/src/pages/en/live-broadcast.md
RecordingsFrench version of RecordingscreateWebContenthowTos/src/pages/en/recordings.md
Statistics Canada (StatCan)French version of Statistics Canada (StatCan)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/en/statistics-canada-statcan.md
Targeted Engagement: draft Standard on Information and Communication Technology (ICT) AccessibilityFrench version of Targeted Engagement: draft Standard on Information and Communication Technology (ICT) AccessibilityaccessibilityStandardsaccessibilityInTheGovernmentOfCanada/src/pages/en/targeted-engagement-draft-standard-on-information-and-communication-technology-ict-accessibility.md
Transcript ChecklistFrench version of Transcript ChecklistcreateWebContenthowTos/src/pages/en/transcript-checklist.md
Transcript GuidelinesFrench version of Transcript GuidelinescreateWebContenthowTos/src/pages/en/transcript-guidelines.md
Virtual Meeting Platforms and Accessibility FeaturesFrench version of Virtual Meeting Platforms and Accessibility Features/src/pages/en/virtual-meeting-platforms-and-accessibility-features.md
Web Accessibility ChecklistFrench version of Web Accessibility ChecklisttestYourProductshowTos/src/pages/en/web-accessibility-checklist.md
What we heard report: Standard on Information and Communication Technology Accessibility (SICTA)French version of What we heard report: Standard on Information and Communication Technology Accessibility (SICTA)accessibilityStandardsaccessibilityInTheGovernmentOfCanada/src/pages/en/what-we-heard-report-standard-on-information-and-communication-technology-accessibility-sicta.md
About UsFrench version of About Us/src/main/en/about-us/index.njk
Access Working Group (AWG)French version of Access Working Group (AWG)/src/pages/en/access-working-group-awg.md
Accessible Excel workbooks in Microsoft 365French version of Accessible Excel workbooks in Microsoft 365createDocument microsoft365howTos/src/pages/en/ms-office/365/accessible-excel-workbooks-in-microsoft-365.md
Accessible PDF documents in Office 2016French version of Accessible PDF documents in Office 2016createDocument office2016howTos/src/pages/en/ms-office/2016/accessible-pdf-documents-in-office-2016.md
Accessible PowerPoint presentations in Microsoft 365French version of Accessible PowerPoint presentations in Microsoft 365createDocument microsoft365howTos/src/pages/en/ms-office/365/accessible-powerpoint-presentations-in-microsoft-365.md
Accessible Visio drawings in Microsoft 365French version of Accessible Visio drawings in Microsoft 365createDocument microsoft365howTos/src/pages/en/ms-office/365/accessible-visio-drawings-in-microsoft-365.md
Accessible Visio drawings in Office 2016French version of Accessible Visio drawings in Office 2016createDocument office2016howTos/src/pages/en/ms-office/2016/accessible-visio-drawings-in-office-2016.md
Accessible Word documents in Microsoft 365French version of Accessible Word documents in Microsoft 365createDocument microsoft365howTos/src/pages/en/ms-office/365/accessible-word-documents-in-microsoft-365.md
Additional resources on accessible meetings and eventsFrench version of Additional resources on accessible meetings and events/src/pages/en/additional-resources-on-accessible-meetings-and-events.md
Auditory DisabilitiesFrench version of Auditory DisabilitiesaboutDisabilitiesaccessibilityFundamentals/src/pages/en/auditory-disabilities.md
Canada School of Public Service (CSPS)French version of Canada School of Public Service (CSPS)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/en/canada-school-of-public-service-csps.md
CART Services and Sign Language InterpretersFrench version of CART Services and Sign Language InterpretersaccessibleVirtualEventshowTos/src/pages/en/cart-services-and-sign-language-interpreters-sli.md
Contact usFrench version of Contact usaboutUs/src/pages/en/contact-us.md
Digital Accessibility Toolkit projectFrench version of Digital Accessibility Toolkit projectaboutUs/src/pages/en/digital-accessibility-toolkit-project.md
Employment and Social Development Canada (ESDC)French version of Employment and Social Development Canada (ESDC)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/en/employment-and-social-development-canada-esdc.md
Find out how to make accessible digital formsFrench version of Find out how to make accessible digital formscreateFormshowTos/src/pages/en/find-out-how-to-make-accessible-digital-forms.md
How to create accessible documents in Microsoft 365French version of How to create accessible documents in Microsoft 365createDocumenthowTos/src/main/en/how-tos/microsoft-office/how-to-create-accessible-documents-in-microsoft-365.njk
How to create accessible documents in Office 2016French version of How to create accessible documents in Office 2016createDocumenthowTos/src/main/en/how-tos/microsoft-office/how-to-create-accessible-documents-in-office-2016.njk
Learning and DevelopmentFrench version of Learning and Developmentmain updatesMain/src/pages/en/learning-and-development.md
Mapping between Revised Section 508 and EN 301 549 (2014, 2018, 2019 and 2021)French version of Mapping between Revised Section 508 and EN 301 549 (2014, 2018, 2019 and 2021)procurementaccessibilityInTheGovernmentOfCanada/src/pages/en/mapping-between-revised-section-508-and-en-301-549-2014-2018-2019-and-2021.md
Microsoft Document Compliance ChecklistFrench version of Microsoft Document Compliance ChecklistcreateDocumenthowTos/src/pages/en/microsoft-document-compliance-checklist.md
Mobility, Flexibility, and Body Structure DisabilitiesFrench version of Mobility, Flexibility, and Body Structure DisabilitiesaboutDisabilitiesaccessibilityFundamentals/src/pages/en/mobility-flexibility-and-body-structure-disabilities.md
PDF Accessibility ChecklistFrench version of PDF Accessibility ChecklistcreateDocumenthowTos/src/pages/en/pdf-accessibility-checklist.md
Terms of ReferenceFrench version of Terms of ReferenceaboutUs/src/pages/en/terms-of-reference.md
The structure of Web Content Accessibility Guidelines (WCAG) 2.1French version of The structure of Web Content Accessibility Guidelines (WCAG) 2.1/src/pages/en/the-structure-of-web-content-accessibility-guidelines-wcag-21.md
Useful LinksFrench version of Useful Links/src/pages/en/useful-links.md
Visual ImpairmentsFrench version of Visual ImpairmentsaboutDisabilitiesaccessibilityFundamentals/src/pages/en/visual-impairments.md
Accessibility FundamentalsFrench version of Accessibility Fundamentalsmain/src/main/en/accessibility-fundamentals/index.njk
Accessibility in your roleFrench version of Accessibility in your role/src/main/en/accessibility-in-your-role.njk
Accessibility standardsFrench version of Accessibility standardsaccessibilityInTheGovernmentOfCanada/src/main/en/accessibility-in-the-government-of-canada/accessibility-standards.njk
Accessibility Testing 101French version of Accessibility Testing 101testYourProductshowTos/src/pages/en/accessibility-testing-101.md
Accessible virtual eventsFrench version of Accessible virtual eventshowTos/src/main/en/how-tos/accessible-virtual-events.njk
Alternative text and long description – Best practicesFrench version of Alternative text and long description – Best practicescreateWebContenthowTos/src/pages/en/alternative-text-and-long-description-best-practices.md
Audio Description GuidelinesFrench version of Audio Description GuidelinescreateWebContenthowTos/src/pages/en/audio-description-guidelines.md
Best practices for accessible virtual eventsFrench version of Best practices for accessible virtual eventsaccessibleVirtualEvents updatesMainhowTos/src/pages/en/best-practices-for-accessible-virtual-events.md
Cognitive DisabilitiesFrench version of Cognitive DisabilitiesaboutDisabilitiesaccessibilityFundamentals/src/pages/en/cognitive-disabilities.md
Community DirectoryFrench version of Community DirectoryaccessibilityInTheGovernmentOfCanada/src/main/en/accessibility-in-the-government-of-canada/community-directory.njk
Designing accessible servicesFrench version of Designing accessible serviceshowTos/src/main/en/how-tos/designing-accessible-services.njk
Designing for users of screen readersFrench version of Designing for users of screen readersdesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-of-screen-readers.md
Designing for users on the autism spectrumFrench version of Designing for users on the autism spectrumdesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-on-the-autism-spectrum.md
Designing for users who are deaf or hard of hearingFrench version of Designing for users who are deaf or hard of hearingdesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-who-are-deaf-or-hard-of-hearing.md
Designing for users with cognitive disabilitiesFrench version of Designing for users with cognitive disabilitiesdesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-with-cognitive-disabilities.md
Designing for users with low visionFrench version of Designing for users with low visiondesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-with-low-vision.md
Designing for users with physical or motor disabilitiesFrench version of Designing for users with physical or motor disabilitiesdesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-with-physical-or-motor-disabilities.md
Digital accessibility in the Government of CanadaFrench version of Digital accessibility in the Government of Canadamain/src/main/en/accessibility-in-the-government-of-canada/index.njk
Do’s and Don’ts for developing online coursesFrench version of Do’s and Don’ts for developing online coursesdesignCoursehowTos/src/pages/en/do-s-and-don-ts-for-developing-online-courses.md
Global Accessibility StandardsFrench version of Global Accessibility StandardsaccessibilityFundamentals/src/main/en/accessibility-fundamentals/global-accessibility-standards.njk
Information and Communication Technology (ICT) Accessibility RequirementsFrench version of Information and Communication Technology (ICT) Accessibility RequirementsprocurementaccessibilityInTheGovernmentOfCanada/src/pages/en/information-and-communications-technology-ict-accessibility-requirements.md
Most Common Types of DisabilityFrench version of Most Common Types of DisabilityaccessibilityFundamentals/src/main/en/accessibility-fundamentals/most-common-types-of-disability.njk
Personas with Disabilities for inclusive user experience (UX) designFrench version of Personas with Disabilities for inclusive user experience (UX) designdesignCoursehowTos/src/pages/en/personas-with-disabilities-for-inclusive-user-experience-ux-design.md
ProcurementFrench version of ProcurementaccessibilityInTheGovernmentOfCanada/src/main/en/accessibility-in-the-government-of-canada/procurement.njk
Research on our target audienceFrench version of Research on our target audienceaboutUs/src/pages/en/research-on-our-target-audience.md
Tips for creating online coursesFrench version of Tips for creating online coursesdesignCoursehowTos/src/pages/en/tips-for-creating-online-courses.md
Universal Design for Learning (UDL)French version of Universal Design for Learning (UDL)designCoursehowTos/src/pages/en/universal-design-for-learning-udl.md
Accessible PDF documents in Microsoft 365French version of Accessible PDF documents in Microsoft 365createDocument microsoft365howTos/src/pages/en/ms-office/365/accessible-pdf-documents-in-microsoft-365.md
Additional ResourcesFrench version of Additional ResourcesresourcesAndTools/src/pages/en/additional-resources.md
Create documentFrench version of Create documenthowTos/src/main/en/how-tos/create-document.njk
Create formsFrench version of Create formshowTos/src/main/en/how-tos/create-forms.njk
Create web contentFrench version of Create web contenthowTos/src/main/en/how-tos/create-web-content.njk
Design a courseFrench version of Design a coursehowTos/src/main/en/how-tos/design-a-course.njk
How to’sFrench version of How to’smain/src/main/en/how-tos/index.njk
Making Accessible EmailsFrench version of Making Accessible EmailshowTos updatesMain/src/pages/en/making-accessible-emails.md
ResourcesFrench version of Resources/src/main/en/resources-and-tools/resources.njk
Resources and ToolsFrench version of Resources and Toolsmain/src/main/en/resources-and-tools/index.njk
Technical Summary of the EN 301 549 v3.2.1 (2021)French version of Technical Summary of the EN 301 549 v3.2.1 (2021)procurementaccessibilityInTheGovernmentOfCanada/src/pages/en/technical-summary-of-the-en-301-549-v3-2-1-2021.md
Test your productsFrench version of Test your productshowTos updatesMain/src/main/en/how-tos/test-your-products.njk
ToolsFrench version of Tools/src/main/en/resources-and-tools/tools.njk

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Page list table

List of all the pages found on the Digital Accessibility Toolkit website.

Definitions of labels

Definitions of labels

Subjects

accessibilityFundamentals
Accessibility Fundamentals
howTos
How to’s
resourcesAndTools
Resources and Tools
learningAndDevelopment
Learning and Development
accessibilityInTheGovernmentOfCanada
Digital accessibility in the Government of Canada
aboutUs
About Us

Topics

aboutDisabilities
Most Common Types of Disability
globalAccessibilityStandards
Global Accessibility Standards
createDocument
Create document
createEmails
Create emails
createForms
Create forms
createWebContent
Create web content
designCourse
Design a course
designingAccessible
Designing accessible services
accessibleVirtualEvents
Accessible virtual events
testYourProducts
Test your products
accessibilityAct
Accessibility Act
procurement
Procurement
accessibilityStandards
Accessibility standards
communityDirectory
Community Directory
aboutTheDigitalTheAccessibilityToolkitProject
About the Digital the accessibility toolkit project
contactUs
Contact us
accessibilityInYourRole
Accessibility in your role
mainAbout
About us section on homepage
office2016
How to create accessible documents in Office 2016
microsoft365
How to create accessible documents in Microsoft 365
Visible columns
TitleOther language linkTopicsSubjectsLink to file
Accessible Excel workbooks in Office 2016French version of Accessible Excel workbooks in Office 2016createDocument office2016howTos/src/pages/en/ms-office/2016/accessible-excel-workbooks-in-office-2016.md
Accessible PowerPoint presentations in Office 2016French version of Accessible PowerPoint presentations in Office 2016createDocument office2016howTos/src/pages/en/ms-office/2016/accessible-powerpoint-presentations-in-office-2016.md
Accessible Word documents in Office 2016French version of Accessible Word documents in Office 2016createDocument office2016howTos/src/pages/en/ms-office/2016/accessible-word-documents-in-office-2016.md
Captioning ChecklistFrench version of Captioning ChecklistcreateWebContenthowTos/src/pages/en/captioning-checklist.md
Designing accessible imagesFrench version of Designing accessible images/src/pages/en/designing-accessible-images.md
Digital Accessibility ToolkitFrench version of Digital Accessibility Toolkit/src/main/en/index.njk
Language of Audio/Video ContentFrench version of Language of Audio/Video ContentcreateWebContenthowTos/src/pages/en/language-of-audio-video-content.md
Live BroadcastFrench version of Live BroadcastcreateWebContenthowTos/src/pages/en/live-broadcast.md
RecordingsFrench version of RecordingscreateWebContenthowTos/src/pages/en/recordings.md
Targeted Engagement: draft Standard on Information and Communication Technology (ICT) AccessibilityFrench version of Targeted Engagement: draft Standard on Information and Communication Technology (ICT) AccessibilityaccessibilityStandardsaccessibilityInTheGovernmentOfCanada/src/pages/en/targeted-engagement-draft-standard-on-information-and-communication-technology-ict-accessibility.md
Transcript ChecklistFrench version of Transcript ChecklistcreateWebContenthowTos/src/pages/en/transcript-checklist.md
Transcript GuidelinesFrench version of Transcript GuidelinescreateWebContenthowTos/src/pages/en/transcript-guidelines.md
Virtual Meeting Platforms and Accessibility FeaturesFrench version of Virtual Meeting Platforms and Accessibility Features/src/pages/en/virtual-meeting-platforms-and-accessibility-features.md
Web Accessibility ChecklistFrench version of Web Accessibility ChecklisttestYourProductshowTos/src/pages/en/web-accessibility-checklist.md
What we heard report: Standard on Information and Communication Technology Accessibility (SICTA)French version of What we heard report: Standard on Information and Communication Technology Accessibility (SICTA)accessibilityStandardsaccessibilityInTheGovernmentOfCanada/src/pages/en/what-we-heard-report-standard-on-information-and-communication-technology-accessibility-sicta.md
About UsFrench version of About Us/src/main/en/about-us/index.njk
Accessible Excel workbooks in Microsoft 365French version of Accessible Excel workbooks in Microsoft 365createDocument microsoft365howTos/src/pages/en/ms-office/365/accessible-excel-workbooks-in-microsoft-365.md
Accessible PDF documents in Office 2016French version of Accessible PDF documents in Office 2016createDocument office2016howTos/src/pages/en/ms-office/2016/accessible-pdf-documents-in-office-2016.md
Accessible PowerPoint presentations in Microsoft 365French version of Accessible PowerPoint presentations in Microsoft 365createDocument microsoft365howTos/src/pages/en/ms-office/365/accessible-powerpoint-presentations-in-microsoft-365.md
Accessible Visio drawings in Microsoft 365French version of Accessible Visio drawings in Microsoft 365createDocument microsoft365howTos/src/pages/en/ms-office/365/accessible-visio-drawings-in-microsoft-365.md
Accessible Visio drawings in Office 2016French version of Accessible Visio drawings in Office 2016createDocument office2016howTos/src/pages/en/ms-office/2016/accessible-visio-drawings-in-office-2016.md
Accessible Word documents in Microsoft 365French version of Accessible Word documents in Microsoft 365createDocument microsoft365howTos/src/pages/en/ms-office/365/accessible-word-documents-in-microsoft-365.md
Additional resources on accessible meetings and eventsFrench version of Additional resources on accessible meetings and events/src/pages/en/additional-resources-on-accessible-meetings-and-events.md
Contact usFrench version of Contact usaboutUs/src/pages/en/contact-us.md
Designing accessible servicesFrench version of Designing accessible serviceshowTos/src/main/en/how-tos/designing-accessible-services.njk
Designing for users of screen readersFrench version of Designing for users of screen readersdesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-of-screen-readers.md
Designing for users on the autism spectrumFrench version of Designing for users on the autism spectrumdesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-on-the-autism-spectrum.md
Designing for users who are deaf or hard of hearingFrench version of Designing for users who are deaf or hard of hearingdesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-who-are-deaf-or-hard-of-hearing.md
Designing for users with cognitive disabilitiesFrench version of Designing for users with cognitive disabilitiesdesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-with-cognitive-disabilities.md
How to create accessible documents in Microsoft 365French version of How to create accessible documents in Microsoft 365createDocumenthowTos/src/main/en/how-tos/microsoft-office/how-to-create-accessible-documents-in-microsoft-365.njk
How to create accessible documents in Office 2016French version of How to create accessible documents in Office 2016createDocumenthowTos/src/main/en/how-tos/microsoft-office/how-to-create-accessible-documents-in-office-2016.njk
Learning and DevelopmentFrench version of Learning and Developmentmain updatesMain/src/pages/en/learning-and-development.md
Mobility, Flexibility, and Body Structure DisabilitiesFrench version of Mobility, Flexibility, and Body Structure DisabilitiesaboutDisabilitiesaccessibilityFundamentals/src/pages/en/mobility-flexibility-and-body-structure-disabilities.md
Accessibility FundamentalsFrench version of Accessibility Fundamentalsmain/src/main/en/accessibility-fundamentals/index.njk
Accessibility in your roleFrench version of Accessibility in your role/src/main/en/accessibility-in-your-role.njk
Accessibility standardsFrench version of Accessibility standardsaccessibilityInTheGovernmentOfCanada/src/main/en/accessibility-in-the-government-of-canada/accessibility-standards.njk
Accessible virtual eventsFrench version of Accessible virtual eventshowTos/src/main/en/how-tos/accessible-virtual-events.njk
Community DirectoryFrench version of Community DirectoryaccessibilityInTheGovernmentOfCanada/src/main/en/accessibility-in-the-government-of-canada/community-directory.njk
Create documentFrench version of Create documenthowTos/src/main/en/how-tos/create-document.njk
Create formsFrench version of Create formshowTos/src/main/en/how-tos/create-forms.njk
Designing for users with low visionFrench version of Designing for users with low visiondesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-with-low-vision.md
Designing for users with physical or motor disabilitiesFrench version of Designing for users with physical or motor disabilitiesdesigningAccessiblehowTos/src/pages/en/design-accessible-services/designing-for-users-with-physical-or-motor-disabilities.md
Digital accessibility in the Government of CanadaFrench version of Digital accessibility in the Government of Canadamain/src/main/en/accessibility-in-the-government-of-canada/index.njk
Do’s and Don’ts for developing online coursesFrench version of Do’s and Don’ts for developing online coursesdesignCoursehowTos/src/pages/en/do-s-and-don-ts-for-developing-online-courses.md
Global Accessibility StandardsFrench version of Global Accessibility StandardsaccessibilityFundamentals/src/main/en/accessibility-fundamentals/global-accessibility-standards.njk
Most Common Types of DisabilityFrench version of Most Common Types of DisabilityaccessibilityFundamentals/src/main/en/accessibility-fundamentals/most-common-types-of-disability.njk
ProcurementFrench version of ProcurementaccessibilityInTheGovernmentOfCanada/src/main/en/accessibility-in-the-government-of-canada/procurement.njk
Tips for creating online coursesFrench version of Tips for creating online coursesdesignCoursehowTos/src/pages/en/tips-for-creating-online-courses.md
Access Working Group (AWG)French version of Access Working Group (AWG)/src/pages/en/access-working-group-awg.md
Accessibility Testing 101French version of Accessibility Testing 101testYourProductshowTos/src/pages/en/accessibility-testing-101.md
Accessible PDF documents in Microsoft 365French version of Accessible PDF documents in Microsoft 365createDocument microsoft365howTos/src/pages/en/ms-office/365/accessible-pdf-documents-in-microsoft-365.md
Additional ResourcesFrench version of Additional ResourcesresourcesAndTools/src/pages/en/additional-resources.md
Alternative text and long description – Best practicesFrench version of Alternative text and long description – Best practicescreateWebContenthowTos/src/pages/en/alternative-text-and-long-description-best-practices.md
Audio Description GuidelinesFrench version of Audio Description GuidelinescreateWebContenthowTos/src/pages/en/audio-description-guidelines.md
Auditory DisabilitiesFrench version of Auditory DisabilitiesaboutDisabilitiesaccessibilityFundamentals/src/pages/en/auditory-disabilities.md
Best practices for accessible virtual eventsFrench version of Best practices for accessible virtual eventsaccessibleVirtualEvents updatesMainhowTos/src/pages/en/best-practices-for-accessible-virtual-events.md
Canada School of Public Service (CSPS)French version of Canada School of Public Service (CSPS)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/en/canada-school-of-public-service-csps.md
CART Services and Sign Language InterpretersFrench version of CART Services and Sign Language InterpretersaccessibleVirtualEventshowTos/src/pages/en/cart-services-and-sign-language-interpreters-sli.md
Cognitive DisabilitiesFrench version of Cognitive DisabilitiesaboutDisabilitiesaccessibilityFundamentals/src/pages/en/cognitive-disabilities.md
Create web contentFrench version of Create web contenthowTos/src/main/en/how-tos/create-web-content.njk
Design a courseFrench version of Design a coursehowTos/src/main/en/how-tos/design-a-course.njk
Digital Accessibility Toolkit projectFrench version of Digital Accessibility Toolkit projectaboutUs/src/pages/en/digital-accessibility-toolkit-project.md
Employment and Social Development Canada (ESDC)French version of Employment and Social Development Canada (ESDC)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/en/employment-and-social-development-canada-esdc.md
Find out how to make accessible digital formsFrench version of Find out how to make accessible digital formscreateFormshowTos/src/pages/en/find-out-how-to-make-accessible-digital-forms.md
How to’sFrench version of How to’smain/src/main/en/how-tos/index.njk
Information and Communication Technology (ICT) Accessibility RequirementsFrench version of Information and Communication Technology (ICT) Accessibility RequirementsprocurementaccessibilityInTheGovernmentOfCanada/src/pages/en/information-and-communications-technology-ict-accessibility-requirements.md
Introduction to accessibility requirements for audio-videoFrench version of Introduction to accessibility requirements for audio-videocreateWebContenthowTos/src/pages/en/introduction-to-accessibility-requirements-for-audio-video.md
Making Accessible EmailsFrench version of Making Accessible EmailshowTos updatesMain/src/pages/en/making-accessible-emails.md
Mapping between Revised Section 508 and EN 301 549 (2014, 2018, 2019 and 2021)French version of Mapping between Revised Section 508 and EN 301 549 (2014, 2018, 2019 and 2021)procurementaccessibilityInTheGovernmentOfCanada/src/pages/en/mapping-between-revised-section-508-and-en-301-549-2014-2018-2019-and-2021.md
Microsoft Document Compliance ChecklistFrench version of Microsoft Document Compliance ChecklistcreateDocumenthowTos/src/pages/en/microsoft-document-compliance-checklist.md
PDF Accessibility ChecklistFrench version of PDF Accessibility ChecklistcreateDocumenthowTos/src/pages/en/pdf-accessibility-checklist.md
Personas with Disabilities for inclusive user experience (UX) designFrench version of Personas with Disabilities for inclusive user experience (UX) designdesignCoursehowTos/src/pages/en/personas-with-disabilities-for-inclusive-user-experience-ux-design.md
Research on our target audienceFrench version of Research on our target audienceaboutUs/src/pages/en/research-on-our-target-audience.md
ResourcesFrench version of Resources/src/main/en/resources-and-tools/resources.njk
Resources and ToolsFrench version of Resources and Toolsmain/src/main/en/resources-and-tools/index.njk
Statistics Canada (StatCan)French version of Statistics Canada (StatCan)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/en/statistics-canada-statcan.md
Technical Summary of the EN 301 549 v3.2.1 (2021)French version of Technical Summary of the EN 301 549 v3.2.1 (2021)procurementaccessibilityInTheGovernmentOfCanada/src/pages/en/technical-summary-of-the-en-301-549-v3-2-1-2021.md
Terms of ReferenceFrench version of Terms of ReferenceaboutUs/src/pages/en/terms-of-reference.md
Test your productsFrench version of Test your productshowTos updatesMain/src/main/en/how-tos/test-your-products.njk
The structure of Web Content Accessibility Guidelines (WCAG) 2.1French version of The structure of Web Content Accessibility Guidelines (WCAG) 2.1/src/pages/en/the-structure-of-web-content-accessibility-guidelines-wcag-21.md
ToolsFrench version of Tools/src/main/en/resources-and-tools/tools.njk
Universal Design for Learning (UDL)French version of Universal Design for Learning (UDL)designCoursehowTos/src/pages/en/universal-design-for-learning-udl.md
Useful LinksFrench version of Useful Links/src/pages/en/useful-links.md
Visual ImpairmentsFrench version of Visual ImpairmentsaboutDisabilitiesaccessibilityFundamentals/src/pages/en/visual-impairments.md

Page details

Date modified:
\ No newline at end of file diff --git a/en/pdf-accessibility-checklist/index.html b/en/pdf-accessibility-checklist/index.html index 88d7c69e2..afbbbc957 100644 --- a/en/pdf-accessibility-checklist/index.html +++ b/en/pdf-accessibility-checklist/index.html @@ -1,4 +1,4 @@ -PDF Accessibility Checklist - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

PDF Accessibility Checklist

Here you can find different questions to help you to know if your pdf document is accessible or not.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

PDF Accessibility Checklist ( PDF, 324 KB)

Introduction

The purpose of the PDF Accessibility Checklist is to support Employment and Social Development Canada (ESDC) PDF document developers ensure that accessibility compliance meets the Web Content Accessibility Guidelines (WCAG) 2.1 standards. Please note that the checklist only contains WCAG criteria that are related to the most common errors identified in PDF documents.

We established a list of tools and resources to help developers verify their document accessibility, as well as the PDF Accessibility Checklist that identifies 27 success criteria that are pertinent to PDFs.

Tools and Resources

Resources to make Accessible PDFs

PDF Accessibility Checklist Instructions

Please complete the PDF Accessibility Checklist. This is to ensure common accessibility errors are resolved.

Please note for ESDC employees, you will need to fill out this checklist prior to requesting an accessibility audit from the IT Accessibility Office.

Contact Information

For any further questions or comments regarding the PDF Accessibility Checklist, or to request an accessibility audit, please submit a new request.

Checklist

Glossary

Alternative Text:
Text associated with an image that conveys the same essential information as the image.
Assistive Technology:
Any light-, mid-, or high-tech tool or device which helps people with disabilities perform tasks with greater ease or independence.
Bookmark:
A type of link with representative text that makes it easier to navigate through documents.
Descriptive Text:
The text that describes a form field’s contents to a screen reader user. This is also called a "label”.
Reading Order:
This is the order in which assistive technologies, like screen readers, present the content in a PDF. The tags in the Tags Tree determine this order.
Running Headers/Footers:
Information that is repeated at the top/bottom of pages in a document. They often contain information such as page number, the name of the document, etc.
Screen Reader:
A software program used to allow reading of content and navigation of the screen using speech or Braille output. Used primarily by persons who are blind or have low vision.
Tags:
The structured, textual representation of the PDF content that is accessed by screen readers, to read the document out-loud.

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

PDF Accessibility Checklist

Here you can find different questions to help you to know if your pdf document is accessible or not.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link

PDF Accessibility Checklist ( PDF, 324 KB)

Introduction

The purpose of the PDF Accessibility Checklist is to support Employment and Social Development Canada (ESDC) PDF document developers ensure that accessibility compliance meets the Web Content Accessibility Guidelines (WCAG) 2.1 standards. Please note that the checklist only contains WCAG criteria that are related to the most common errors identified in PDF documents.

We established a list of tools and resources to help developers verify their document accessibility, as well as the PDF Accessibility Checklist that identifies 27 success criteria that are pertinent to PDFs.

Tools and Resources

Resources to make Accessible PDFs

PDF Accessibility Checklist Instructions

Please complete the PDF Accessibility Checklist. This is to ensure common accessibility errors are resolved.

Please note for ESDC employees, you will need to fill out this checklist prior to requesting an accessibility audit from the IT Accessibility Office.

Contact Information

For any further questions or comments regarding the PDF Accessibility Checklist, or to request an accessibility audit, please submit a new request.

Checklist

Glossary

Alternative Text:
Text associated with an image that conveys the same essential information as the image.
Assistive Technology:
Any light-, mid-, or high-tech tool or device which helps people with disabilities perform tasks with greater ease or independence.
Bookmark:
A type of link with representative text that makes it easier to navigate through documents.
Descriptive Text:
The text that describes a form field’s contents to a screen reader user. This is also called a "label”.
Reading Order:
This is the order in which assistive technologies, like screen readers, present the content in a PDF. The tags in the Tags Tree determine this order.
Running Headers/Footers:
Information that is repeated at the top/bottom of pages in a document. They often contain information such as page number, the name of the document, etc.
Screen Reader:
A software program used to allow reading of content and navigation of the screen using speech or Braille output. Used primarily by persons who are blind or have low vision.
Tags:
The structured, textual representation of the PDF content that is accessed by screen readers, to read the document out-loud.

Page details

Date modified:
\ No newline at end of file diff --git a/en/personas-with-disabilities-for-inclusive-user-experience-ux-design/index.html b/en/personas-with-disabilities-for-inclusive-user-experience-ux-design/index.html index 21c8b989d..7b2771a38 100644 --- a/en/personas-with-disabilities-for-inclusive-user-experience-ux-design/index.html +++ b/en/personas-with-disabilities-for-inclusive-user-experience-ux-design/index.html @@ -1,4 +1,4 @@ -Personas with Disabilities for inclusive user experience (UX) design - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Personas with Disabilities for inclusive user experience (UX) design

The case to include disabilities into user personas, the types of technologies they use, and sample personas with disabilities.

On this page

The purpose of this document is to assist the user in understanding how to build personas with disabilities. Personas are fictional characters created to represent different user types that may use a site, brand, or product in their own particular ways. Developers often design websites and web applications, both desktop and mobile, to their own liking which can potentially cause barriers for some users. It is important to plan for a diverse group of users with a wide range of abilities, technical levels, functional capabilities and familiarity with processes or activities. One important aspect of Inclusive Design is to include people with disabilities in the early design stage and throughout all steps in the software development life-cycle. This will help increase the accessibility and usability components of the end product and better ensure inclusive best practices. This document is a collection of material from a variety of sources geared towards assembling a cohesive view towards inclusion by design.

Creating equal access for everyone

The Government of Canada is committed to delivering information to the public in an accessible format and is equally committed to creating an inclusive, barrier-free work environment that include persons with disabilities. Both obligations require following standards, requirements, guidelines and supporting an extensive use of technology including various adaptive technology tools including software, hardware and devices for users with disabilities.

Users access information through various means: desktop computers, laptops, and mobile devices including smartphones and tablets. In order to keep pace with the demand and provide a satisfactory experience to all users, we should consider 3 different aspects of requirements:

  1. Need for an enterprise level functionality and inclusion requirements, such as:
    1. The functional requirements of end users with disabilities, that include the following Adaptive techniques, tools and technologies:
      1. Vision Enhancement;
      2. Vision Replacement;
      3. Audio Enhancement and Replacement;
      4. Mobility and Dexterity Enhancement and Replacement;
      5. Cognitive and Learning Style Enhancement.
    2. The identified tasks and users abilities.
  2. The design of the applications that make up the solution and how they relate to both:
    1. the operating system manufacturer's own published standards; and
    2. the standards for accessible native applications.
  3. Individual user needs in terms of adaptive technology and built in functionality.

Understanding adaptive techniques, tools and technology

Vision enhancement technology

Vision Enhancement Technology is used by a wide variety of individuals with some form of visual impairment (commonly referred to as "low vision"), where the person still relies on their vision to consume information. The requirements can be quite varied in the manner and level of features required (i.e. someone with a different field of vision will require different settings from someone with glaucoma or a form of color blindness).

The information is often presented differently such as using high contrasting colors, large print or magnification. The system often must be usable with low vision without relying on audio. Low vision is sometimes accompanied by hearing loss. This is especially common in older people. Audio alone as an accessibility strategy will fail to meet the needs of this group. Screen magnification programs (also called large print programs) allow users to enlarge a portion of their screen. This effectively turns the computer monitor into a viewport showing only a portion of an enlarged virtual display. The user can then use the mouse or keyboard commands to move this viewport in order to view different areas of the virtual display.

Vision replacement technology

Vision Replacement Technology is used by individuals with some form of visual impairment (commonly referred to as "blind"), where the person no longer relies or never relied on their vision to consume information. The information is often presented in a different modality such as through Braille or a Text To Speech Engine. Microsoft's Windows, Windows Mobile, Linux, Blackberry OS, Apple Mac OS, iOS, Google's Android and Chrome OS (among others) all have solutions for blind users that make use of screen reader software for a variety of devices. Screen Readers attempt to identify and interpret what is being displayed on the screen. The information is then represented to the user with text-to-speech, sound, haptic icons or a Braille output device. The screen reader keeps track of events that happen (such as windows opening) and actions that are performed on a device with a physical keyboard, D-Pad, Trackball or joystick when movement is performed. On a device with a touch screen, it alters the way the touch screen behaves and provides touch based methods of interaction. There is also Touch Exploration Technology, which allows a blind person to explore the screen with touch without activating the items on the screen. The screen reader can also provide feedback about screen items by providing audio or haptic alerts. It also provides spoken text as controls and information when touched. A set of additional gestures are provided to move around on the screen from item to item and to activate specific screen reader functions (such as reading a block of text).

Audio enhancement and replacement technology

Audio Enhancement and Replacement Technology is used by individuals with some form of hearing impairment or limitation and some users with speech or communication related impairment. There is a wide variety of needs and requirements in this category of technology. Solutions can be as simple as t-coil hearing aid compatibility to as complex as teletypewriter (TTY) access.

Systems often must be usable without hearing. Information conveyed by audio alone is not accessible by individuals who are deaf. Systems often must also be usable with limited hearing. People with limited hearing often cannot see well either, especially people who are older. Allowing them to use their residual hearing is therefore important rather than having to rely on sight (e.g. relying on access techniques that would be used by people who are deaf).

Individuals who do not hear beeps or recognize spoken words may require a program to prompt them in a different manner, such as a screen flash or displaying spoken messages as text or that translate audio cues to visual ones.

Mobility and dexterity enhancement and replacement technology

Mobility and Dexterity Related Technology is used by individuals with some form of physical impairment or limitation. There is a wide variety of needs and requirements in this category of technology. Solutions can be as simple as alternate input such as voice recognition or as complex as scanning with switch access. There are many different kinds of switches on the market that can be used for touching, clicking and dragging operations, in conjunction with a cursor movement device. Switches can also be used to communicate with a device using different coding systems such as Morse code which is helpful to some persons with severe physical disabilities, who use it to input text.

Voice Recognition technology allows the user to control the device and to input text using the voice. Although voice recognition is becoming mainstream, it has always had important applications to the adaptive technology industry. It allows for hands free device use. In addition to being usable by people with differing levels of dexterity or mobility needs, systems must be usable regardless of the severity of the physical impairment. For a person with a physical disability e.g., limited strength, reach or manipulation, tremor, lack of sensation, technology can provide modes of operation that do not require fine motor control or simultaneous actions. Adaptive technology can provide modes that are operable with limited reach, strength and that do not require a response time.

Cognitive and learning style enhancement technology

Cognitive and learning disabilities are neurologically-based processing problems. These processing problems can interfere with learning skills such as reading, writing and/or math. They can also interfere with higher level skills such as organization, time planning, abstract reasoning, long or short-term memory and attention. There is a wide variety of needs and requirements in this category of technology.

Solutions can be as simple as a calendar and task systems or as complex as multi-modal document reading.

Voice Recognition helps persons with dyslexia and dysgraphia that may have difficulty expressing themselves. Additionally, certain typing and writing software that is designed to aid the process of entering information into a computer through the use of tools such as phonetic spell check and advanced thesaurus are commonly used. Usually a combination of screen reading, magnification systems and alternate input devices are used to provide computing access to persons with such impairments.

There are cognitive impairments which take many forms, including Downs Syndrome, short and long-term memory impairments, and perceptual differences. Proper application design can increase functionality of computers for people with mild cognitive impairments.

Visual Stress Syndrome (Concussion) is a neurological condition that interferes with reading, attention, coordination, general health and behaviour, and can occur despite normal vision. Visual Stress occurs when stimuli such as patterns, contrast, light and colour affect the visual cortex, altering brain function and resulting in symptoms of physical discomfort and perceptual distortions. Solutions such as coloured filters have been shown to reduce the effects of these stimuli, calming the stress and restoring brain function.

Certain physical or neurological impairments make speaking difficult for some individuals. Systems that can speak for its user can be used to help individuals with speech impairments. Most of the software packages used for these applications operates with a speech synthesizer.

Breaking down usability barriers

Common problems that users experience while browsing the web and accessing information via technology can be categorized into the following barriers:

It's not simply just about checklists; inclusion is personal and about people. Following the Web Content Accessibility Guidelines (WCAG) 2.0 will make Web content more accessible, however, the important question is, will the content be usable?

Involve users throughout your project

Accessibility should be addressed early in the life cycle of the project; starting from project inception and it should be included in the user-centered design (UCD) processes, including user personas. Our personas should include the different ranges of disabilities. Creating a range of personas, including personas of persons with disabilities, will help developers understand accessibility requirements and implement more universally usable solutions.

Incorporating accessibility needs into personas

Designing personas with disabilities requires special attention as there is a long list of key factors to consider:

Sample of general personas with disabilities

Trevor is 18 years old

He lives with family and goes to secondary school. He uses desktop computers at school, a laptop at home and a basic mobile phone with Short Message Service (SMS). He likes consistent and familiar places on the web.

Disability Category:
Cognitive and Learning Style Enhancement
Disability:
Autism Spectrum Disorder
Ability:
Uses larger text and a program that hides everything but the text, so he doesn’t get distracted
Aptitude:
Uses the computer well for games, but doesn’t learn new sites easily
Attitude:
Prefers familiar sites in an established routine
Adaptive Technology:
Text preference settings, power keyboard user

Emily is 24 years old

She graduated from high school and is working on a college degree. She lives in a small independent living facility and works part-time at a local community center. She wants to do everything for herself.

Disability Category:
Mobility and Dexterity Enhancement and Replacement
Disability:
Cerebral palsy. Difficult to use hands and has some difficulty speaking clearly
Ability:
Uses a motorized wheel chair
Aptitude:
Uses the computer well, with the right input device; good at finding efficient search terms
Attitude:
Wants to do everything for herself; can be impatient
Adaptive Technology:
Augmentative and Alternative Communication (AAC) Communicator with speech generator, iPad, power wheelchair.

Francis is a 30 year old war veteran who lives with his girlfriend

He uses a laptop at home, computers at community centres and libraries, and his iPhone. He works part time at the community centre as a receptionist and finds it difficult to concentrate, remember, manage stress, think, write and speak clearly. He has trouble organizing and managing time. This tends to cause problems for Francis in social and work situations.

Disability Category:
Cognitive and Learning Style Enhancement
Disabilities:
Post Traumatic Stress Disorder (PTSD). Cognitive impairments
Ability:
Slow writing and slow reading. Longer time to process information.
Aptitude:
Used computers proficiently before but finds completing work tasks more difficult
Attitude:
Proficient but he is prone to frequent seizures and blackouts and finds some sites too stimulating
Adaptive Technology:
System intelligence or processing features such as software agents, reminders and spell checkers, sometimes used in conjunction with adaptations in input and/or output systems. Others: time management software, white noise creator, brain storming software and software to park ideas quickly (quick note), word completion software.

Jacob is 32 years old

He is a college graduate who has completed legal training courses. He shares an apartment with a friend and works as a paralegal, reviewing cases and writing case summaries. He uses a laptop, braille display, and an iPhone. He believes the right technology can allow him to do anything.

Disability Category:
Vision Replacement
Disability:
Blind since birth
Ability:
Has some light perception
Aptitude:
Skilled technology user
Attitude:
Digital native, early adopter, persists until he gets it
Adaptive Technology:
Screen reader, audio note-taker, Braille display.

Lea: 35 years old

Master’s degree. Writes for a trade publication; works from home. No one gets that this really is a disability.

Disability Category:
Mobility and Dexterity Enhancement
Disability:
Fibromyalgia
Ability:
Fatigue from fibromyalgia, trackball, and special keyboard
Aptitude:
Average user
Attitude:
Wishes people would understand how hard it can be for her to make it through the day
Adaptive Technology:
Split keyboard, power keyboard user, Dragon Naturally Speaking.

Steven is 38 years old and attends art school

He is a graphic artist in a small ad agency. He uses an iPad, iPhone and MacBook Pro. He believes everyone should be able to communicate through sign-language.

Disability Category:
Audio Replacement
Disability:
Deaf since birth
Ability:
Native language is American Sign Language (ASL); can speak and read lips; uses SMS/IM, Skype, and video chat
Aptitude:
Good with graphic tools, and prefers visuals to text; poor spelling makes searching more difficult
Attitude:
Can be annoyed about accessibility, such as lack of captions
Adaptive Technology:
Sign language, Communication Access Realtime Translation (CART), captions, video chat.

Nancy is 45 years old.

Has been using computer-based technology for four years, it provides her with independent access to reading materials and written communication.

Disability Category:
Audio Replacement, Vision Replacement
Disability:
Deaf-blind and does not speak. Has limited ASL
Ability:
Able to read grade 2 Braille. Uses telephone with a Braille TTY
Attitude:
She uses manual sign language for two-way communication via an interpreter/facilitator
Attitude:
Can become frustrated easily when the services she requires to communicate are not provided or available
Adaptive Technology:
Screen reader, Braille display, telephone with a Braille TTY, and computer based TTY software.

Vishnu is 48 years old and has an engineering degree

He works for a medical software company on international projects. He was born in India, finished graduate school in Malaysia, and now lives in Singapore. High tech all the way at work; two mobile phones and a personal laptop. I want to be on the same level as everyone else.

Disability Category:
Vision Enhancement
Disability:
Low vision
Ability:
Speaks three languages: Gujarati, Hindi, English, and a little spoken Mandarin. Uses contrast adjustments to see the screen clearly
Aptitude:
Expert user of technical tools; frustrated searching across languages
Attitude:
Sees himself as a world citizen, and wants to be able to use any site
Adaptive Technology:
Contrast adjustments, screen magnification, personalized style sheets

Maria is 49 years old and has a community college and health-care certificate

She is married with grown children and speaks both Spanish and English. She is a community health worker. She has a smartphone, her home computer is primarily her husband’s work computer. She is happy with this set up and assuming she can find what she’s looking for, she loves it.

Disability Category:
Cognitive and Learning Style Enhancement
Disability:
Dyslexia
Ability:
Prefers Spanish language sites, when she can find them; needs information and instructions written clearly
Aptitude:
Adventurous, but not very proficient; husband and daughter set up bookmarks for her
Attitude:
Thinks it’s wonderful to be able to have her favorite websites with her at all times
Adaptive Technology:
Skype, online translation sites

Mary is 52 years old and a college graduate

She lives with her sister and has worked in a dentist office as a receptionist for 20 years. She has lived on disability for the past 5 years.

Disability Category:
Vision Enhancement, Mobility and Dexterity Enhancement
Disability:
Has a chronic progressive course of Multiple Sclerosis. Has motor and sensory impairments
Ability:
She uses a power wheelchair with a joystick control for moving about her environment. Her vision is also extremely limited and fluctuates
Aptitude:
Used computers proficiently before now her physical abilities are extremely limited
Attitude:
Likes to use computers but gets annoyed when she can’t access some features
Adaptive Technology:
She is able to access a computer by targeting one-inch squares on a programmable keyboard, which features large black letters on a white background to access her computer to assist her with typing. On days when her vision is at its lowest, she relies upon motoric memory to access her keyboard. On "good days" she may read print magnified 8x or greater.

Carol is 74 years old and lost her husband a year ago

She lives in an apartment near one of her daughters and a few of her six grandkids (ages 6 to 16). She is retired and worked 25 years as a bookkeeper for a construction company. She has an older computer at home and basic mobile phone. Her grandkids are trying to drag her into the world of technology.

Disability Category:
Vision Enhancement, Audio Enhancement
Disability:
First signs of macular degeneration, mild arthritis; hearing aid
Ability:
No special AT on computer
Aptitude:
Used computers when she worked as a bookkeeper, but now her grandkids keep her old home computer updated
Attitude:
Willing, but not adventurous
Adaptive Technology:
Enlarges text, but makes few other adjustments.

Sample of Government of Canada (GC) employee personas with disabilities

John is a 33 year old art school graduate

He works as a graphic artist inside the Communications Branch at Indigenous and Northern Affairs Canada (INAC). He is fluid with the use of Apple products (iPad, iPhone, MacBook Pro). He feels his only disability is that not everyone in the world can sign.

Disability Category:
Audio Replacement
Disability:
Deaf since birth
Ability:
Native language is ASL; can speak and read lips; uses SMS/IM, Skype, and video chat
Aptitude:
Good with graphic tools/software, is extremely computer literate and prefers visuals to text; Suffers from poor spelling/English grammar which makes searching the web for support more difficult
Attitude:
Has a tendency to become annoyed easily about accessibility, such as lack of captions or subtitles on videos or visual/video learning tutorials
Adaptive Technology:
Sign language, CART, captions, video chat.

Abdul is a 51 year old Structural Engineer with low vision

Abdul holds an Engineering degree that was received with honors. He works for Global Affairs Canada on international projects focused on assisting war torn countries rebuild their infrastructure. He travels constantly and is required to be accessible nearly 24/7. He carries two mobile phones, tablet and work laptop. He also carries a personal laptop. Despite his low vision he strives to be on the same level as everyone else.

Disability Category:
Vision Enhancement
Disability:
Low vision
Ability:
Speaks three languages: Gujarati, Hindi, English, and a little spoken Mandarin. Highly skilled computer user who contrast adjustments to see the screen clearly
Aptitude:
Expert user of technical tools; tends to get frustrated when searching across languages; finds some devices from overseas lacking of adaptive settings
Attitude:
Considers himself a worldly citizen. Wants the ability to use any site when performing his countless hours of research, regardless of language or the fact his PC/Mobile device settings have been individually configured
Adaptive Technology:
Contrast adjustments, screen magnification, personalized style sheets.

Yvette is a 35 year old translator

She holds a Master’s degree in French Language and works as a translator with the Translation Bureau at Public Works and Government Services Canada. She works from home and can spend hours at a time reviewing, revising and translating Government of Canada content from all departments. Her biggest personal issue is that she feels nobody really understands what she goes through physically every day and that she does in fact have a disability.

Disability Category:
Mobility and Dexterity Enhancement
Disability:
Fibromyalgia
Ability:
Fatigue from Fibromyalgia, extreme anxiety when workload increases unexpectedly, hands often cramp or seize up. Uses trackball and a special keyboard to perform daily tasks
Aptitude:
Average computer user with advance Microsoft Office skills
Attitude:
Wishes people would understand how hard it can be for her to make it through the day and complete all assigned projects on time
Adaptive Technology:
Split keyboard, power keyboard user, Dragon Naturally Speaking, pre-programmed X-Keys.

Donald is 21 years old and lives with his family

He has completed secondary school through a specialized program for individuals with Autism and or Attention deficit hyperactivity disorder (ADHD). He learned general computer knowledge in school and has a standard laptop at home and a basic mobile phone with SMS. He was hired as a mailroom assistant with Public Works and Government Services Canada (PWGSC). Donald works best with consistent and familiar routines and processes.

Disability Category:
Cognitive and Learning Style Enhancement;
Disability:
Autism Spectrum Disorder
Ability:
Uses larger text then most on his devices (laptop and standard cell phone) and a program that hides everything but the text, so he doesn’t get distracted
Aptitude:
Uses the computer well for games, but doesn’t learn new sites or software programs easily
Attitude:
Prefers familiar sites online and does best when involved in an established routine
Adaptive Technology:
Text preference settings, power keyboard user.

George is 47 years old and has a Master’s degree in languages

He works for Global Affairs Canada as a translator and lives alone. George has a laptop and an iPhone which he uses daily for both work and personal use. He does not read Braille so most of the information that he receives must be converted to sound since losing his eye sight. George does have a guide dog and also uses a white cane when navigating unfamiliar rooms.

Disability Category:
Vision Replacement
Disability:
Lost his vision at the age of 38 due to other medical issues
Ability:
Has some limited light perception
Aptitude:
Having vision previously he is a skilled technology user
Attitude:
Very eager and open to learn new technology/tools. He is learning to use specialized software to read electronic materials
Adaptive Technology:
Screen reader, audio note-taker.

Brian is 27 years old and is a Seaman with the Royal Canadian Navy

He is away at sea for a minimum of 6 month intervals at a time.

Disability Category:
Audio Enhancement
Disability:
Lost hearing in left ear and 65% in the right ear due to an accident that occurred at sea
Ability:
Functions as an able bodied person with the exception of very poor hearing and on rare occasion slight issues with his balance
Aptitude:
Not being 30 yet he possesses an open mind and is eager to try any form of technology that could make his hearing loss seem less impactful
Adaptive Technology:
Hearing Aid with Telecoil capability.

Remember that people are diverse. Be careful not to assume that all users, including users with disabilities, use your product the same way. People use different interaction techniques, different adaptive strategies, and different assistive technology configurations. People have different experiences, expectations, and different preferences.

References

  1. Policy on the Duty to Accommodate Persons with Disabilities in the Federal Public Service
  2. Persona (user experience)
  3. Accessibility in User-Centered Design: Personas
  4. Standard on Optimizing Websites and Applications for Mobile Devices

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Personas with Disabilities for inclusive user experience (UX) design

The case to include disabilities into user personas, the types of technologies they use, and sample personas with disabilities.

On this page

The purpose of this document is to assist the user in understanding how to build personas with disabilities. Personas are fictional characters created to represent different user types that may use a site, brand, or product in their own particular ways. Developers often design websites and web applications, both desktop and mobile, to their own liking which can potentially cause barriers for some users. It is important to plan for a diverse group of users with a wide range of abilities, technical levels, functional capabilities and familiarity with processes or activities. One important aspect of Inclusive Design is to include people with disabilities in the early design stage and throughout all steps in the software development life-cycle. This will help increase the accessibility and usability components of the end product and better ensure inclusive best practices. This document is a collection of material from a variety of sources geared towards assembling a cohesive view towards inclusion by design.

Creating equal access for everyone

The Government of Canada is committed to delivering information to the public in an accessible format and is equally committed to creating an inclusive, barrier-free work environment that include persons with disabilities. Both obligations require following standards, requirements, guidelines and supporting an extensive use of technology including various adaptive technology tools including software, hardware and devices for users with disabilities.

Users access information through various means: desktop computers, laptops, and mobile devices including smartphones and tablets. In order to keep pace with the demand and provide a satisfactory experience to all users, we should consider 3 different aspects of requirements:

  1. Need for an enterprise level functionality and inclusion requirements, such as:
    1. The functional requirements of end users with disabilities, that include the following Adaptive techniques, tools and technologies:
      1. Vision Enhancement;
      2. Vision Replacement;
      3. Audio Enhancement and Replacement;
      4. Mobility and Dexterity Enhancement and Replacement;
      5. Cognitive and Learning Style Enhancement.
    2. The identified tasks and users abilities.
  2. The design of the applications that make up the solution and how they relate to both:
    1. the operating system manufacturer's own published standards; and
    2. the standards for accessible native applications.
  3. Individual user needs in terms of adaptive technology and built in functionality.

Understanding adaptive techniques, tools and technology

Vision enhancement technology

Vision Enhancement Technology is used by a wide variety of individuals with some form of visual impairment (commonly referred to as "low vision"), where the person still relies on their vision to consume information. The requirements can be quite varied in the manner and level of features required (i.e. someone with a different field of vision will require different settings from someone with glaucoma or a form of color blindness).

The information is often presented differently such as using high contrasting colors, large print or magnification. The system often must be usable with low vision without relying on audio. Low vision is sometimes accompanied by hearing loss. This is especially common in older people. Audio alone as an accessibility strategy will fail to meet the needs of this group. Screen magnification programs (also called large print programs) allow users to enlarge a portion of their screen. This effectively turns the computer monitor into a viewport showing only a portion of an enlarged virtual display. The user can then use the mouse or keyboard commands to move this viewport in order to view different areas of the virtual display.

Vision replacement technology

Vision Replacement Technology is used by individuals with some form of visual impairment (commonly referred to as "blind"), where the person no longer relies or never relied on their vision to consume information. The information is often presented in a different modality such as through Braille or a Text To Speech Engine. Microsoft's Windows, Windows Mobile, Linux, Blackberry OS, Apple Mac OS, iOS, Google's Android and Chrome OS (among others) all have solutions for blind users that make use of screen reader software for a variety of devices. Screen Readers attempt to identify and interpret what is being displayed on the screen. The information is then represented to the user with text-to-speech, sound, haptic icons or a Braille output device. The screen reader keeps track of events that happen (such as windows opening) and actions that are performed on a device with a physical keyboard, D-Pad, Trackball or joystick when movement is performed. On a device with a touch screen, it alters the way the touch screen behaves and provides touch based methods of interaction. There is also Touch Exploration Technology, which allows a blind person to explore the screen with touch without activating the items on the screen. The screen reader can also provide feedback about screen items by providing audio or haptic alerts. It also provides spoken text as controls and information when touched. A set of additional gestures are provided to move around on the screen from item to item and to activate specific screen reader functions (such as reading a block of text).

Audio enhancement and replacement technology

Audio Enhancement and Replacement Technology is used by individuals with some form of hearing impairment or limitation and some users with speech or communication related impairment. There is a wide variety of needs and requirements in this category of technology. Solutions can be as simple as t-coil hearing aid compatibility to as complex as teletypewriter (TTY) access.

Systems often must be usable without hearing. Information conveyed by audio alone is not accessible by individuals who are deaf. Systems often must also be usable with limited hearing. People with limited hearing often cannot see well either, especially people who are older. Allowing them to use their residual hearing is therefore important rather than having to rely on sight (e.g. relying on access techniques that would be used by people who are deaf).

Individuals who do not hear beeps or recognize spoken words may require a program to prompt them in a different manner, such as a screen flash or displaying spoken messages as text or that translate audio cues to visual ones.

Mobility and dexterity enhancement and replacement technology

Mobility and Dexterity Related Technology is used by individuals with some form of physical impairment or limitation. There is a wide variety of needs and requirements in this category of technology. Solutions can be as simple as alternate input such as voice recognition or as complex as scanning with switch access. There are many different kinds of switches on the market that can be used for touching, clicking and dragging operations, in conjunction with a cursor movement device. Switches can also be used to communicate with a device using different coding systems such as Morse code which is helpful to some persons with severe physical disabilities, who use it to input text.

Voice Recognition technology allows the user to control the device and to input text using the voice. Although voice recognition is becoming mainstream, it has always had important applications to the adaptive technology industry. It allows for hands free device use. In addition to being usable by people with differing levels of dexterity or mobility needs, systems must be usable regardless of the severity of the physical impairment. For a person with a physical disability e.g., limited strength, reach or manipulation, tremor, lack of sensation, technology can provide modes of operation that do not require fine motor control or simultaneous actions. Adaptive technology can provide modes that are operable with limited reach, strength and that do not require a response time.

Cognitive and learning style enhancement technology

Cognitive and learning disabilities are neurologically-based processing problems. These processing problems can interfere with learning skills such as reading, writing and/or math. They can also interfere with higher level skills such as organization, time planning, abstract reasoning, long or short-term memory and attention. There is a wide variety of needs and requirements in this category of technology.

Solutions can be as simple as a calendar and task systems or as complex as multi-modal document reading.

Voice Recognition helps persons with dyslexia and dysgraphia that may have difficulty expressing themselves. Additionally, certain typing and writing software that is designed to aid the process of entering information into a computer through the use of tools such as phonetic spell check and advanced thesaurus are commonly used. Usually a combination of screen reading, magnification systems and alternate input devices are used to provide computing access to persons with such impairments.

There are cognitive impairments which take many forms, including Downs Syndrome, short and long-term memory impairments, and perceptual differences. Proper application design can increase functionality of computers for people with mild cognitive impairments.

Visual Stress Syndrome (Concussion) is a neurological condition that interferes with reading, attention, coordination, general health and behaviour, and can occur despite normal vision. Visual Stress occurs when stimuli such as patterns, contrast, light and colour affect the visual cortex, altering brain function and resulting in symptoms of physical discomfort and perceptual distortions. Solutions such as coloured filters have been shown to reduce the effects of these stimuli, calming the stress and restoring brain function.

Certain physical or neurological impairments make speaking difficult for some individuals. Systems that can speak for its user can be used to help individuals with speech impairments. Most of the software packages used for these applications operates with a speech synthesizer.

Breaking down usability barriers

Common problems that users experience while browsing the web and accessing information via technology can be categorized into the following barriers:

It's not simply just about checklists; inclusion is personal and about people. Following the Web Content Accessibility Guidelines (WCAG) 2.0 will make Web content more accessible, however, the important question is, will the content be usable?

Involve users throughout your project

Accessibility should be addressed early in the life cycle of the project; starting from project inception and it should be included in the user-centered design (UCD) processes, including user personas. Our personas should include the different ranges of disabilities. Creating a range of personas, including personas of persons with disabilities, will help developers understand accessibility requirements and implement more universally usable solutions.

Incorporating accessibility needs into personas

Designing personas with disabilities requires special attention as there is a long list of key factors to consider:

Sample of general personas with disabilities

Trevor is 18 years old

He lives with family and goes to secondary school. He uses desktop computers at school, a laptop at home and a basic mobile phone with Short Message Service (SMS). He likes consistent and familiar places on the web.

Disability Category:
Cognitive and Learning Style Enhancement
Disability:
Autism Spectrum Disorder
Ability:
Uses larger text and a program that hides everything but the text, so he doesn’t get distracted
Aptitude:
Uses the computer well for games, but doesn’t learn new sites easily
Attitude:
Prefers familiar sites in an established routine
Adaptive Technology:
Text preference settings, power keyboard user

Emily is 24 years old

She graduated from high school and is working on a college degree. She lives in a small independent living facility and works part-time at a local community center. She wants to do everything for herself.

Disability Category:
Mobility and Dexterity Enhancement and Replacement
Disability:
Cerebral palsy. Difficult to use hands and has some difficulty speaking clearly
Ability:
Uses a motorized wheel chair
Aptitude:
Uses the computer well, with the right input device; good at finding efficient search terms
Attitude:
Wants to do everything for herself; can be impatient
Adaptive Technology:
Augmentative and Alternative Communication (AAC) Communicator with speech generator, iPad, power wheelchair.

Francis is a 30 year old war veteran who lives with his girlfriend

He uses a laptop at home, computers at community centres and libraries, and his iPhone. He works part time at the community centre as a receptionist and finds it difficult to concentrate, remember, manage stress, think, write and speak clearly. He has trouble organizing and managing time. This tends to cause problems for Francis in social and work situations.

Disability Category:
Cognitive and Learning Style Enhancement
Disabilities:
Post Traumatic Stress Disorder (PTSD). Cognitive impairments
Ability:
Slow writing and slow reading. Longer time to process information.
Aptitude:
Used computers proficiently before but finds completing work tasks more difficult
Attitude:
Proficient but he is prone to frequent seizures and blackouts and finds some sites too stimulating
Adaptive Technology:
System intelligence or processing features such as software agents, reminders and spell checkers, sometimes used in conjunction with adaptations in input and/or output systems. Others: time management software, white noise creator, brain storming software and software to park ideas quickly (quick note), word completion software.

Jacob is 32 years old

He is a college graduate who has completed legal training courses. He shares an apartment with a friend and works as a paralegal, reviewing cases and writing case summaries. He uses a laptop, braille display, and an iPhone. He believes the right technology can allow him to do anything.

Disability Category:
Vision Replacement
Disability:
Blind since birth
Ability:
Has some light perception
Aptitude:
Skilled technology user
Attitude:
Digital native, early adopter, persists until he gets it
Adaptive Technology:
Screen reader, audio note-taker, Braille display.

Lea: 35 years old

Master’s degree. Writes for a trade publication; works from home. No one gets that this really is a disability.

Disability Category:
Mobility and Dexterity Enhancement
Disability:
Fibromyalgia
Ability:
Fatigue from fibromyalgia, trackball, and special keyboard
Aptitude:
Average user
Attitude:
Wishes people would understand how hard it can be for her to make it through the day
Adaptive Technology:
Split keyboard, power keyboard user, Dragon Naturally Speaking.

Steven is 38 years old and attends art school

He is a graphic artist in a small ad agency. He uses an iPad, iPhone and MacBook Pro. He believes everyone should be able to communicate through sign-language.

Disability Category:
Audio Replacement
Disability:
Deaf since birth
Ability:
Native language is American Sign Language (ASL); can speak and read lips; uses SMS/IM, Skype, and video chat
Aptitude:
Good with graphic tools, and prefers visuals to text; poor spelling makes searching more difficult
Attitude:
Can be annoyed about accessibility, such as lack of captions
Adaptive Technology:
Sign language, Communication Access Realtime Translation (CART), captions, video chat.

Nancy is 45 years old.

Has been using computer-based technology for four years, it provides her with independent access to reading materials and written communication.

Disability Category:
Audio Replacement, Vision Replacement
Disability:
Deaf-blind and does not speak. Has limited ASL
Ability:
Able to read grade 2 Braille. Uses telephone with a Braille TTY
Attitude:
She uses manual sign language for two-way communication via an interpreter/facilitator
Attitude:
Can become frustrated easily when the services she requires to communicate are not provided or available
Adaptive Technology:
Screen reader, Braille display, telephone with a Braille TTY, and computer based TTY software.

Vishnu is 48 years old and has an engineering degree

He works for a medical software company on international projects. He was born in India, finished graduate school in Malaysia, and now lives in Singapore. High tech all the way at work; two mobile phones and a personal laptop. I want to be on the same level as everyone else.

Disability Category:
Vision Enhancement
Disability:
Low vision
Ability:
Speaks three languages: Gujarati, Hindi, English, and a little spoken Mandarin. Uses contrast adjustments to see the screen clearly
Aptitude:
Expert user of technical tools; frustrated searching across languages
Attitude:
Sees himself as a world citizen, and wants to be able to use any site
Adaptive Technology:
Contrast adjustments, screen magnification, personalized style sheets

Maria is 49 years old and has a community college and health-care certificate

She is married with grown children and speaks both Spanish and English. She is a community health worker. She has a smartphone, her home computer is primarily her husband’s work computer. She is happy with this set up and assuming she can find what she’s looking for, she loves it.

Disability Category:
Cognitive and Learning Style Enhancement
Disability:
Dyslexia
Ability:
Prefers Spanish language sites, when she can find them; needs information and instructions written clearly
Aptitude:
Adventurous, but not very proficient; husband and daughter set up bookmarks for her
Attitude:
Thinks it’s wonderful to be able to have her favorite websites with her at all times
Adaptive Technology:
Skype, online translation sites

Mary is 52 years old and a college graduate

She lives with her sister and has worked in a dentist office as a receptionist for 20 years. She has lived on disability for the past 5 years.

Disability Category:
Vision Enhancement, Mobility and Dexterity Enhancement
Disability:
Has a chronic progressive course of Multiple Sclerosis. Has motor and sensory impairments
Ability:
She uses a power wheelchair with a joystick control for moving about her environment. Her vision is also extremely limited and fluctuates
Aptitude:
Used computers proficiently before now her physical abilities are extremely limited
Attitude:
Likes to use computers but gets annoyed when she can’t access some features
Adaptive Technology:
She is able to access a computer by targeting one-inch squares on a programmable keyboard, which features large black letters on a white background to access her computer to assist her with typing. On days when her vision is at its lowest, she relies upon motoric memory to access her keyboard. On "good days" she may read print magnified 8x or greater.

Carol is 74 years old and lost her husband a year ago

She lives in an apartment near one of her daughters and a few of her six grandkids (ages 6 to 16). She is retired and worked 25 years as a bookkeeper for a construction company. She has an older computer at home and basic mobile phone. Her grandkids are trying to drag her into the world of technology.

Disability Category:
Vision Enhancement, Audio Enhancement
Disability:
First signs of macular degeneration, mild arthritis; hearing aid
Ability:
No special AT on computer
Aptitude:
Used computers when she worked as a bookkeeper, but now her grandkids keep her old home computer updated
Attitude:
Willing, but not adventurous
Adaptive Technology:
Enlarges text, but makes few other adjustments.

Sample of Government of Canada (GC) employee personas with disabilities

John is a 33 year old art school graduate

He works as a graphic artist inside the Communications Branch at Indigenous and Northern Affairs Canada (INAC). He is fluid with the use of Apple products (iPad, iPhone, MacBook Pro). He feels his only disability is that not everyone in the world can sign.

Disability Category:
Audio Replacement
Disability:
Deaf since birth
Ability:
Native language is ASL; can speak and read lips; uses SMS/IM, Skype, and video chat
Aptitude:
Good with graphic tools/software, is extremely computer literate and prefers visuals to text; Suffers from poor spelling/English grammar which makes searching the web for support more difficult
Attitude:
Has a tendency to become annoyed easily about accessibility, such as lack of captions or subtitles on videos or visual/video learning tutorials
Adaptive Technology:
Sign language, CART, captions, video chat.

Abdul is a 51 year old Structural Engineer with low vision

Abdul holds an Engineering degree that was received with honors. He works for Global Affairs Canada on international projects focused on assisting war torn countries rebuild their infrastructure. He travels constantly and is required to be accessible nearly 24/7. He carries two mobile phones, tablet and work laptop. He also carries a personal laptop. Despite his low vision he strives to be on the same level as everyone else.

Disability Category:
Vision Enhancement
Disability:
Low vision
Ability:
Speaks three languages: Gujarati, Hindi, English, and a little spoken Mandarin. Highly skilled computer user who contrast adjustments to see the screen clearly
Aptitude:
Expert user of technical tools; tends to get frustrated when searching across languages; finds some devices from overseas lacking of adaptive settings
Attitude:
Considers himself a worldly citizen. Wants the ability to use any site when performing his countless hours of research, regardless of language or the fact his PC/Mobile device settings have been individually configured
Adaptive Technology:
Contrast adjustments, screen magnification, personalized style sheets.

Yvette is a 35 year old translator

She holds a Master’s degree in French Language and works as a translator with the Translation Bureau at Public Works and Government Services Canada. She works from home and can spend hours at a time reviewing, revising and translating Government of Canada content from all departments. Her biggest personal issue is that she feels nobody really understands what she goes through physically every day and that she does in fact have a disability.

Disability Category:
Mobility and Dexterity Enhancement
Disability:
Fibromyalgia
Ability:
Fatigue from Fibromyalgia, extreme anxiety when workload increases unexpectedly, hands often cramp or seize up. Uses trackball and a special keyboard to perform daily tasks
Aptitude:
Average computer user with advance Microsoft Office skills
Attitude:
Wishes people would understand how hard it can be for her to make it through the day and complete all assigned projects on time
Adaptive Technology:
Split keyboard, power keyboard user, Dragon Naturally Speaking, pre-programmed X-Keys.

Donald is 21 years old and lives with his family

He has completed secondary school through a specialized program for individuals with Autism and or Attention deficit hyperactivity disorder (ADHD). He learned general computer knowledge in school and has a standard laptop at home and a basic mobile phone with SMS. He was hired as a mailroom assistant with Public Works and Government Services Canada (PWGSC). Donald works best with consistent and familiar routines and processes.

Disability Category:
Cognitive and Learning Style Enhancement;
Disability:
Autism Spectrum Disorder
Ability:
Uses larger text then most on his devices (laptop and standard cell phone) and a program that hides everything but the text, so he doesn’t get distracted
Aptitude:
Uses the computer well for games, but doesn’t learn new sites or software programs easily
Attitude:
Prefers familiar sites online and does best when involved in an established routine
Adaptive Technology:
Text preference settings, power keyboard user.

George is 47 years old and has a Master’s degree in languages

He works for Global Affairs Canada as a translator and lives alone. George has a laptop and an iPhone which he uses daily for both work and personal use. He does not read Braille so most of the information that he receives must be converted to sound since losing his eye sight. George does have a guide dog and also uses a white cane when navigating unfamiliar rooms.

Disability Category:
Vision Replacement
Disability:
Lost his vision at the age of 38 due to other medical issues
Ability:
Has some limited light perception
Aptitude:
Having vision previously he is a skilled technology user
Attitude:
Very eager and open to learn new technology/tools. He is learning to use specialized software to read electronic materials
Adaptive Technology:
Screen reader, audio note-taker.

Brian is 27 years old and is a Seaman with the Royal Canadian Navy

He is away at sea for a minimum of 6 month intervals at a time.

Disability Category:
Audio Enhancement
Disability:
Lost hearing in left ear and 65% in the right ear due to an accident that occurred at sea
Ability:
Functions as an able bodied person with the exception of very poor hearing and on rare occasion slight issues with his balance
Aptitude:
Not being 30 yet he possesses an open mind and is eager to try any form of technology that could make his hearing loss seem less impactful
Adaptive Technology:
Hearing Aid with Telecoil capability.

Remember that people are diverse. Be careful not to assume that all users, including users with disabilities, use your product the same way. People use different interaction techniques, different adaptive strategies, and different assistive technology configurations. People have different experiences, expectations, and different preferences.

References

  1. Policy on the Duty to Accommodate Persons with Disabilities in the Federal Public Service
  2. Persona (user experience)
  3. Accessibility in User-Centered Design: Personas
  4. Standard on Optimizing Websites and Applications for Mobile Devices

Page details

Date modified:
\ No newline at end of file diff --git a/en/research-on-our-target-audience/index.html b/en/research-on-our-target-audience/index.html index f65be3cf6..ef87413be 100644 --- a/en/research-on-our-target-audience/index.html +++ b/en/research-on-our-target-audience/index.html @@ -1,4 +1,4 @@ -Research on our target audience - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Research on our target audience

The main goal of creating these personas was to better understand our target audience. By developing a greater understanding of our users. By developing a greater understanding of our users, we would be able to build a responsive site architecture for all existing and future content hosted on the Digital Accessibility Toolkit’s website.

The creation of our persona

The main goal of creating these personas was to better understand our target audience. By developing a greater understanding of our users. By developing a greater understanding of our users, we would be able to build a responsive site architecture for all existing and future content hosted on the Digital Accessibility Toolkit’s website.

To do this we must:

Framework

Our approach is modular: we combined two types of persona to create a template that better represents our target audience. We used the two following framework:

Target user persona

Accessibility persona

Disability types and inclusivity

In our personas, we included a variety of disabilities and a spectrum of limitations:

We believe it is important to account for a wide range of human experiences. This is why for each disability type we included different possibilities of exclusion.

Seven (7) Persona

5 broad disability types and 2 combined disability types

Brandon – Auditory

About

Pronouns
He/Him
Age
52
Job
User Experience (UX).
Commonly used sites
IAAP, CSPS.
Disability:
Deaf since birth.

Example of Temporary or situational

  • Temporary hearing loss due to an ear infection in the right ear.
  • Construction noise.

Skills (aptitude)

  • Tech-savvy and able to picks up new software quickly.
  • Knows sign-language.

Tools (adaptive technology, devices, other)

Category: audio replacement and enhancement.

  • Live closed captioning in meetings.
  • Other: Transcripts during/post-event.

Needs (tasks, environments)

  • Prefers the option to work from home.
  • Requires access to his laptop daily for work.
  • Often asks for instructions or conversations to be repeated to him.

Barriers & frustrations (specifics, attitudes)

  • It can be really frustrating when tools lag or aren't available.
  • Web-based services and applications that rely on interactions using voice-only commands are really difficult or sometimes not possible to use.
  • Group meetings, back-to-back meetings, or just too many meetings in a day can be draining.

Quote:

“When music is playing while a speaker is speaking, it’s very distracting. WCAG 2.1 has a criterion that says background noise has to be certain decibels below the speaker’s voice but it’s an AAA level. This means it’s not mandatory for companies and organizations to comply with this criterion.”

Alasie - Vision

About

Pronouns
She/Her
Age
23
Job
Junior accessibility tester.
Commonly used sites
W3C and Deque.
Disability:
Blurred vision with low contrast.

Example of Temporary or situational

  • Brightness from the sun.

Skills (aptitude)

  • Solid understanding of assistive technology used for web browsing.
  • Highly skilled computer user who uses contrast adjustments to see the screen clearly.

Tools (adaptive technology, devices, other)

Category: Vision Enhancements

  • Colour adjustments.
  • Automated web accessibility checker.
  • Microsoft Teams.
  • Screen reader.
  • Word processing software.
  • Screen magnification.

Needs (tasks, environments)

  • Requires access to web and document accessibility guidelines when conducting tests.
  • Adequate testing time for Information and communications technology (ICT) accessibility in the GC.
  • Digital files to be available in accessible formats.

Barriers & frustrations (specifics, attitudes)

  • Loss of web content or functionality when font size or browser screen is resized.
  • Low contrast text can be hard to read.
  • Images on websites that do not provide text alternatives.
  • Speakers who do not provide information that help understand information displayed visually.

Quote:

“It's really annoying when the colours of the text and background are so close to each other, it makes anything on the screen hard to read.”

Yenah - Dexterity

About

Pronouns
She/Her.
Age
52
Job
Front-end developer.
Commonly used sites
WCAG for developers.
Disability:
Fibromyalgia.

Example of Temporary or situational

  • Inflammatory arthritis.
  • Bumpy car ride.

Skills (aptitude)

  • Uses macbook and apple products daily for her job.
  • Techsavvy and relies on her tools in her day-to-day life.

Tools (adaptive technology, devices, other)

Category: Mobility and Dexterity Enhancement.

  • Ergonomic keyboard, mouse.
  • Dragon Naturally Speaking.
  • Pre-programmed X-Keys.
  • Voice recognition software.

Needs (tasks, environments)

  • Prefers accommodations and flexibility in work schedule to account for rest, medical support, preferred working styles.
  • Understanding from their team for the varying levels of discomfort that may occur each day.
  • Simple pointer gestures when navigating through webpages (ex: single-click/tap).
  • Links with proper names to clearly indicate where the link leads to and what its purpose is.

Barriers & frustrations (specifics, attitudes)

  • Distractions in the workplace.
  • Workplace policies that make work from home accommodations difficult to get.
  • When alternative interaction patterns are not available and the required action is difficult to complete (ex: shaking a device, pinching, drawing, etc).

Quote:

“The buttons on my phone screen can be so small, I want to hit a checkbox but accidentally click another option, I have to uncheck the wrong one to proceed but it’s frustrating.”

Ike - Mobility

About

Pronouns
They/Them.
Age
31
Job
Trainer / Educator.
Commonly used sites
AAACT, GcPedia, DAT.
Disability:
Motor Neurone Disease.

Example of Temporary or situational

  • Holding a baby.
  • Fracturing a limb.

Skills (aptitude)

  • Has experience providing training on web and document accessibility.

Tools (adaptive technology, devices, other)

Category: Mobility Enhancements.

  • Speech recognition device.
  • Power wheelchair.
  • Adjustable monitors.
  • Adaptive keyboards.

Needs (tasks, environments)

  • Information about how to acquire workplace accommodations due to mandatory return to office policies.
  • Standard method to provide trainees with resources on accessibility standards, policies and requirements within GC.
  • Ability to view web content in both portrait and landscape orientation.

Barriers & frustrations (specifics, attitudes)

  • Difficulty booking a workspace through the designated web application.
  • Difficulty finding accessible routes outside and within buildings.
  • Buildings without an automatic door button.
  • Obstructions on accessible routes including ramps and corridors.

Quote:

”I cannot book a workspace like everyone else does because the application does not support keyboard navigation.”

Damien - Cognitive

About

Pronouns
He/Him.
Age
48
Job
Manager in communications.
Commonly used sites
Deque.
Disability:
Autism spectrum disorder, Dyslexia.

Example of Temporary or situational

  • Sustaining a Concussion.

Skills (aptitude)

  • Relies on calendar, timetables, and organizational apps on desktop and mobile.
  • Prefers having the option to customize my environment (ex: tools and tech, room light and temperature, monitor display, etc.)

Tools (adaptive technology, devices, other)

Category: Cognitive and Learning Style Enhancement.

  • Text preference settings, power keyboard user.
  • Text to speech software.

Needs (tasks, environments)

  • Works best with consistent and familiar routines and processes.
  • When communicating, terms used in conversations must be literal, clear, and to the point.
  • Hopes people understand neurodiversity diagnoses are unique, 1 person’s needs may be different from another person with the same disability.
  • Sites with multiple pathways of navigations to make the site easier to use.

Barriers & frustrations (specifics, attitudes)

  • Not great with socializing, like small talk, eye contact, picking up subtle hints/cues, and physical touch.
  • Often deals with headaches and migraines.

Quote:

“When I’m using a website, I find it frustrating when there is no consistency in page layouts and some terminologies to confirm my actions can be difficult to understand.”

Valeria – Cognitive and Auditory

About

Pronouns
She/Her.
Age
62
Job
Administrative Services Officer.
Commonly used sites
Salesforce, IAAP, DAT.
Disability:
ADHD, anxiety-disorder, severe hearing loss, hear sounds but can’t distinguish speech

Example of Temporary or situational

  • Users who aren’t familiar with the internet.
  • Non-native speakers.

Skills (aptitude)

  • Works best with consistent and familiar routines and processes.
  • Skilled in Microsoft Office applications.

Tools (adaptive technology, devices, other)

Category: Cognitive and Learning Style Enhancement and others.

  • Screen reader.
  • Zoom magnifier.
  • Password manager.

Needs (tasks, environments)

  • Enjoys working with automated tools like autofill/complete that can help fill in information quickly and helps users to remember all their different account information.
  • Often works in spaces in the office with privacy and low volume policies to help eliminate distractions and facilitate deep focus work.
  • Use of simple, plain language, free of acronyms, metaphors, slangs, explanatory instructions, and descriptive images.

Barriers & frustrations (specifics, attitudes)

  • Not being able to lip-read and see facial expressions when people have cameras turned off during a video call.
  • Use of captions that are inaccurate or non-customizable.

Quote:

“When I fill out a form online, it’s difficult to complete the task within the given time. It is even more frustrating when I don’t know how much time I have, the site times out and deletes my work, and I have to redo the form all over again.”

Yosef – Mobility and Speech

About

Pronouns
He/Him.
Age
39
Job
Administrative Support and Program Officer.
Commonly used sites
GCdocs, GCXchange, DAT.
Disability:
Muscle fatigue and slurred speech.

Example of Temporary or situational

  • Repetitive stress injury and cannot speak in certain situations due to anxiety.
  • Recovering from a concussion.

Skills (aptitude)

  • Experience reviewing information and extracting critical information.
  • Often requires repeated exposure to content to understand it.

Tools (adaptive technology, devices, other)

Category: Mobility and Speech replacement or enhancements.

  • Text preference settings, power keyboard user.
  • Text to speech software. Text-to-speech software.
  • Spell checkers.
  • Ergonomic keyboard and mouse.
  • Templates and organizational tools.

Needs (tasks, environments)

  • Websites and browsers that provide full keyboard support and provide options to skip to main sections of the page.
  • Alternative means of communication that do not rely heavily on speech. For example, text-based chat, email and feedback form.
  • Must use an ergonomic keyboard and mouse for daily office use.

Barriers & frustrations (specifics, attitudes)

  • Web content that cannot be accessed using a keyboard.
  • Insufficient time limits to complete tasks like completing a web form.
  • Support and help centers that offer phone numbers as the only way to communicate with their organization.

Quote:

“It can be very tiring to have to tab through irrelevant material to reach the content need.”

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Research on our target audience

The main goal of creating these personas was to better understand our target audience. By developing a greater understanding of our users. By developing a greater understanding of our users, we would be able to build a responsive site architecture for all existing and future content hosted on the Digital Accessibility Toolkit’s website.

The creation of our persona

The main goal of creating these personas was to better understand our target audience. By developing a greater understanding of our users. By developing a greater understanding of our users, we would be able to build a responsive site architecture for all existing and future content hosted on the Digital Accessibility Toolkit’s website.

To do this we must:

Framework

Our approach is modular: we combined two types of persona to create a template that better represents our target audience. We used the two following framework:

Target user persona

Accessibility persona

Disability types and inclusivity

In our personas, we included a variety of disabilities and a spectrum of limitations:

We believe it is important to account for a wide range of human experiences. This is why for each disability type we included different possibilities of exclusion.

Seven (7) Persona

5 broad disability types and 2 combined disability types

Brandon – Auditory

About

Pronouns
He/Him
Age
52
Job
User Experience (UX).
Commonly used sites
IAAP, CSPS.
Disability:
Deaf since birth.

Example of Temporary or situational

  • Temporary hearing loss due to an ear infection in the right ear.
  • Construction noise.

Skills (aptitude)

  • Tech-savvy and able to picks up new software quickly.
  • Knows sign-language.

Tools (adaptive technology, devices, other)

Category: audio replacement and enhancement.

  • Live closed captioning in meetings.
  • Other: Transcripts during/post-event.

Needs (tasks, environments)

  • Prefers the option to work from home.
  • Requires access to his laptop daily for work.
  • Often asks for instructions or conversations to be repeated to him.

Barriers & frustrations (specifics, attitudes)

  • It can be really frustrating when tools lag or aren't available.
  • Web-based services and applications that rely on interactions using voice-only commands are really difficult or sometimes not possible to use.
  • Group meetings, back-to-back meetings, or just too many meetings in a day can be draining.

Quote:

“When music is playing while a speaker is speaking, it’s very distracting. WCAG 2.1 has a criterion that says background noise has to be certain decibels below the speaker’s voice but it’s an AAA level. This means it’s not mandatory for companies and organizations to comply with this criterion.”

Alasie - Vision

About

Pronouns
She/Her
Age
23
Job
Junior accessibility tester.
Commonly used sites
W3C and Deque.
Disability:
Blurred vision with low contrast.

Example of Temporary or situational

  • Brightness from the sun.

Skills (aptitude)

  • Solid understanding of assistive technology used for web browsing.
  • Highly skilled computer user who uses contrast adjustments to see the screen clearly.

Tools (adaptive technology, devices, other)

Category: Vision Enhancements

  • Colour adjustments.
  • Automated web accessibility checker.
  • Microsoft Teams.
  • Screen reader.
  • Word processing software.
  • Screen magnification.

Needs (tasks, environments)

  • Requires access to web and document accessibility guidelines when conducting tests.
  • Adequate testing time for Information and communications technology (ICT) accessibility in the GC.
  • Digital files to be available in accessible formats.

Barriers & frustrations (specifics, attitudes)

  • Loss of web content or functionality when font size or browser screen is resized.
  • Low contrast text can be hard to read.
  • Images on websites that do not provide text alternatives.
  • Speakers who do not provide information that help understand information displayed visually.

Quote:

“It's really annoying when the colours of the text and background are so close to each other, it makes anything on the screen hard to read.”

Yenah - Dexterity

About

Pronouns
She/Her.
Age
52
Job
Front-end developer.
Commonly used sites
WCAG for developers.
Disability:
Fibromyalgia.

Example of Temporary or situational

  • Inflammatory arthritis.
  • Bumpy car ride.

Skills (aptitude)

  • Uses macbook and apple products daily for her job.
  • Techsavvy and relies on her tools in her day-to-day life.

Tools (adaptive technology, devices, other)

Category: Mobility and Dexterity Enhancement.

  • Ergonomic keyboard, mouse.
  • Dragon Naturally Speaking.
  • Pre-programmed X-Keys.
  • Voice recognition software.

Needs (tasks, environments)

  • Prefers accommodations and flexibility in work schedule to account for rest, medical support, preferred working styles.
  • Understanding from their team for the varying levels of discomfort that may occur each day.
  • Simple pointer gestures when navigating through webpages (ex: single-click/tap).
  • Links with proper names to clearly indicate where the link leads to and what its purpose is.

Barriers & frustrations (specifics, attitudes)

  • Distractions in the workplace.
  • Workplace policies that make work from home accommodations difficult to get.
  • When alternative interaction patterns are not available and the required action is difficult to complete (ex: shaking a device, pinching, drawing, etc).

Quote:

“The buttons on my phone screen can be so small, I want to hit a checkbox but accidentally click another option, I have to uncheck the wrong one to proceed but it’s frustrating.”

Ike - Mobility

About

Pronouns
They/Them.
Age
31
Job
Trainer / Educator.
Commonly used sites
(AAACT), GcPedia, title="Digital Accessibility Toolkit">DAT.
Disability:
Motor Neurone Disease.

Example of Temporary or situational

  • Holding a baby.
  • Fracturing a limb.

Skills (aptitude)

  • Has experience providing training on web and document accessibility.

Tools (adaptive technology, devices, other)

Category: Mobility Enhancements.

  • Speech recognition device.
  • Power wheelchair.
  • Adjustable monitors.
  • Adaptive keyboards.

Needs (tasks, environments)

  • Information about how to acquire workplace accommodations due to mandatory return to office policies.
  • Standard method to provide trainees with resources on accessibility standards, policies and requirements within GC.
  • Ability to view web content in both portrait and landscape orientation.

Barriers & frustrations (specifics, attitudes)

  • Difficulty booking a workspace through the designated web application.
  • Difficulty finding accessible routes outside and within buildings.
  • Buildings without an automatic door button.
  • Obstructions on accessible routes including ramps and corridors.

Quote:

”I cannot book a workspace like everyone else does because the application does not support keyboard navigation.”

Damien - Cognitive

About

Pronouns
He/Him.
Age
48
Job
Manager in communications.
Commonly used sites
Deque.
Disability:
Autism spectrum disorder, Dyslexia.

Example of Temporary or situational

  • Sustaining a Concussion.

Skills (aptitude)

  • Relies on calendar, timetables, and organizational apps on desktop and mobile.
  • Prefers having the option to customize my environment (ex: tools and tech, room light and temperature, monitor display, etc.)

Tools (adaptive technology, devices, other)

Category: Cognitive and Learning Style Enhancement.

  • Text preference settings, power keyboard user.
  • Text to speech software.

Needs (tasks, environments)

  • Works best with consistent and familiar routines and processes.
  • When communicating, terms used in conversations must be literal, clear, and to the point.
  • Hopes people understand neurodiversity diagnoses are unique, 1 person’s needs may be different from another person with the same disability.
  • Sites with multiple pathways of navigations to make the site easier to use.

Barriers & frustrations (specifics, attitudes)

  • Not great with socializing, like small talk, eye contact, picking up subtle hints/cues, and physical touch.
  • Often deals with headaches and migraines.

Quote:

“When I’m using a website, I find it frustrating when there is no consistency in page layouts and some terminologies to confirm my actions can be difficult to understand.”

Valeria – Cognitive and Auditory

About

Pronouns
She/Her.
Age
62
Job
Administrative Services Officer.
Commonly used sites
Salesforce, IAAP, DAT.
Disability:
ADHD, anxiety-disorder, severe hearing loss, hear sounds but can’t distinguish speech

Example of Temporary or situational

  • Users who aren’t familiar with the internet.
  • Non-native speakers.

Skills (aptitude)

  • Works best with consistent and familiar routines and processes.
  • Skilled in Microsoft Office applications.

Tools (adaptive technology, devices, other)

Category: Cognitive and Learning Style Enhancement and others.

  • Screen reader.
  • Zoom magnifier.
  • Password manager.

Needs (tasks, environments)

  • Enjoys working with automated tools like autofill/complete that can help fill in information quickly and helps users to remember all their different account information.
  • Often works in spaces in the office with privacy and low volume policies to help eliminate distractions and facilitate deep focus work.
  • Use of simple, plain language, free of acronyms, metaphors, slangs, explanatory instructions, and descriptive images.

Barriers & frustrations (specifics, attitudes)

  • Not being able to lip-read and see facial expressions when people have cameras turned off during a video call.
  • Use of captions that are inaccurate or non-customizable.

Quote:

“When I fill out a form online, it’s difficult to complete the task within the given time. It is even more frustrating when I don’t know how much time I have, the site times out and deletes my work, and I have to redo the form all over again.”

Yosef – Mobility and Speech

About

Pronouns
He/Him.
Age
39
Job
Administrative Support and Program Officer.
Commonly used sites
GCdocs, GCXchange, DAT.
Disability:
Muscle fatigue and slurred speech.

Example of Temporary or situational

  • Repetitive stress injury and cannot speak in certain situations due to anxiety.
  • Recovering from a concussion.

Skills (aptitude)

  • Experience reviewing information and extracting critical information.
  • Often requires repeated exposure to content to understand it.

Tools (adaptive technology, devices, other)

Category: Mobility and Speech replacement or enhancements.

  • Text preference settings, power keyboard user.
  • Text to speech software. Text-to-speech software.
  • Spell checkers.
  • Ergonomic keyboard and mouse.
  • Templates and organizational tools.

Needs (tasks, environments)

  • Websites and browsers that provide full keyboard support and provide options to skip to main sections of the page.
  • Alternative means of communication that do not rely heavily on speech. For example, text-based chat, email and feedback form.
  • Must use an ergonomic keyboard and mouse for daily office use.

Barriers & frustrations (specifics, attitudes)

  • Web content that cannot be accessed using a keyboard.
  • Insufficient time limits to complete tasks like completing a web form.
  • Support and help centers that offer phone numbers as the only way to communicate with their organization.

Quote:

“It can be very tiring to have to tab through irrelevant material to reach the content need.”

Page details

Date modified:
\ No newline at end of file diff --git a/en/statistics-canada-statcan/index.html b/en/statistics-canada-statcan/index.html index 11d6b6b6b..6f5860676 100644 --- a/en/statistics-canada-statcan/index.html +++ b/en/statistics-canada-statcan/index.html @@ -1,4 +1,4 @@ -Statistics Canada (StatCan) - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Statistics Canada (StatCan)

Statistics Canada, in collaboration with partners from Employment and Social Development Canada, will continue to develop and release products to better understand the accessibility experiences of Canadians. The Accessibility Data Hub provides a centralized location of topics related to accessibility and disability through data tables, articles, infographics and interactive data visualization tools.

StatCan Accessibility Secretariat

The Accessibility Secretariat is a StatCan internal central support hub for divisions across StatCan to build their understanding and capacity for accessibility. They support a dynamic relationship with employees, respondents, and data users with disabilities. They also lead the development of plans and reports that meet the requirements of the Accessible Canada Act and the objectives defined by the agency based on those set out in the act and those refined by the Office of Public Services’ Accessibility Strategy.

Centre of Expertise on Accessibility (CEA)

The Centre of Expertise on Accessibility offers expertise on accessibility internally to StatCan to ensure that all Canadians have equal access regardless of their abilities, official languages and adaptive technologies. The team assesses compliance with international World Wide Web Consortium (W3C) accessibility guidelines, provides advice, feedback and proposed solutions to common Government of Canada web accessibility issues, tests how a product is viewed and functions with screen-reader software and other adaptive technologies such as JAWS, NVDA and Braille display, produces alternate formats on request (multiple formats — Braille/audio), and promotes awareness and alignment of current best practices and technologies of users’ web experience with different types of disabilities.

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Statistics Canada (StatCan)

Statistics Canada, in collaboration with partners from Employment and Social Development Canada, will continue to develop and release products to better understand the accessibility experiences of Canadians. The Accessibility Data Hub provides a centralized location of topics related to accessibility and disability through data tables, articles, infographics and interactive data visualization tools.

StatCan Accessibility Secretariat

The Accessibility Secretariat is a StatCan internal central support hub for divisions across StatCan to build their understanding and capacity for accessibility. They support a dynamic relationship with employees, respondents, and data users with disabilities. They also lead the development of plans and reports that meet the requirements of the Accessible Canada Act and the objectives defined by the agency based on those set out in the act and those refined by the Office of Public Services’ Accessibility Strategy.

Centre of Expertise on Accessibility (CEA)

The Centre of Expertise on Accessibility offers expertise on accessibility internally to StatCan to ensure that all Canadians have equal access regardless of their abilities, official languages and adaptive technologies. The team assesses compliance with international World Wide Web Consortium (W3C) accessibility guidelines, provides advice, feedback and proposed solutions to common Government of Canada web accessibility issues, tests how a product is viewed and functions with screen-reader software and other adaptive technologies such as JAWS, NVDA and Braille display, produces alternate formats on request (multiple formats — Braille/audio), and promotes awareness and alignment of current best practices and technologies of users’ web experience with different types of disabilities.

Page details

Date modified:
\ No newline at end of file diff --git a/en/terms-of-reference/index.html b/en/terms-of-reference/index.html index ae1a6f071..bf4e50119 100644 --- a/en/terms-of-reference/index.html +++ b/en/terms-of-reference/index.html @@ -1,4 +1,4 @@ -Terms of Reference - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Terms of Reference

Terms of Reference define the purpose and scope of the Digital Accessibility Toolkit project. It includes information regarding the structures of a project, key roles, membership, meeting, and more.

On this page

Purpose

The purpose of this task force is to collaborate on the creation of a structured platform to centralize Government of Canada (GC) information on accessibility.

The Access Working Group (AWG) would like to enable interdepartmental centralization and sharing of accessibility information produced by GC departments in a central repository and sharing space.

Sharing accessibility resources and work in a central repository would, among other benefits:

Key roles

The Digital Accessibility Toolkit (DAT) task force supports the Public Service Accessibility Strategy Goal 3: Technology Make information and communications technology usable by all.

This task force will:

  1. provide recommendations for creating the Government of Canada (GC) central repository for GC created accessibility resources and work;
  2. support the implementation through various phases of work; and
  3. discuss and initiate supporting activities to identify which information / materials would be appropriate to shared.

The Digital Accessibility Toolkit (DAT) will leverage accessibility expertise across government, showcase best practices, and promote inclusive design and accessible by default.

The key roles will be defined based on the World Wide Web Consortium's (W3C) ARRM Project - Accessibility Roles and Responsibilities Mapping project.

Reporting structure

Co-chairs will be leaders in the accessibility community within the Government of Canada (GC). The chair(s) may change over time as appropriate.

The Digital Accessibility Toolkit (DAT) operates under the umbrella of the Access Working Group (AWG) and will make periodic reports to that working group.

Mandate and decision-making authority

The Digital Accessibility Toolkit (DAT) is a recommendation-making forum that has a mandate to:

Membership

Digital Accessibility Toolkit (DAT) members belong to multiple stakeholder departments who have knowledge in digital accessibility.

Members

Operating procedures and frequency of meetings

This task force meets weekly, or as required. Agendas will be prepared for each meeting and meeting materials will be circulated in advance of the meetings. Members are invited at all times to add agenda items.

Members are expected to be working members, drafting and editing materials and making recommendations.

In the event that the member is unavailable for a scheduled meeting, the member may appoint an alternate who has equivalent background and/or knowledge of the subject being discussed.

A brief summary of the project progress will be provided at minimum at every other Access Working Group (AWG) meeting.

The methods of contributing could be as done in one or more of the following ways:

  1. Github discussion in the open;
    1. GitHub,
    2. email, or
    3. anonymously via web form.
  2. Task force meetings

Final decisions will be published on the Github discussion.

The Terms of Reference will be reviewed at minimum annually and adjusted as required.

Scope

While ideally the project have a four phases approach, the focus of this task force will be on Phase 1 as early as 2023.

Phase 1: Site Architecture

What to post, how to organize, publishing procedures, maintenance cycle, documenting process.

Phase 2: Publishing

Authoring tool / Content Management System (CMS)

Phase 3: Expand

Expanding the various topics and subjects or adding new topics

Phase 4: Maintenance cycle

Establishing a proper maintenance cycle, including the review of the current content, adding new content, and testing the functionality and accessibility of the site.

Resources

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Terms of Reference

Terms of Reference define the purpose and scope of the Digital Accessibility Toolkit project. It includes information regarding the structures of a project, key roles, membership, meeting, and more.

On this page

Purpose

The purpose of this task force is to collaborate on the creation of a structured platform to centralize Government of Canada (GC) information on accessibility.

The Access Working Group (AWG) would like to enable interdepartmental centralization and sharing of accessibility information produced by GC departments in a central repository and sharing space.

Sharing accessibility resources and work in a central repository would, among other benefits:

Key roles

The Digital Accessibility Toolkit (DAT) task force supports the Public Service Accessibility Strategy Goal 3: Technology Make information and communications technology usable by all.

This task force will:

  1. provide recommendations for creating the Government of Canada (GC) central repository for GC created accessibility resources and work;
  2. support the implementation through various phases of work; and
  3. discuss and initiate supporting activities to identify which information / materials would be appropriate to shared.

The Digital Accessibility Toolkit (DAT) will leverage accessibility expertise across government, showcase best practices, and promote inclusive design and accessible by default.

The key roles will be defined based on the World Wide Web Consortium's (W3C) ARRM Project - Accessibility Roles and Responsibilities Mapping project.

Reporting structure

Co-chairs will be leaders in the accessibility community within the Government of Canada (GC). The chair(s) may change over time as appropriate.

The Digital Accessibility Toolkit (DAT) operates under the umbrella of the Access Working Group (AWG) and will make periodic reports to that working group.

Mandate and decision-making authority

The Digital Accessibility Toolkit (DAT) is a recommendation-making forum that has a mandate to:

Membership

Digital Accessibility Toolkit (DAT) members belong to multiple stakeholder departments who have knowledge in digital accessibility.

Members

Operating procedures and frequency of meetings

This task force meets weekly, or as required. Agendas will be prepared for each meeting and meeting materials will be circulated in advance of the meetings. Members are invited at all times to add agenda items.

Members are expected to be working members, drafting and editing materials and making recommendations.

In the event that the member is unavailable for a scheduled meeting, the member may appoint an alternate who has equivalent background and/or knowledge of the subject being discussed.

A brief summary of the project progress will be provided at minimum at every other Access Working Group (AWG) meeting.

The methods of contributing could be as done in one or more of the following ways:

  1. Github discussion in the open;
    1. GitHub,
    2. email, or
    3. anonymously via web form.
  2. Task force meetings

Final decisions will be published on the Github discussion.

The Terms of Reference will be reviewed at minimum annually and adjusted as required.

Scope

While ideally the project have a four phases approach, the focus of this task force will be on Phase 1 as early as 2023.

Phase 1: Site Architecture

What to post, how to organize, publishing procedures, maintenance cycle, documenting process.

Phase 2: Publishing

Authoring tool / Content Management System (CMS)

Phase 3: Expand

Expanding the various topics and subjects or adding new topics

Phase 4: Maintenance cycle

Establishing a proper maintenance cycle, including the review of the current content, adding new content, and testing the functionality and accessibility of the site.

Resources

Page details

Date modified:
\ No newline at end of file diff --git a/en/the-structure-of-web-content-accessibility-guidelines-wcag-2-1/index.html b/en/the-structure-of-web-content-accessibility-guidelines-wcag-2-1/index.html index 8d2ee45fd..8d6cad503 100644 --- a/en/the-structure-of-web-content-accessibility-guidelines-wcag-2-1/index.html +++ b/en/the-structure-of-web-content-accessibility-guidelines-wcag-2-1/index.html @@ -1,4 +1,4 @@ -The structure of Web Content Accessibility Guidelines (WCAG) 2.1 - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

The structure of Web Content Accessibility Guidelines (WCAG) 2.1

Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities.

Principle 1 – Perceivable

Guideline 1.1 – Text Alternatives

Guideline 1.2 – Time-Based Media

Guideline 1.3 – Adaptable

Guideline 1.4 – Distinguishable

Principle 2 – Operable

Guideline 2.1 – Keyboard Accessible

Guideline 2.2 – Enough Time

Guideline 2.3 – Seizures

Guideline 2.4 – Navigable

Guideline 2.5 – Input Modalities

Principle 3 – Understandable

Guideline 3.1 – Readable

Guideline 3.2 – Predictable

Guideline 3.3 – Input Assistance

Principle 4 – Robust

Guideline 4.1 – Compatible

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

The structure of Web Content Accessibility Guidelines (WCAG) 2.1

Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities.

Principle 1 – Perceivable

Guideline 1.1 – Text Alternatives

Guideline 1.2 – Time-Based Media

Guideline 1.3 – Adaptable

Guideline 1.4 – Distinguishable

Principle 2 – Operable

Guideline 2.1 – Keyboard Accessible

Guideline 2.2 – Enough Time

Guideline 2.3 – Seizures

Guideline 2.4 – Navigable

Guideline 2.5 – Input Modalities

Principle 3 – Understandable

Guideline 3.1 – Readable

Guideline 3.2 – Predictable

Guideline 3.3 – Input Assistance

Principle 4 – Robust

Guideline 4.1 – Compatible

Page details

Date modified:
\ No newline at end of file diff --git a/en/universal-design-for-learning-udl/index.html b/en/universal-design-for-learning-udl/index.html index 7d6d482b3..7ddd26a01 100644 --- a/en/universal-design-for-learning-udl/index.html +++ b/en/universal-design-for-learning-udl/index.html @@ -1,4 +1,4 @@ -Universal Design for Learning (UDL) - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Universal Design for Learning (UDL)

Universal Design for Learning (UDL) is a framework that avoids a ‘one-size fits all approach’ to learning materials. It encourages using multiple ways of engagement, representation and action and expression can meet the needs of a larger number of learners. Learn about the three main UDL principles, advantages, benefits and tips.

Introduction to Universal Design for Learning (UDL)

It is important to design courses and adopt a teaching style that meets the needs of people with different backgrounds, abilities and learning styles. Everyone learns differently, so there is no one-size-fits-all teaching method. By using different teaching methods, we can meet the needs of a larger number of learners. Rather than using a ‘one-size fits all approach’, providing multiple ways of engagement, representation and action and expression can meet the needs of a larger number of learners.

Universal Design for Learning (UDL) is a framework that comes from the concept of Universal Design (UD). You've probably seen examples of universal design in your daily life, such as closed captions, automatic doors, ramps and accessibility features of smart phones. These things help people with disabilities, but they can also be helpful for people who don't have a disability.

Universal Design for Learning (UDL) helps all leaners succeed. It encourages teaching and learning professionals to provide multiple ways for learners. It helps remove barriers that may prevent some people from learning and gives all students an equal chance of success. It is flexible and can be adapted to meet the needs of each student. UDL is useful for everyone.

Using UDL principles, teachers can effectively educate a diverse group of learners by making access to information and the demonstration of knowledge more flexible. This means they can adapt to each learner's individual strengths and needs, removing barriers to learning and providing equal opportunities for success for all. UDL therefore benefits not only learners with disabilities, but all learners.

There are three main principles of UDL:

Multiple means of representation

Providing learners with multiple ways to access information and content. This includes presenting information in different formats such as text, audio, and video, and offering different modes of interaction such as visuals, audio, and text.

Multiple means of action and expression

Allowing learners to demonstrate what they know in different ways. This includes providing options for students to express themselves through writing, speech, or other forms of communication.

Multiple means of engagement

Providing learners with multiple ways to engage with content, activities, and assessments. This includes offering choices in how they approach and interact with learning materials, as well as creating opportunities for motivation and self-reflection.

The advantages

Benefits for educators

Such as facilitators, coaches, course instructors, and developers

Benefits for learners

Tips and tricks for creating accessible course content

It's important to make learning accessible for everyone, regardless of their abilities.

Ask yourself some questions to figure out how you can make your course accessible.

Which topics might pose difficulties for students with visual, hearing, cognitive, motor disabilities or for those learning French as a second language?

By considering these questions, you can improve the experience for all students, including those who use adaptive technologies to support their learning.

Creating an accessible and universal learning experience is possible by following those simple tips:

Overall, by following these tips and considering the needs of different students, you can create an accessible and enjoyable learning experience for everyone.

The importance of words

It is important to use the right words when talking about people with disabilities, to show them respect. We need to use positive, non-discriminatory language that evolves over time to reflect the increasing equality and independence of people with disabilities. As educators, we have a role to play in using the right vocabulary and changing the way we deal with topics that concern them. The Government of Canada has created a booklet, A way with words and images, to help achieve this goal.

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Universal Design for Learning (UDL)

Universal Design for Learning (UDL) is a framework that avoids a ‘one-size fits all approach’ to learning materials. It encourages using multiple ways of engagement, representation and action and expression can meet the needs of a larger number of learners. Learn about the three main UDL principles, advantages, benefits and tips.

Introduction to Universal Design for Learning (UDL)

It is important to design courses and adopt a teaching style that meets the needs of people with different backgrounds, abilities and learning styles. Everyone learns differently, so there is no one-size-fits-all teaching method. By using different teaching methods, we can meet the needs of a larger number of learners. Rather than using a ‘one-size fits all approach’, providing multiple ways of engagement, representation and action and expression can meet the needs of a larger number of learners.

Universal Design for Learning (UDL) is a framework that comes from the concept of Universal Design (UD). You've probably seen examples of universal design in your daily life, such as closed captions, automatic doors, ramps and accessibility features of smart phones. These things help people with disabilities, but they can also be helpful for people who don't have a disability.

Universal Design for Learning (UDL) helps all leaners succeed. It encourages teaching and learning professionals to provide multiple ways for learners. It helps remove barriers that may prevent some people from learning and gives all students an equal chance of success. It is flexible and can be adapted to meet the needs of each student. UDL is useful for everyone.

Using UDL principles, teachers can effectively educate a diverse group of learners by making access to information and the demonstration of knowledge more flexible. This means they can adapt to each learner's individual strengths and needs, removing barriers to learning and providing equal opportunities for success for all. UDL therefore benefits not only learners with disabilities, but all learners.

There are three main principles of UDL:

Multiple means of representation

Providing learners with multiple ways to access information and content. This includes presenting information in different formats such as text, audio, and video, and offering different modes of interaction such as visuals, audio, and text.

Multiple means of action and expression

Allowing learners to demonstrate what they know in different ways. This includes providing options for students to express themselves through writing, speech, or other forms of communication.

Multiple means of engagement

Providing learners with multiple ways to engage with content, activities, and assessments. This includes offering choices in how they approach and interact with learning materials, as well as creating opportunities for motivation and self-reflection.

The advantages

Benefits for educators

Such as facilitators, coaches, course instructors, and developers

Benefits for learners

Tips and tricks for creating accessible course content

It's important to make learning accessible for everyone, regardless of their abilities.

Ask yourself some questions to figure out how you can make your course accessible.

Which topics might pose difficulties for students with visual, hearing, cognitive, motor disabilities or for those learning French as a second language?

By considering these questions, you can improve the experience for all students, including those who use adaptive technologies to support their learning.

Creating an accessible and universal learning experience is possible by following those simple tips:

Overall, by following these tips and considering the needs of different students, you can create an accessible and enjoyable learning experience for everyone.

The importance of words

It is important to use the right words when talking about people with disabilities, to show them respect. We need to use positive, non-discriminatory language that evolves over time to reflect the increasing equality and independence of people with disabilities. As educators, we have a role to play in using the right vocabulary and changing the way we deal with topics that concern them. The Government of Canada has created a booklet, A way with words and images, to help achieve this goal.

Page details

Date modified:
\ No newline at end of file diff --git a/en/useful-links/index.html b/en/useful-links/index.html index 53443297b..933700ac0 100644 --- a/en/useful-links/index.html +++ b/en/useful-links/index.html @@ -1,4 +1,4 @@ -Useful Links - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Useful Links

This page contains a list of key links for ESDC's IT Accessibility Office.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link
TitleDescriptionCategory
Part of a WholeNicolas Steenhout writes about accessibility.Learning
Which Video Conferencing Tools Are Most Accessible?In this article, Claudio Luis Vera explains what to keep in mind when choosing between video conferencing tools to benefit everyone on your team — including those with disabilities.Learning
Accessibility Best PracticesAccessibility is an important corner stone of iOS development. It enables all people to use your apps, no matter their abilities. Fortunately UIKit offers many APIs, which allow Developers to offer support for system technologies within their apps.Development
Centrally Deployed Templates Solution (CDTS)The purpose of the CDTS is essentially to deliver the presentation layer of the Canada.ca theme or Intranet.canada.ca theme to web assets.Development
Web Experience Toolkit (WET)An award-winning front-end framework for building websites that are accessible, usable, interoperable, mobile friendly and multilingualDevelopment
Canada.ca Content Style GuideThese are the rules to create web content that can be easily found, understood and used. They are based on writing principles and techniques that help make web content clear and adapted to the needs of all people.Development
Canada.ca Content and Information Architecture SpecificationThe Canada.ca design system provides user-tested templates, patterns and design principles. The system allows designers and developers to create a more usable, consistent and trustworthy online experience for people who access Government of Canada digital services.Development
A11Y Style GuideThis application is a living style guide or pattern library, generated from KSS documented styles...with an accessibility twist.Style guide
Asking users for datesFollow this pattern whenever you need users to provide or select a date as part of your service.Development
Web accessibility for Canada.ca (CSPS - T716)This course outlines federal standards and guidelines on web accessibility and emphasizes the requirements, roles and responsibilities for compliance with this standard. Participants will learn how to assess and apply WCAG 2.0 in a consistent manner throughout the Canada.ca web pages under the Web Renewal Initiative.Learning
18F Accessibility GuideAccessibility guide developed by the US Government.Development
Nutrition Cards for Accessible ComponentsA11Y Nutrition Cards is an attempt to digest and simplify the accessibility expectations when it comes to component authoring.Development
The A11Y ProjectThe A11Y Project is a community-driven effort to make digital accessibility easier.Style guide
CDS Accessibility HandbookThe Canadian Digital Service is committed to building accessible and inclusive services. Building accessible services means meeting the needs of as many people as possible.Learning
International Association of Accessibility ProfessionalsAccessibility professionals from around the world come together to define, promote and improve the accessibility profession through networking, education and certification.Learning
Guide to Planning Inclusive MeetingsWell-planned meetings are an essential communication tool for any organization. Meetings in the workplace and in volunteer and community groups regularly bring people together to share information, develop strategies, work toward common goals and celebrate successes.Learning
Guideline on Making Information Technology Usable by AllThis guideline supports the Government of Canada’s direction to ensure that departments, agencies and organizations consider accessibility in the acquisition or development of information technology (IT) solutions and equipment to make IT usable by all.Policy
EU EN 301 549 (Managing accessibility in the public procurement of ICT)Accessibility requirements suitable for public procurement of ICT products and services in Europe.Policy
General accessibility services, tools and resources listing Internal linkLearn about the services, tools and resources for making communications products and activities accessible.Listing
Making communications accessible in the Government of CanadaAccessibility is about respecting differences and removing barriers so that everyone can participate.Development
M365 accessibilityList of resources and learning material on M365 accessibility.Learning
Accessibility PortalOur believe is that digital equality is a human right for websites, mobile applications, and digital content. But it doesn’t stop there. We need to do it for quality, innovation, compliance, relations, user experience and much much more.Learning
Short note on aria-label, aria-labelledby, and aria-describedbyBe careful when you use the aria-label, aria-labelledby, and aria-describedby attributes, because they do not work consistently with all HTML elements.Development
YouTube: Apple: AccessibilityFrom using your iPhone without seeing the screen, to adapting gestures to your physical needs, discover how the accessibility features built into your Apple devices can help you do more.Learning
Screen reader considerations when choosing between Google at IU My Drive and Microsoft OneDrive at IUThe choice between Google at IU My Drive and Microsoft OneDrive at IU isn't simple when considering screen reader accessibility. There are pros and cons to both, which can differ depending on the screen reader and browser combination used.Learning
The web, design, and accessibility – tempertemperI’m Martin, a user interface and interaction designer, lover of HTML and CSS, and co-founder of Frontend NE. Here’s a wee bit more about me and what I’m up to.Learning
Web Content Accessibility GuideThe fundamental basis for you to have truly inclusive and accessible digital products.Learning
Accessibility Maze: a fun game to learn about web accessibilityRyerson University created the Accessibility Maze, a fun game, to help people new to web accessibility practise and learn more on barriers and challenges that people with disabilities usually experience when navigating the Web. The game provides quick lessons on how to avoid those barriers or correct them.Learning
Web Accessibility Assessment Methodology (Level AA)Assist with measuring conformance to the Web Content Accessibility Guidelines (WCAG) 2.1 Level A and Level AA Success CriteriaDevelopment
Digital Accessibility ToolkitDigital accessibility resources for public servants, by public servants.Learning
Accessibility CoursesCourses, webinars, educational videos, and more, offered in web accessibility.Learning
Accessibility SupportCheck if your code will work with assistive technologies.Development

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Useful Links

This page contains a list of key links for ESDC's IT Accessibility Office.

Important information

  • Links that only work within the Government of Canada firewall are marked with internal link
TitleDescriptionCategory
Part of a WholeNicolas Steenhout writes about accessibility.Learning
Which Video Conferencing Tools Are Most Accessible?In this article, Claudio Luis Vera explains what to keep in mind when choosing between video conferencing tools to benefit everyone on your team — including those with disabilities.Learning
Accessibility Best PracticesAccessibility is an important corner stone of iOS development. It enables all people to use your apps, no matter their abilities. Fortunately UIKit offers many APIs, which allow Developers to offer support for system technologies within their apps.Development
Centrally Deployed Templates Solution (CDTS)The purpose of the CDTS is essentially to deliver the presentation layer of the Canada.ca theme or Intranet.canada.ca theme to web assets.Development
Web Experience Toolkit (WET)An award-winning front-end framework for building websites that are accessible, usable, interoperable, mobile friendly and multilingualDevelopment
Canada.ca Content Style GuideThese are the rules to create web content that can be easily found, understood and used. They are based on writing principles and techniques that help make web content clear and adapted to the needs of all people.Development
Canada.ca Content and Information Architecture SpecificationThe Canada.ca design system provides user-tested templates, patterns and design principles. The system allows designers and developers to create a more usable, consistent and trustworthy online experience for people who access Government of Canada digital services.Development
A11Y Style GuideThis application is a living style guide or pattern library, generated from KSS documented styles...with an accessibility twist.Style guide
Asking users for datesFollow this pattern whenever you need users to provide or select a date as part of your service.Development
Web accessibility for Canada.ca (CSPS - T716)This course outlines federal standards and guidelines on web accessibility and emphasizes the requirements, roles and responsibilities for compliance with this standard. Participants will learn how to assess and apply WCAG 2.0 in a consistent manner throughout the Canada.ca web pages under the Web Renewal Initiative.Learning
18F Accessibility GuideAccessibility guide developed by the US Government.Development
Nutrition Cards for Accessible ComponentsA11Y Nutrition Cards is an attempt to digest and simplify the accessibility expectations when it comes to component authoring.Development
The A11Y ProjectThe A11Y Project is a community-driven effort to make digital accessibility easier.Style guide
CDS Accessibility HandbookThe Canadian Digital Service is committed to building accessible and inclusive services. Building accessible services means meeting the needs of as many people as possible.Learning
International Association of Accessibility ProfessionalsAccessibility professionals from around the world come together to define, promote and improve the accessibility profession through networking, education and certification.Learning
Guide to Planning Inclusive MeetingsWell-planned meetings are an essential communication tool for any organization. Meetings in the workplace and in volunteer and community groups regularly bring people together to share information, develop strategies, work toward common goals and celebrate successes.Learning
Guideline on Making Information Technology Usable by AllThis guideline supports the Government of Canada’s direction to ensure that departments, agencies and organizations consider accessibility in the acquisition or development of information technology (IT) solutions and equipment to make IT usable by all.Policy
EU EN 301 549 (Managing accessibility in the public procurement of ICT)Accessibility requirements suitable for public procurement of ICT products and services in Europe.Policy
General accessibility services, tools and resources listing Internal linkLearn about the services, tools and resources for making communications products and activities accessible.Listing
Making communications accessible in the Government of CanadaAccessibility is about respecting differences and removing barriers so that everyone can participate.Development
M365 accessibilityList of resources and learning material on M365 accessibility.Learning
Accessibility PortalOur believe is that digital equality is a human right for websites, mobile applications, and digital content. But it doesn’t stop there. We need to do it for quality, innovation, compliance, relations, user experience and much much more.Learning
Short note on aria-label, aria-labelledby, and aria-describedbyBe careful when you use the aria-label, aria-labelledby, and aria-describedby attributes, because they do not work consistently with all HTML elements.Development
YouTube: Apple: AccessibilityFrom using your iPhone without seeing the screen, to adapting gestures to your physical needs, discover how the accessibility features built into your Apple devices can help you do more.Learning
Screen reader considerations when choosing between Google at IU My Drive and Microsoft OneDrive at IUThe choice between Google at IU My Drive and Microsoft OneDrive at IU isn't simple when considering screen reader accessibility. There are pros and cons to both, which can differ depending on the screen reader and browser combination used.Learning
The web, design, and accessibility – tempertemperI’m Martin, a user interface and interaction designer, lover of HTML and CSS, and co-founder of Frontend NE. Here’s a wee bit more about me and what I’m up to.Learning
Web Content Accessibility GuideThe fundamental basis for you to have truly inclusive and accessible digital products.Learning
Accessibility Maze: a fun game to learn about web accessibilityRyerson University created the Accessibility Maze, a fun game, to help people new to web accessibility practise and learn more on barriers and challenges that people with disabilities usually experience when navigating the Web. The game provides quick lessons on how to avoid those barriers or correct them.Learning
Web Accessibility Assessment Methodology (Level AA)Assist with measuring conformance to the Web Content Accessibility Guidelines (WCAG) 2.1 Level A and Level AA Success CriteriaDevelopment
Digital Accessibility ToolkitDigital accessibility resources for public servants, by public servants.Learning
Accessibility CoursesCourses, webinars, educational videos, and more, offered in web accessibility.Learning
Accessibility SupportCheck if your code will work with assistive technologies.Development

Page details

Date modified:
\ No newline at end of file diff --git a/en/visual-impairments/index.html b/en/visual-impairments/index.html index a95fc305b..7ecf7f50a 100644 --- a/en/visual-impairments/index.html +++ b/en/visual-impairments/index.html @@ -1,4 +1,4 @@ -Visual Impairments - Digital Accessibility Toolkit

Language selection

Government of Canada / Government of Canada

Search

Visual Impairments

Visual disabilities are sensory disabilities that can range from some amount of vision loss, loss of visual acuity, or increased or decreased sensitivity to specific or bright colours, to complete or uncorrectable loss of vision in either or both eyes.

Blindness

Definition:
Blindness is a sensory disability involving nearly complete vision loss.
Characteristics:
Some people are completely blind, without the ability to see anything. Others can perceive light versus dark, or the general shapes of large objects, but cannot read text or recognize people by sight.

Colour Blindness

Definition:
Colour blindness is a sensory disability that impairs a person’s ability to distinguish certain colour combinations.
Characteristics:
The most common forms of colour-blindness affect an individual’s ability to distinguish reds and greens, although other colours may be affected.

Low Vision

Definition:

Low vision is uncorrectable vision loss that interferes with daily activities. It is better defined in terms of function, rather than numerical test results.

Characteristics:
  • In other words, low vision is “not enough vision to do whatever it is you need to do,” which can vary from person to person.
  • Most eye care professionals prefer to use the term “low vision” to describe permanently reduced vision that cannot be corrected with regular glasses, contact lenses, medicine, or surgery.

Adaptive Technologies and Adaptive Strategies

Here are some commonly used products:

Page details

Date modified:
\ No newline at end of file + })(window);

Language selection

Government of Canada / Government of Canada

Search

Visual Impairments

Visual disabilities are sensory disabilities that can range from some amount of vision loss, loss of visual acuity, or increased or decreased sensitivity to specific or bright colours, to complete or uncorrectable loss of vision in either or both eyes.

Blindness

Definition:
Blindness is a sensory disability involving nearly complete vision loss.
Characteristics:
Some people are completely blind, without the ability to see anything. Others can perceive light versus dark, or the general shapes of large objects, but cannot read text or recognize people by sight.

Colour Blindness

Definition:
Colour blindness is a sensory disability that impairs a person’s ability to distinguish certain colour combinations.
Characteristics:
The most common forms of colour-blindness affect an individual’s ability to distinguish reds and greens, although other colours may be affected.

Low Vision

Definition:

Low vision is uncorrectable vision loss that interferes with daily activities. It is better defined in terms of function, rather than numerical test results.

Characteristics:
  • In other words, low vision is “not enough vision to do whatever it is you need to do,” which can vary from person to person.
  • Most eye care professionals prefer to use the term “low vision” to describe permanently reduced vision that cannot be corrected with regular glasses, contact lenses, medicine, or surgery.

Adaptive Technologies and Adaptive Strategies

Here are some commonly used products:

Page details

Date modified:
\ No newline at end of file diff --git a/fr/ameliorer-l-accessibilite-des-formulaires/index.html b/fr/ameliorer-l-accessibilite-des-formulaires/index.html index 060094cae..497d49482 100644 --- a/fr/ameliorer-l-accessibilite-des-formulaires/index.html +++ b/fr/ameliorer-l-accessibilite-des-formulaires/index.html @@ -1,4 +1,4 @@ -Améliorer l’accessibilité des formulaires - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Améliorer l’accessibilité des formulaires

Dans cette section, vous trouverez les étapes essentielles pour le développement d’un formulaire accessible.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

Le format de formulaire le plus accessible: HTML

HTML est le meilleur et le plus flexibles. Lorsqu’ils sont codés correctement, HTML offrent les meilleures caractéristiques en matière d’accessibilité, notamment:

Pour les sites Web utilisant la Boîte à outils de l’expérience Web, veuillez suivre le Guide de conception de la Boîte à outils de l’expérience Web pour créer un formulaire HTML accessible.

Facile et accessible : un document Word simple

Les documents Microsoft Word (sans champs de formulaire) sont le deuxième meilleur outil pour créer des formulaires accessibles. On peut adapter un document Word comme on le fait pour un document HTML afin de répondre à des besoins particuliers de l’utilisateur (p. ex. la taille de la police peut être augmentée). Ce type de document peut constituer un bon choix pour l’accessibilité malgré ses limites. Le document devrait être structurer de façon simple, avec les questions et les réponses sous une seule colonne, qui comprends aussi un espace vide sous chaque question pour les réponses. Toutefois, dans un document Word simple, vous ne pourrez pas inclure d’éléments de formulaire, comme des cases à cocher ou un moyen automatisé de validation pour s’assurer que les champs requis ont été remplis. La protection du contenu que vous ne voulez pas modifier (comme les questions) peut rendre l’accès à ce contenu plus difficile pour les utilisateurs de la technologie adaptée. Si vous respectez ces limites, un document Word simple pourrait bien être tout ce dont vous avez besoin pour recueillir de l’information. Il s’agit à la fois du format le plus facile à créer et le plus facile à adapter aux besoins particuliers des utilisateurs.

Non recommandé : un document Word complexe

Dans Microsoft Word, si vous utilisez des éléments de formulaire intégrés, comme les cases à cocher, le formulaire deviendra inaccessible. Pour en savoir plus sur les raisons de ces limites, consultez Les limites d’accessibilité des formulaires Microsoft Word (en anglais seulement). Microsoft a même caché ces fonctions dans les versions récentes de Word sous « anciens outils ». Dans un document Word, les champs de formulaire sont difficiles à atteindre à l’aide d’un clavier et ne comportent pas d’associations d’étiquettes explicites. Cela entraîne des difficultés pour les utilisateurs de technologies adaptées. Par exemple, l’utilisateur d’un lecteur d’écran devra s’éloigner du champ du formulaire afin de trouver l’étiquette correspondante – un problème aggravé par les difficultés de navigation à l’aide du clavier et d’accès au contenu protégé.

Difficile et semi-accessible : le format PDF

Le format de document portable (PDF) est le format le plus couramment utilisé pour les formulaires au sein du gouvernement du Canada. C’est aussi l’un des formats les plus difficiles à rendre accessibles. Pour préserver le formatage lors de l’impression du formulaire, une grande partie de la présentation est « programmée » dans le fichier. Ceci limite considérablement l’adaptabilité du formulaire lorsqu’un utilisateur le remplit par voie électronique. Par exemple, la plupart des formulaires PDF ne sont pas reformatés avec succès lorsqu’e l’espace d’affichage est plus petit, ce qui en rend la lecture plus difficile sur des appareils mobiles ou pour des utilisateurs ayant une déficience visuelle. Les préférences des utilisateurs en matière de couleurs et de polices ne sont que rarement reflétées. Il est également difficile d’adapter un document PDF en d’autres formats, comme les gros caractères ou le braille.

Les formulaires PDF remplissable sont fréquemment utilisés parce qu’il offre plusieurs caractéristiques similaires à celles des formulaires HTML, soit des éléments de formulaire comme des cases à cocher, des étiquettes programmatiques et même la validation JavaScript. Si vous ne pouvez pas utiliser un formulaire HTML, mais que vous avez besoin de ces fonctions, prenez des mesures pour vous assurer que votre PDF soit aussi accessible que le format le permet.

Créer un formulaire PDF

Bien qu’il existe des outils spécifiques pour créer des formulaires PDF (p. ex. Adobe LiveCycle), vous pouvez utiliser Microsoft Word comme point de départ pour créer un formulaire PDF (voir Créer des fichiers PDF accessibles). Ne créez pas les champs de formulaire dans Word. Laissez plutôt des espaces blancs pour les créer dans l’éditeur PDF (p. ex. Acrobat Pro, Foxit PDF Editor).

Premièrement, le document Word doit être lui-même accessible. En plus de suivre les lignes directrices générales concernant l’accessibilité du document, évitez les erreurs communes de conception de formulaires:

  1. N’utilisez pas de tableaux pour la présentation visuelle.
    1. Utilisez plutôt l’ordre linéaire, qui est l’option la plus simple et la plus accessible, où chaque champ de formulaire sera sur une nouvelle ligne.
    2. Si vous souhaitez un style visuel sur « plusieurs colonnes », vous pouvez le faire à l’aide de tabulations ou de colonnes. Vous pouvez utiliser des styles personnalisés pour créer des encadrés. N’utilisez pas de zones de texte.
  2. Des titres devraient être utilisés pour séparer les différentes sections afin de faciliter la navigation dans le formulaire.
    1. Notez que les titres ne fonctionneront qu’à l’extérieur d’un tableau.

Une fois que le modèle de formulaire a été créé en Word pour être le plus accessible possible, exportez-le en format PDF. Assurez-vous que les options sont sélectionnées pour créer, dans le PDF, des signets à partir des titres ainsi que des balises.

Vous devrez ensuite créer les champs de formulaire dans le logiciel PDF. Veuillez consulter ce guide d’Adobe sur la création de formulaires accessibles dans Acrobat Pro DC. Il est très important que vous indiquiez explicitement en tant qu’« infobulles » les étiquettes des champs de formulaire. Voir aussi les tutoriels vidéo et les guides d’utilisation de Foxit PDF Editor.

Signatures électroniques

Examinez attentivement les exigences relatives aux signatures. Le Secrétariat du Conseil du Trésor du Canada a publié un document intitulé Orientation du gouvernement du Canada sur l’utilisation des signatures électroniques. Souvent, le fait de demander à l’utilisateur de taper son nom sur une ligne ou d’insérer une image de signature suffit pour un document Word ou un PDF. La vérification de l’identité s’effectue lorsque le document est envoyé en pièce jointe par courriel. Pour un formulaire HTML, le fait de demander à l’utilisateur de taper son nom et de cocher une case pour confirmer son identité peut également être suffisant.

Lorsqu’un niveau de sécurité accru est requis, une signature numérique peut être utilisée que ce soit dans un document PDF ou Word. Vous aurez besoin de votre clé Entrust pour signer un document de façon électronique. Pour plus de renseignements, consultez le Guide de l’utilisateur technique des signatures numériques de Transports Canada (en anglais seulement) Lien interne( Word, 1.1 mo).

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Améliorer l’accessibilité des formulaires

Dans cette section, vous trouverez les étapes essentielles pour le développement d’un formulaire accessible.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

Le format de formulaire le plus accessible: HTML

HTML est le meilleur et le plus flexibles. Lorsqu’ils sont codés correctement, HTML offrent les meilleures caractéristiques en matière d’accessibilité, notamment:

Pour les sites Web utilisant la Boîte à outils de l’expérience Web, veuillez suivre le Guide de conception de la Boîte à outils de l’expérience Web pour créer un formulaire HTML accessible.

Facile et accessible : un document Word simple

Les documents Microsoft Word (sans champs de formulaire) sont le deuxième meilleur outil pour créer des formulaires accessibles. On peut adapter un document Word comme on le fait pour un document HTML afin de répondre à des besoins particuliers de l’utilisateur (p. ex. la taille de la police peut être augmentée). Ce type de document peut constituer un bon choix pour l’accessibilité malgré ses limites. Le document devrait être structurer de façon simple, avec les questions et les réponses sous une seule colonne, qui comprends aussi un espace vide sous chaque question pour les réponses. Toutefois, dans un document Word simple, vous ne pourrez pas inclure d’éléments de formulaire, comme des cases à cocher ou un moyen automatisé de validation pour s’assurer que les champs requis ont été remplis. La protection du contenu que vous ne voulez pas modifier (comme les questions) peut rendre l’accès à ce contenu plus difficile pour les utilisateurs de la technologie adaptée. Si vous respectez ces limites, un document Word simple pourrait bien être tout ce dont vous avez besoin pour recueillir de l’information. Il s’agit à la fois du format le plus facile à créer et le plus facile à adapter aux besoins particuliers des utilisateurs.

Non recommandé : un document Word complexe

Dans Microsoft Word, si vous utilisez des éléments de formulaire intégrés, comme les cases à cocher, le formulaire deviendra inaccessible. Pour en savoir plus sur les raisons de ces limites, consultez Les limites d’accessibilité des formulaires Microsoft Word (en anglais seulement). Microsoft a même caché ces fonctions dans les versions récentes de Word sous « anciens outils ». Dans un document Word, les champs de formulaire sont difficiles à atteindre à l’aide d’un clavier et ne comportent pas d’associations d’étiquettes explicites. Cela entraîne des difficultés pour les utilisateurs de technologies adaptées. Par exemple, l’utilisateur d’un lecteur d’écran devra s’éloigner du champ du formulaire afin de trouver l’étiquette correspondante – un problème aggravé par les difficultés de navigation à l’aide du clavier et d’accès au contenu protégé.

Difficile et semi-accessible : le format PDF

Le format de document portable (PDF) est le format le plus couramment utilisé pour les formulaires au sein du gouvernement du Canada. C’est aussi l’un des formats les plus difficiles à rendre accessibles. Pour préserver le formatage lors de l’impression du formulaire, une grande partie de la présentation est « programmée » dans le fichier. Ceci limite considérablement l’adaptabilité du formulaire lorsqu’un utilisateur le remplit par voie électronique. Par exemple, la plupart des formulaires PDF ne sont pas reformatés avec succès lorsqu’e l’espace d’affichage est plus petit, ce qui en rend la lecture plus difficile sur des appareils mobiles ou pour des utilisateurs ayant une déficience visuelle. Les préférences des utilisateurs en matière de couleurs et de polices ne sont que rarement reflétées. Il est également difficile d’adapter un document PDF en d’autres formats, comme les gros caractères ou le braille.

Les formulaires PDF remplissable sont fréquemment utilisés parce qu’il offre plusieurs caractéristiques similaires à celles des formulaires HTML, soit des éléments de formulaire comme des cases à cocher, des étiquettes programmatiques et même la validation JavaScript. Si vous ne pouvez pas utiliser un formulaire HTML, mais que vous avez besoin de ces fonctions, prenez des mesures pour vous assurer que votre PDF soit aussi accessible que le format le permet.

Créer un formulaire PDF

Bien qu’il existe des outils spécifiques pour créer des formulaires PDF (p. ex. Adobe LiveCycle), vous pouvez utiliser Microsoft Word comme point de départ pour créer un formulaire PDF (voir Créer des fichiers PDF accessibles). Ne créez pas les champs de formulaire dans Word. Laissez plutôt des espaces blancs pour les créer dans l’éditeur PDF (p. ex. Acrobat Pro, Foxit PDF Editor).

Premièrement, le document Word doit être lui-même accessible. En plus de suivre les lignes directrices générales concernant l’accessibilité du document, évitez les erreurs communes de conception de formulaires:

  1. N’utilisez pas de tableaux pour la présentation visuelle.
    1. Utilisez plutôt l’ordre linéaire, qui est l’option la plus simple et la plus accessible, où chaque champ de formulaire sera sur une nouvelle ligne.
    2. Si vous souhaitez un style visuel sur « plusieurs colonnes », vous pouvez le faire à l’aide de tabulations ou de colonnes. Vous pouvez utiliser des styles personnalisés pour créer des encadrés. N’utilisez pas de zones de texte.
  2. Des titres devraient être utilisés pour séparer les différentes sections afin de faciliter la navigation dans le formulaire.
    1. Notez que les titres ne fonctionneront qu’à l’extérieur d’un tableau.

Une fois que le modèle de formulaire a été créé en Word pour être le plus accessible possible, exportez-le en format PDF. Assurez-vous que les options sont sélectionnées pour créer, dans le PDF, des signets à partir des titres ainsi que des balises.

Vous devrez ensuite créer les champs de formulaire dans le logiciel PDF. Veuillez consulter ce guide d’Adobe sur la création de formulaires accessibles dans Acrobat Pro DC. Il est très important que vous indiquiez explicitement en tant qu’« infobulles » les étiquettes des champs de formulaire. Voir aussi les tutoriels vidéo et les guides d’utilisation de Foxit PDF Editor.

Signatures électroniques

Examinez attentivement les exigences relatives aux signatures. Le Secrétariat du Conseil du Trésor du Canada a publié un document intitulé Orientation du gouvernement du Canada sur l’utilisation des signatures électroniques. Souvent, le fait de demander à l’utilisateur de taper son nom sur une ligne ou d’insérer une image de signature suffit pour un document Word ou un PDF. La vérification de l’identité s’effectue lorsque le document est envoyé en pièce jointe par courriel. Pour un formulaire HTML, le fait de demander à l’utilisateur de taper son nom et de cocher une case pour confirmer son identité peut également être suffisant.

Lorsqu’un niveau de sécurité accru est requis, une signature numérique peut être utilisée que ce soit dans un document PDF ou Word. Vous aurez besoin de votre clé Entrust pour signer un document de façon électronique. Pour plus de renseignements, consultez le Guide de l’utilisateur technique des signatures numériques de Transports Canada (en anglais seulement) Lien interne( Word, 1.1 mo).

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/approvisionnement/index.html b/fr/approvisionnement/index.html index fbd027754..a4b5236d4 100644 --- a/fr/approvisionnement/index.html +++ b/fr/approvisionnement/index.html @@ -9,4 +9,4 @@ w.gtag('js', new Date()); w.gtag('config', 'G-SM9MSHWDVN'); } - })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Approvisionnement

En savoir plus et accéder à des ressources pour soutenir l'inclusion des exigences d'accessibilité des technologies de l'information et de la communication (TIC) dans les marchés publics et les contrats non concurrentiels du gouvernement du Canada.

Exigences en matière de technologies de l’information et des communications (TIC) accessibles

Cette page a pour but de partager une partie du travail effectué par Services partagés Canada (SPC) pour le pilotage des normes harmonisées d'accessibilité des technologies de l’information et des communications (TIC) EN 301 549 (2021). Il ne s'agit pas d'un copier / coller / traduction complet des normes, l'EN 301 549 (2021) ou le Web Content Accessibility Guidelines (WCAG) 2.1.

Générateur d'exigences en technologies de l'information et de la communication (TIC) (prototype) pour la norme EN 301 549 (2021)

Le générateur d'exigences en technologies de l'information et de la communication (TIC) (aussi connu comme l’assistant) peut être utilisé pour générer les exigences EN 301 549 qui sont pertinentes pour votre projet.

Cet outil ne fournit pas un copier / coller / traduction complet de la norme EN 301 549 ou des WCAG 2.1, seulement les portions pertinentes requises sont fournis pour définir les exigences d’accessibilité des TIC.

Générateur d'exigences d'accessibilité des TIC (prototype) pour la norme EN 301 549 (2018) - périmé

Mise en correspondance entre l’article 508 révisé (Revised Section 508) et la norme EN 301 549 (2014, 2018, 2019 et 2021)

Comme les normes EN 301 549 (en anglais seulement) continuent, d’évoluer et de publier des mises à jour, le présent document montre la progression des normes EN 301 549 depuis 2014, jusqu’aux mises à jour de 2018, 2019 et 2021. Ces renseignements sont importants, car le GC se dirige vers l’adoption de la norme EN 301 549 (2021)) comme norme d’accessibilité pour les TIC. Le GC, dans le cadre du processus d’invitation à soumissionner, peut demander aux fournisseurs de fournir des rapports de conformité en matière d’accessibilité basés sur le modèle d’accessibilité volontaire des produits Voluntary Product Accessibility Template - (VPAT). Chaque VPAT est fondé sur une norme technique précise – l’article 508 révisé, la norme EN 301 549 ou les Web Content Accessibility Guidelines (WCAG) (en anglais seulement). Les fournisseurs, les responsables techniques et les autorités contractantes doivent comprendre les différences entre ces normes pour s’assurer que les exigences d’accessibilité sont abordées comme il se doit.

Résumé technique de la norme EN 301 549 v3.2.1 (2021)

Ce résumé technique fournit au lecteur un résumé simplifié des exigences techniques de la norme EN 301 549 (V3.2.1 (2021-03) Norme européenne harmonisée relative à l'accessibilité des produits et services TIC. Chaque clause ou groupe de clauses connexes a été reformulé en langage clair et des exemples ont été ajoutés pour aider les lecteurs à comprendre les exigences à un niveau élevé. Ce document est particulièrement utile pour ceux qui souhaitent comprendre les exigences de la norme EN 301 549 sans avoir à lire l'intégralité de la norme.

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Approvisionnement

En savoir plus et accéder à des ressources pour soutenir l'inclusion des exigences d'accessibilité des technologies de l'information et de la communication (TIC) dans les marchés publics et les contrats non concurrentiels du gouvernement du Canada.

Exigences en matière de technologies de l’information et des communications (TIC) accessibles

Cette page a pour but de partager une partie du travail effectué par Services partagés Canada (SPC) pour le pilotage des normes harmonisées d'accessibilité des technologies de l’information et des communications (TIC) EN 301 549 (2021). Il ne s'agit pas d'un copier / coller / traduction complet des normes, l'EN 301 549 (2021) ou le Web Content Accessibility Guidelines (WCAG) 2.1.

Générateur d'exigences en technologies de l'information et de la communication (TIC) (prototype) pour la norme EN 301 549 (2021)

Le générateur d'exigences en technologies de l'information et de la communication (TIC) (aussi connu comme l’assistant) peut être utilisé pour générer les exigences EN 301 549 qui sont pertinentes pour votre projet.

Cet outil ne fournit pas un copier / coller / traduction complet de la norme EN 301 549 ou des WCAG 2.1, seulement les portions pertinentes requises sont fournis pour définir les exigences d’accessibilité des TIC.

Générateur d'exigences d'accessibilité des TIC (prototype) pour la norme EN 301 549 (2018) - périmé

Mise en correspondance entre l’article 508 révisé (Revised Section 508) et la norme EN 301 549 (2014, 2018, 2019 et 2021)

Comme les normes EN 301 549 (en anglais seulement) continuent, d’évoluer et de publier des mises à jour, le présent document montre la progression des normes EN 301 549 depuis 2014, jusqu’aux mises à jour de 2018, 2019 et 2021. Ces renseignements sont importants, car le GC se dirige vers l’adoption de la norme EN 301 549 (2021)) comme norme d’accessibilité pour les TIC. Le GC, dans le cadre du processus d’invitation à soumissionner, peut demander aux fournisseurs de fournir des rapports de conformité en matière d’accessibilité basés sur le modèle d’accessibilité volontaire des produits Voluntary Product Accessibility Template - (VPAT). Chaque VPAT est fondé sur une norme technique précise – l’article 508 révisé, la norme EN 301 549 ou les Web Content Accessibility Guidelines (WCAG) (en anglais seulement). Les fournisseurs, les responsables techniques et les autorités contractantes doivent comprendre les différences entre ces normes pour s’assurer que les exigences d’accessibilité sont abordées comme il se doit.

Résumé technique de la norme EN 301 549 v3.2.1 (2021)

Ce résumé technique fournit au lecteur un résumé simplifié des exigences techniques de la norme EN 301 549 (V3.2.1 (2021-03) Norme européenne harmonisée relative à l'accessibilité des produits et services TIC. Chaque clause ou groupe de clauses connexes a été reformulé en langage clair et des exemples ont été ajoutés pour aider les lecteurs à comprendre les exigences à un niveau élevé. Ce document est particulièrement utile pour ceux qui souhaitent comprendre les exigences de la norme EN 301 549 sans avoir à lire l'intégralité de la norme.

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/bonnes-pratiques-pour-les-evenements-virtuels-accessibles/index.html b/fr/bonnes-pratiques-pour-les-evenements-virtuels-accessibles/index.html index 75cc18a82..2b99a981f 100644 --- a/fr/bonnes-pratiques-pour-les-evenements-virtuels-accessibles/index.html +++ b/fr/bonnes-pratiques-pour-les-evenements-virtuels-accessibles/index.html @@ -1,4 +1,4 @@ -Bonnes pratiques pour les événements virtuels accessibles - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Bonnes pratiques pour les événements virtuels accessibles

Ce guide porte sur la planification d’événements, couvrant un large éventail d’activités comme des conférences, des réunions, et des présentations. Il comprend les obstacles courants auxquels les personnes en situation d’handicap sont confrontées lors des événements et un calendrier suggéré pour l’organisation de votre événement. L’objectif est de travailler ensemble pour créer des expériences plus inclusives et accessibles.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

Bonnes pratiques pour les événements virtuels accessibles ( Word, 86 ko)

Sur cette page

Introduction

Aux fins du présent contenu, le terme « événement » comprend des activités telles que: événements, des conférences, des réunions, des kiosques, des formations, des présentations et plus encore.

Le présent guide propose un calendrier pour l'organisation de votre événement, mais celui-ci n'est pas normatif.

Problèmes courants signalés par les personnes en situation de handicap

Avant d'explorer le présent guide, nous vous invitons à prendre connaissance les obstacles les plus courantes concernant les événements que nous avons recueillies auprès de personnes en situation de handicap. Nous vous invitons à collaborer avec nous pour aborder les difficultés suivantes.

Audio

Visuel

Mobilité

Cognitif

Cadre juridique canadien pour l'accessibilité des événements

Au Canada, la Loi canadienne sur l’accessibilité ainsi que la Loi canadienne sur les droits de la personne et la Directive sur l’obligation de prendre des mesures d’adaptation nous incitent à créer des événements accessibles. Ce cadre juridique protège les droits des personnes en situation de handicap afin d'assurer leur pleine participation dans la société.

Voici un bref résumé de leur relation avec la gestion des événements :

Loi canadienne sur l’accessibilité

L'objectif est de faire du Canada un pays exempt obstacles d'ici le 1er janvier 2040, en exigeant la reconnaissance, l'élimination et la prévention des obstacles dans les domaines suivants :

Loi canadienne sur les droits de la personne

Interdit la discrimination fondée sur le handicap.

Directive sur l’obligation de prendre des mesures d’adaptation

Garantit la pleine participation des personnes en situation de handicap en concevant l’ensemble des systèmes, processus et installations de manière à ce qu'ils soient accessibles dès le départ. Lorsqu'un obstacle ne peut être supprimé, la personne doit bénéficier de mesures d'adaptation.

Faits à retenir

À propos des mesures d’adaptation

À propos des handicaps

À propos d’une planification minutieuse

Événements virtuels

Feuille de route

Tout d'abord, vous devrez planifier votre événement. Plusieurs décisions devront être prises, notamment :

Ensuite, vous organiserez votre événement. Nous vous recommandons de faire ce qui suit :

Troisièmement, vous animerez votre événement. Assurez-vous de faire ce qui suit :

Enfin, après l'événement, vous voudrez faire ce qui suit :

Planification de l’événement : un à deux mois avant la tenue de l'événement (environ)

Décidez si l'événement est bilingue ou s'il s'agit de deux sessions unilingues

Une session en français, une session en anglais (meilleur choix pour l'accessibilité)

Dans la mesure du possible, prévoyez deux sessions distinctes, l'une en français et l'autre en anglais. C'est particulièrement utile pour les formations obligatoires et essentielles.

Événement bilingue (meilleur choix pour les langues officielles)

Les événements bilingues sont une option, en particulier pour les conférences et les événements hebdomadaires ou pour l’ensemble du personnel.

Voici les points à retenir lorsque vous organisez un événement bilingue :

Ressources pour les événements bilingues

Décidez de la plateforme virtuelle qui accueillera votre événement

Choisissez une platniveau AA de la norme WCAG 2.1. En outre, nous vous recommandons de faire appel à des utilisateurs en situation de handicap pour tester la convivialité de votre plateforme et la manière dont vous avez mis en œuvre votre événement. Pour obtenir des conseils détaillés, reportez-vous à la section Selecting an accessible remote meeting platform (en anglais seulement) du guide sur l'accessibilité des réunions à distance de W3C.

Attribuez des rôles et des responsabilités au personnel chargé de l'événement

Avertissement :

Lors des événements de moindre envergure, certains membres du personnel peuvent être amenés à jouer plusieurs rôles. Les événements plus importants présenteront plus de défis et nécessiteront une plus grande répartition des tâches. N'oubliez pas que des tiers, tels que des compagnies de production audiovisuelle, peuvent être chargés de certaines de ces tâches.

En règle générale, les rôles suivants sont attribués, mais ces conseils ne sont pas normatifs :

Hôte / responsable de l'événement

Remarque : Il est recommandé d'avoir un seul hôte / animateur de l'événement, car les participants se sentent plus à l'aise lorsqu'ils entendent une voix familière.

Modérateur(s)
Présentateur(s)
Administrateur / Soutien
Preneur de notes

Remarque : La distribution des notes après l'événement est importante, en particulier pour les participants qui ont de la difficulté à écouter et à écrire en même temps.

Réservez les services de mesures d’adaptation une fois la date confirmée

Des mesures d’adaptation peuvent être nécessaires pour remplir les obligations énoncées dans la Directive sur l’obligation de prendre des mesures d’adaptation.

Remarque : Veuillez fournir à l'avance le matériel de présentation (PowerPoint, Word, courriel, vidéos préenregistrées) aux fournisseurs de services. En raison de la forte demande, nous vous conseillons de soumettre vos demandes au moins quatre semaines avant l'événement.

Services d'interprétation en langue des signes (ASL, LSQ)

Les personnes qui sont sourdes, malentendantes ou qui maîtrisent la langue des signes peuvent avoir des difficultés avec les sous-titres écrits, car il s'agit de leur deuxième langue. L'interprétation en langue des signes améliore également l'expérience en transmettant l'intonation, l'émotion et des renseignements audio importants.

Traduction en temps réel des communications

Le sous-titrage permet aux personnes qui sont sourdes, qui ont subi une perte d’audition ou qui souffrent de troubles cognitifs tels que des difficultés à traiter des informations auditives, et même aux personnes dont le français et l'anglais ne sont pas la langue maternelle, de participer pleinement à des événements en direct.

Remarque : La réservation doit être faite pour un minimum de deux heures, après quoi des frais sont facturés au demandeur par tranches de 30 minutes.

Mise en garde : Certaines plateformes d'événements virtuels proposent des sous-titres automatisés en direct, comme les sous-titres en direct dans Microsoft Teams. Malheureusement, ces technologies commettent souvent des erreurs, ce qui désavantage les utilisateurs qui comptent sur les sous-titres. Les sous-titres automatiques ne devraient être utilisés qu'en dernier recours ou pour des événements de moindre importance. Utilisez plutôt les services de sous-titrage CART.

Services d’interprétation et de traduction simultanée

Les événements bilingues peuvent constituer un obstacle pour les personnes unilingues en situation de handicap. Pour garantir le plein accès, des traductions vocales simultanées sont nécessaires. Les sous-titres traduits ou le contenu à l'écran ne sont pas accessibles aux utilisateurs non visuels. Par conséquent, ils doivent attendre les changements de langue sans aucun stimulus et s'en remettre uniquement aux résumés des points de discussion dans leur langue.

Remarque : Ceci nécessite une plateforme virtuelle qui offre plusieurs canaux vocaux, un pour chaque langue. Lorsque le présentateur ne parle plus la langue du canal vocal, l'interprète affecté au canal vocal doit prononcer la traduction.

Veillez à ce que tous les supports de l'événement soient accessibles (tels que les courriels, les présentations PowerPoint, les documents Word...)

Tout le contenu distribué doit être accessible et dans les deux langues officielles. Dans la mesure du possible, privilégiez les formats plus accessibles tels que HTML, Word, PowerPoint, ePub plutôt que les formats moins accessibles tels que PDF.

Important : Révisez toujours le matériel des présentateurs, même lorsque ceux-ci sont externes, car vous serez responsable de l'accessibilité du contenu.

Formation

Envisagez de suivre une formation sur l'accessibilité. Lorsque le contenu est élaboré par des personnes qui ont acquis des connaissances en matière d'accessibilité et qui les appliquent dès le départ, cela permet de gagner bien du temps et d'économiser beaucoup d'argent en réduisant la nécessité de prendre des mesures correctives et en évitant les plaintes potentielles.

Veuillez consulter la boîte à outils de l'accessibilité numérique pour obtenir des renseignements plus détaillés dans nos guides. En outre, nous vous recommandons de regarder l'atelier enregistré de l'EFPC intitulé « Rendre ses documents accessibles (INC1-V46) ».

Conseil général sur l'accessibilité des documents (s'applique à tous)
Conseils rapides pour les courriels
Conseils rapides pour les présentations PowerPoint
Conseils rapides pour les documents Word
Conseils rapides pour les vidéos préenregistrés

Envoie des invitations aux participants

Établissez un ordre du jour
Incluez les renseignements sur l'événement dans l'invitation

Veillez à inclure les renseignements suivants dans votre invitation à l'événement :

Préparez-vous : une à deux semaines avant l'événement (environ)

Préparez les scénarios

Un scénario pour l'hôte peut être très utile pour guider l'événement. En général, un tel scénario contient le discours d'ouverture de l'hôte, les déclarations pour les sections de questions et réponses et, enfin, le mot de la fin.

Vous trouverez ci-dessous un exemple de modèle de scénario de discours d'ouverture que vous pouvez modifier à votre guise :

Bienvenue à notre [nom de l'événement] à propos de [ajouter une courte description de l'événement]. Je m'appelle [dites votre nom] et je serai votre hôte aujourd'hui. [L'hôte devrait prendre le temps de reconnaître les Premières Nations et les territoires traditionnels (consultez le guide).] Je vais d’abord aborder quelques points d’ordre administratif concernant l’événement virtuel d’aujourd’hui :

  • Si vous ne vous êtes pas encore déconnecté du VPN, veuillez le faire pour profiter d’une expérience optimale
  • Veuillez désactiver votre microphone et votre vidéo pendant toute la durée de l'événement
  • Pour poser des questions, tapez dans la fonction de clavardage ou attendez que nous ayons une période de questions pour utiliser la fonction « lever la main » - le raccourci clavier est [donnez le raccourci clavier]. Une fois que vous êtes sélectionné pour poser votre question, veuillez réactiver votre micro et montrer votre vidéo si vous le souhaitez. Nous trierons vos questions posées dans le clavardage et y répondrons soit dans le clavardage, soit pendant la période de questions. Sinon, nous pouvons vous demander d'envoyer votre question par courriel à l’adresse courriel de l'événement afin que nous puissions y répondre après cet événement

Je vais maintenant vous présenter notre présentateur aujourd'hui : [présentez le présentateur]

Préparez-vous à présenter – Sensibilisation à l'accessibilité pour les orateurs

Tenez des répétitions (si nécessaire)

Plus l'événement est important ou critique, plus il est préférable d'organiser une répétition générale.

Si une répétition est jugée souhaitable, nous recommandons vivement de la faire pour vous assurer que tout le monde est sur la même longueur d'onde.

Animez l'événement : jour de l'événement

Testez votre installation environ 15 à 30 minutes avant l'événement

Commencez l'événement!

Étiquette recommandée pour les participants

Invitez les participants à :

Corrigez les erreurs

Récapitulez l’événement

Après l'événement

Envoyez le contenu de la récapitulation

Veillez à distribuer le contenu dans un format accessible, ce qui est souvent fait par le biais d'un courriel de remerciement après l'événement :

Répondez aux questions après l'événement

Veuillez répondre en temps opportun.

Recueillez les commentaires des participants

Demandez aux participants de vous faire part de leurs commentaires et offrez-leur plusieurs moyens de les recevoir, par exemple par courriel ou par l'intermédiaire d'un formulaire. Il est important d'obtenir une rétroaction pour continuer à améliorer la qualité des événements.

Voici quelques exemples de sujets qui peuvent être abordés et de questions qui peuvent être posées :

À titre de référence : Ce qui affectera votre budget

À titre de référence : Plateformes virtuelles

Avertissement de sécurité : « bombardement » des événements virtuels

Des termes comme « bombardement par Zoom », « T-BOMB », etc. sont devenus populaires pour décrire l'intrusion d'étrangers sur l'internet dans des événements virtuels. En général, les intrus tentent de perturber l'événement en partageant leur caméra, en faisant du bruit dans leur micro ou en utilisant la fonction « Partager l'écran ».

Voici quelques conseils pour gérer les risques liés à ces attaques :

Information sur Microsoft Teams

Conformité aux normes d'accessibilité

Vous trouverez les modèles volontaires d'accessibilité des produits (VPAT) pour MS Teams dans les rapports de conformité de l'accessibilité de Microsoft (en anglais seulement), en utilisant le filtre et en choisissant « Teams » comme catégorie.

Options recommandées pour les événements

Après avoir configuré un événement dans MS Teams, il est possible de modifier les options de réunion. Pour accéder aux options de réunion, activez le lien situé au bas de l'invitation à l'événement générée par Teams.

Dans la mesure du possible, nous recommandons ce qui suit :

Ressources supplémentaires pour l'organisateur
Copiez-collez des renseignements que vous pouvez inclure dans l'invitation des participants

Veuillez consulter les liens suivants pour en savoir plus sur Microsoft Teams :

Pour commencer

Accessibilité

Réduction des distractions

Fonctionnalités pour événements

Remarque : Les participants qui entrent dans une réunion Microsoft Teams après que 1 000 personnes se sont déjà jointes auront une expérience restreinte, en lecture seule. Pour obtenir de plus amples renseignements sur les contrôles et les actions disponibles dans cette expérience de réunion en lecture seule, veuillez consulter la ressource suivante : « Expérience de réunion en lecture seule de Teams - Microsoft Teams | Microsoft Learn »

Information sur WebEx

Conformité aux normes d'accessibilité

Les VPAT remplis pour WebEx se trouvent parmi les autres produits de cette société sur la page « Voluntary Product Accessibility Templates - Cisco (en anglais seulement) », dans la section « WebEx App »

Copiez-collez des renseignements que vous pouvez inclure dans l'invitation des participants

Veuillez consulter les liens suivants pour en savoir plus sur WebEx :

Pour commencer

Accessibilité

Réduction des distractions

Fonctionnalités pour événements

Information sur Zoom

Conformité aux normes d'accessibilité

Zoom affirme être conforme aux normes WCAG 2.1 niveau AA, aux normes révisées de l’article 508 et aux exigences de la norme EN 301 549. Vous trouverez les VPAT remplis pour Zoom à leur page Accessibilité dans la section « Documents relatifs à l’accessibilité ».

Copiez-collez des renseignements que vous pouvez inclure dans l'invitation des participants

Veuillez consulter les liens suivants pour en savoir plus sur Zoom :

Pour commencer

Accessibilité

Réduction des distractions

Fonctionnalités pour événements

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Bonnes pratiques pour les événements virtuels accessibles

Ce guide porte sur la planification d’événements, couvrant un large éventail d’activités comme des conférences, des réunions, et des présentations. Il comprend les obstacles courants auxquels les personnes en situation d’handicap sont confrontées lors des événements et un calendrier suggéré pour l’organisation de votre événement. L’objectif est de travailler ensemble pour créer des expériences plus inclusives et accessibles.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

Bonnes pratiques pour les événements virtuels accessibles ( Word, 86 ko)

Sur cette page

Introduction

Aux fins du présent contenu, le terme « événement » comprend des activités telles que: événements, des conférences, des réunions, des kiosques, des formations, des présentations et plus encore.

Le présent guide propose un calendrier pour l'organisation de votre événement, mais celui-ci n'est pas normatif.

Problèmes courants signalés par les personnes en situation de handicap

Avant d'explorer le présent guide, nous vous invitons à prendre connaissance les obstacles les plus courantes concernant les événements que nous avons recueillies auprès de personnes en situation de handicap. Nous vous invitons à collaborer avec nous pour aborder les difficultés suivantes.

Audio

Visuel

Mobilité

Cognitif

Cadre juridique canadien pour l'accessibilité des événements

Au Canada, la Loi canadienne sur l’accessibilité ainsi que la Loi canadienne sur les droits de la personne et la Directive sur l’obligation de prendre des mesures d’adaptation nous incitent à créer des événements accessibles. Ce cadre juridique protège les droits des personnes en situation de handicap afin d'assurer leur pleine participation dans la société.

Voici un bref résumé de leur relation avec la gestion des événements :

Loi canadienne sur l’accessibilité

L'objectif est de faire du Canada un pays exempt obstacles d'ici le 1er janvier 2040, en exigeant la reconnaissance, l'élimination et la prévention des obstacles dans les domaines suivants :

Loi canadienne sur les droits de la personne

Interdit la discrimination fondée sur le handicap.

Directive sur l’obligation de prendre des mesures d’adaptation

Garantit la pleine participation des personnes en situation de handicap en concevant l’ensemble des systèmes, processus et installations de manière à ce qu'ils soient accessibles dès le départ. Lorsqu'un obstacle ne peut être supprimé, la personne doit bénéficier de mesures d'adaptation.

Faits à retenir

À propos des mesures d’adaptation

À propos des handicaps

À propos d’une planification minutieuse

Événements virtuels

Feuille de route

Tout d'abord, vous devrez planifier votre événement. Plusieurs décisions devront être prises, notamment :

Ensuite, vous organiserez votre événement. Nous vous recommandons de faire ce qui suit :

Troisièmement, vous animerez votre événement. Assurez-vous de faire ce qui suit :

Enfin, après l'événement, vous voudrez faire ce qui suit :

Planification de l’événement : un à deux mois avant la tenue de l'événement (environ)

Décidez si l'événement est bilingue ou s'il s'agit de deux sessions unilingues

Une session en français, une session en anglais (meilleur choix pour l'accessibilité)

Dans la mesure du possible, prévoyez deux sessions distinctes, l'une en français et l'autre en anglais. C'est particulièrement utile pour les formations obligatoires et essentielles.

Événement bilingue (meilleur choix pour les langues officielles)

Les événements bilingues sont une option, en particulier pour les conférences et les événements hebdomadaires ou pour l’ensemble du personnel.

Voici les points à retenir lorsque vous organisez un événement bilingue :

Ressources pour les événements bilingues

Décidez de la plateforme virtuelle qui accueillera votre événement

Choisissez une platniveau AA de la norme WCAG 2.1. En outre, nous vous recommandons de faire appel à des utilisateurs en situation de handicap pour tester la convivialité de votre plateforme et la manière dont vous avez mis en œuvre votre événement. Pour obtenir des conseils détaillés, reportez-vous à la section Selecting an accessible remote meeting platform (en anglais seulement) du guide sur l'accessibilité des réunions à distance de W3C.

Attribuez des rôles et des responsabilités au personnel chargé de l'événement

Avertissement :

Lors des événements de moindre envergure, certains membres du personnel peuvent être amenés à jouer plusieurs rôles. Les événements plus importants présenteront plus de défis et nécessiteront une plus grande répartition des tâches. N'oubliez pas que des tiers, tels que des compagnies de production audiovisuelle, peuvent être chargés de certaines de ces tâches.

En règle générale, les rôles suivants sont attribués, mais ces conseils ne sont pas normatifs :

Hôte / responsable de l'événement

Remarque : Il est recommandé d'avoir un seul hôte / animateur de l'événement, car les participants se sentent plus à l'aise lorsqu'ils entendent une voix familière.

Modérateur(s)
Présentateur(s)
Administrateur / Soutien
Preneur de notes

Remarque : La distribution des notes après l'événement est importante, en particulier pour les participants qui ont de la difficulté à écouter et à écrire en même temps.

Réservez les services de mesures d’adaptation une fois la date confirmée

Des mesures d’adaptation peuvent être nécessaires pour remplir les obligations énoncées dans la Directive sur l’obligation de prendre des mesures d’adaptation.

Remarque : Veuillez fournir à l'avance le matériel de présentation (PowerPoint, Word, courriel, vidéos préenregistrées) aux fournisseurs de services. En raison de la forte demande, nous vous conseillons de soumettre vos demandes au moins quatre semaines avant l'événement.

Services d'interprétation en langue des signes (ASL, LSQ)

Les personnes qui sont sourdes, malentendantes ou qui maîtrisent la langue des signes peuvent avoir des difficultés avec les sous-titres écrits, car il s'agit de leur deuxième langue. L'interprétation en langue des signes améliore également l'expérience en transmettant l'intonation, l'émotion et des renseignements audio importants.

Traduction en temps réel des communications

Le sous-titrage permet aux personnes qui sont sourdes, qui ont subi une perte d’audition ou qui souffrent de troubles cognitifs tels que des difficultés à traiter des informations auditives, et même aux personnes dont le français et l'anglais ne sont pas la langue maternelle, de participer pleinement à des événements en direct.

Remarque : La réservation doit être faite pour un minimum de deux heures, après quoi des frais sont facturés au demandeur par tranches de 30 minutes.

Mise en garde : Certaines plateformes d'événements virtuels proposent des sous-titres automatisés en direct, comme les sous-titres en direct dans Microsoft Teams. Malheureusement, ces technologies commettent souvent des erreurs, ce qui désavantage les utilisateurs qui comptent sur les sous-titres. Les sous-titres automatiques ne devraient être utilisés qu'en dernier recours ou pour des événements de moindre importance. Utilisez plutôt les services de sous-titrage CART.

Services d’interprétation et de traduction simultanée

Les événements bilingues peuvent constituer un obstacle pour les personnes unilingues en situation de handicap. Pour garantir le plein accès, des traductions vocales simultanées sont nécessaires. Les sous-titres traduits ou le contenu à l'écran ne sont pas accessibles aux utilisateurs non visuels. Par conséquent, ils doivent attendre les changements de langue sans aucun stimulus et s'en remettre uniquement aux résumés des points de discussion dans leur langue.

Remarque : Ceci nécessite une plateforme virtuelle qui offre plusieurs canaux vocaux, un pour chaque langue. Lorsque le présentateur ne parle plus la langue du canal vocal, l'interprète affecté au canal vocal doit prononcer la traduction.

Veillez à ce que tous les supports de l'événement soient accessibles (tels que les courriels, les présentations PowerPoint, les documents Word...)

Tout le contenu distribué doit être accessible et dans les deux langues officielles. Dans la mesure du possible, privilégiez les formats plus accessibles tels que HTML, Word, PowerPoint, ePub plutôt que les formats moins accessibles tels que PDF.

Important : Révisez toujours le matériel des présentateurs, même lorsque ceux-ci sont externes, car vous serez responsable de l'accessibilité du contenu.

Formation

Envisagez de suivre une formation sur l'accessibilité. Lorsque le contenu est élaboré par des personnes qui ont acquis des connaissances en matière d'accessibilité et qui les appliquent dès le départ, cela permet de gagner bien du temps et d'économiser beaucoup d'argent en réduisant la nécessité de prendre des mesures correctives et en évitant les plaintes potentielles.

Veuillez consulter la boîte à outils de l'accessibilité numérique pour obtenir des renseignements plus détaillés dans nos guides. En outre, nous vous recommandons de regarder l'atelier enregistré de l'EFPC intitulé « Rendre ses documents accessibles (INC1-V46) ».

Conseil général sur l'accessibilité des documents (s'applique à tous)
Conseils rapides pour les courriels
Conseils rapides pour les présentations PowerPoint
Conseils rapides pour les documents Word
Conseils rapides pour les vidéos préenregistrés

Envoie des invitations aux participants

Établissez un ordre du jour
Incluez les renseignements sur l'événement dans l'invitation

Veillez à inclure les renseignements suivants dans votre invitation à l'événement :

Préparez-vous : une à deux semaines avant l'événement (environ)

Préparez les scénarios

Un scénario pour l'hôte peut être très utile pour guider l'événement. En général, un tel scénario contient le discours d'ouverture de l'hôte, les déclarations pour les sections de questions et réponses et, enfin, le mot de la fin.

Vous trouverez ci-dessous un exemple de modèle de scénario de discours d'ouverture que vous pouvez modifier à votre guise :

Bienvenue à notre [nom de l'événement] à propos de [ajouter une courte description de l'événement]. Je m'appelle [dites votre nom] et je serai votre hôte aujourd'hui. [L'hôte devrait prendre le temps de reconnaître les Premières Nations et les territoires traditionnels (consultez le guide).] Je vais d’abord aborder quelques points d’ordre administratif concernant l’événement virtuel d’aujourd’hui :

  • Si vous ne vous êtes pas encore déconnecté du VPN, veuillez le faire pour profiter d’une expérience optimale
  • Veuillez désactiver votre microphone et votre vidéo pendant toute la durée de l'événement
  • Pour poser des questions, tapez dans la fonction de clavardage ou attendez que nous ayons une période de questions pour utiliser la fonction « lever la main » - le raccourci clavier est [donnez le raccourci clavier]. Une fois que vous êtes sélectionné pour poser votre question, veuillez réactiver votre micro et montrer votre vidéo si vous le souhaitez. Nous trierons vos questions posées dans le clavardage et y répondrons soit dans le clavardage, soit pendant la période de questions. Sinon, nous pouvons vous demander d'envoyer votre question par courriel à l’adresse courriel de l'événement afin que nous puissions y répondre après cet événement

Je vais maintenant vous présenter notre présentateur aujourd'hui : [présentez le présentateur]

Préparez-vous à présenter – Sensibilisation à l'accessibilité pour les orateurs

Tenez des répétitions (si nécessaire)

Plus l'événement est important ou critique, plus il est préférable d'organiser une répétition générale.

Si une répétition est jugée souhaitable, nous recommandons vivement de la faire pour vous assurer que tout le monde est sur la même longueur d'onde.

Animez l'événement : jour de l'événement

Testez votre installation environ 15 à 30 minutes avant l'événement

Commencez l'événement!

Étiquette recommandée pour les participants

Invitez les participants à :

Corrigez les erreurs

Récapitulez l’événement

Après l'événement

Envoyez le contenu de la récapitulation

Veillez à distribuer le contenu dans un format accessible, ce qui est souvent fait par le biais d'un courriel de remerciement après l'événement :

Répondez aux questions après l'événement

Veuillez répondre en temps opportun.

Recueillez les commentaires des participants

Demandez aux participants de vous faire part de leurs commentaires et offrez-leur plusieurs moyens de les recevoir, par exemple par courriel ou par l'intermédiaire d'un formulaire. Il est important d'obtenir une rétroaction pour continuer à améliorer la qualité des événements.

Voici quelques exemples de sujets qui peuvent être abordés et de questions qui peuvent être posées :

À titre de référence : Ce qui affectera votre budget

À titre de référence : Plateformes virtuelles

Avertissement de sécurité : « bombardement » des événements virtuels

Des termes comme « bombardement par Zoom », « T-BOMB », etc. sont devenus populaires pour décrire l'intrusion d'étrangers sur l'internet dans des événements virtuels. En général, les intrus tentent de perturber l'événement en partageant leur caméra, en faisant du bruit dans leur micro ou en utilisant la fonction « Partager l'écran ».

Voici quelques conseils pour gérer les risques liés à ces attaques :

Information sur Microsoft Teams

Conformité aux normes d'accessibilité

Vous trouverez les modèles volontaires d'accessibilité des produits (VPAT) pour MS Teams dans les rapports de conformité de l'accessibilité de Microsoft (en anglais seulement), en utilisant le filtre et en choisissant « Teams » comme catégorie.

Options recommandées pour les événements

Après avoir configuré un événement dans MS Teams, il est possible de modifier les options de réunion. Pour accéder aux options de réunion, activez le lien situé au bas de l'invitation à l'événement générée par Teams.

Dans la mesure du possible, nous recommandons ce qui suit :

Ressources supplémentaires pour l'organisateur
Copiez-collez des renseignements que vous pouvez inclure dans l'invitation des participants

Veuillez consulter les liens suivants pour en savoir plus sur Microsoft Teams :

Pour commencer

Accessibilité

Réduction des distractions

Fonctionnalités pour événements

Remarque : Les participants qui entrent dans une réunion Microsoft Teams après que 1 000 personnes se sont déjà jointes auront une expérience restreinte, en lecture seule. Pour obtenir de plus amples renseignements sur les contrôles et les actions disponibles dans cette expérience de réunion en lecture seule, veuillez consulter la ressource suivante : « Expérience de réunion en lecture seule de Teams - Microsoft Teams | Microsoft Learn »

Information sur WebEx

Conformité aux normes d'accessibilité

Les VPAT remplis pour WebEx se trouvent parmi les autres produits de cette société sur la page « Voluntary Product Accessibility Templates - Cisco (en anglais seulement) », dans la section « WebEx App »

Copiez-collez des renseignements que vous pouvez inclure dans l'invitation des participants

Veuillez consulter les liens suivants pour en savoir plus sur WebEx :

Pour commencer

Accessibilité

Réduction des distractions

Fonctionnalités pour événements

Information sur Zoom

Conformité aux normes d'accessibilité

Zoom affirme être conforme aux normes WCAG 2.1 niveau AA, aux normes révisées de l’article 508 et aux exigences de la norme EN 301 549. Vous trouverez les VPAT remplis pour Zoom à leur page Accessibilité dans la section « Documents relatifs à l’accessibilité ».

Copiez-collez des renseignements que vous pouvez inclure dans l'invitation des participants

Veuillez consulter les liens suivants pour en savoir plus sur Zoom :

Pour commencer

Accessibilité

Réduction des distractions

Fonctionnalités pour événements

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/conception-universelle-pour-l-apprentissage-cua/index.html b/fr/conception-universelle-pour-l-apprentissage-cua/index.html index b7566e84e..3612a4e2e 100644 --- a/fr/conception-universelle-pour-l-apprentissage-cua/index.html +++ b/fr/conception-universelle-pour-l-apprentissage-cua/index.html @@ -1,4 +1,4 @@ -Conception universelle pour l’apprentissage (CUA) - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Conception universelle pour l’apprentissage (CUA)

La conception universelle pour l’apprentissage (CUA) est un cadre qui évite une « approche unique » du matériel d’apprentissage. Il encourage l’utilisation de multiples façons d’engagement, de représentation, d’action et d’expression peut répondre aux besoins d’un plus grand nombre d’apprenants. Renseignez-vous sur les trois principaux principes, avantages, avantages et conseils de la CUA.

Introduction à la conception universelle pour l’apprentissage (CUA)

Il est important de concevoir des cours et d’adopter un style d’enseignement qui répond aux besoins de personnes ayant des antécédents, des capacités et des styles d’apprentissage différents. Tout le monde apprend différemment, il n’y a donc pas de méthode d’enseignement unique. En utilisant différentes méthodes d’enseignement, nous pouvons répondre aux besoins d’un plus grand nombre d’apprenants. Plutôt que d’utiliser une « approche universelle », fournir de multiples façons d’engagement, de représentation, d’action et d’expression peut répondre aux besoins d’un plus grand nombre d’apprenants.

La conception universelle pour l’apprentissage (CUA) est un cadre qui vient du concept de conception universelle (UD). Vous avez probablement vu des exemples de conception universelle dans votre vie quotidienne, tels que les sous-titrages, les portes automatiques, les rampes et les caractéristiques d’accessibilité des téléphones intelligents. Ces choses aident les personnes handicapées, mais elles peuvent également être utiles pour les personnes qui n’ont pas de handicap.

La conception universelle pour l’apprentissage (CUA) aide tous les apprenants à réussir. Il encourage les professionnels de l’enseignement et de l’apprentissage à fournir de multiples façons aux apprenants. Cela aide à éliminer les obstacles qui peuvent empêcher certaines personnes d’apprendre et donne à tous les élèves une chance égale de réussite. De plus, ce cadre est flexible et peut être adapté pour répondre aux besoins de chaque élève. La CUA est utile pour tout le monde.

En utilisant les principes de la CUA, les enseignants peuvent éduquer efficacement un groupe diversifié d’apprenants en rendant l’accès à l’information et la démonstration des connaissances plus flexibles. Cela signifie qu’ils peuvent s’adapter aux forces et aux besoins individuels de chaque apprenant, en éliminant les obstacles à l’apprentissage et en offrant des chances égales de réussite pour tous. La CUA profite donc non seulement aux apprenants vivant avec un handicap ou limitation, mais à tous les apprenants.

Il y a trois grands principes de la CUA :

1. Moyens multiples de représentation

Fournir aux apprenants de multiples façons d’accéder à l’information et au contenu. Cela inclut la présentation d’informations dans différents formats tels que le texte, l’audio et la vidéo, et l’offre de différents modes d’interaction tels que les visuels, l’audio et le texte.

2. Moyens d’action et d’expression multiples

Permettre aux apprenants de démontrer ce qu’ils savent de différentes manières. Cela comprend la fourniture d’options permettant aux élèves de s’exprimer par l’écriture, la parole ou d’autres formes de communication.

3. Moyens d’engagement multiples

Fournir aux apprenants de multiples façons de s’engager dans le contenu, les activités et les évaluations. Cela comprend l’offre de choix dans la façon dont ils abordent et interagissent avec le matériel d’apprentissage, ainsi que la création d’opportunités de motivation et d’autoréflexion.

Les avantages

Avantages pour les éducateurs

Tels que les facilitateurs, les entraîneurs, les instructeurs de cours et les développeurs

Avantages pour les apprenants

Trucs et astuces pour créer du contenu de cours accessible

Il est important de rendre l’apprentissage accessible à tous, quelles que soient leurs capacités.

Posez-vous quelques questions pour comprendre comment vous pouvez rendre votre cours accessible.

Commencez par quelques questions :

En tenant compte de ces questions, vous pouvez améliorer l’expérience de tous les élèves, y compris ceux qui utilisent des technologies d’adaptation pour soutenir leur apprentissage.

La création d’une expérience d'apprentissage accessible et universelle est possible en suivant ces conseils simples:

Dans l’ensemble, en suivant ces conseils et en tenant compte des besoins des différents élèves, vous pouvez créer une expérience d’apprentissage accessible et agréable pour tout le monde.

L’importance des mots

Il est important d’utiliser les bons mots lorsque l’on parle de personnes vivant avec un handicap, pour leur montrer du respect. Nous devons utiliser un langage positif et non discriminatoire qui évolue au fil du temps pour refléter l’égalité et l’indépendance croissantes des personnes handicapées. En tant qu’éducateurs, nous avons un rôle à jouer dans l’utilisation du bon vocabulaire et dans le changement de la façon dont nous traitons les sujets qui les concernent. Le gouvernement du Canada a créé un livret, Le pouvoir des mots et des images, pour aider à atteindre cet objectif.

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Conception universelle pour l’apprentissage (CUA)

La conception universelle pour l’apprentissage (CUA) est un cadre qui évite une « approche unique » du matériel d’apprentissage. Il encourage l’utilisation de multiples façons d’engagement, de représentation, d’action et d’expression peut répondre aux besoins d’un plus grand nombre d’apprenants. Renseignez-vous sur les trois principaux principes, avantages, avantages et conseils de la CUA.

Introduction à la conception universelle pour l’apprentissage (CUA)

Il est important de concevoir des cours et d’adopter un style d’enseignement qui répond aux besoins de personnes ayant des antécédents, des capacités et des styles d’apprentissage différents. Tout le monde apprend différemment, il n’y a donc pas de méthode d’enseignement unique. En utilisant différentes méthodes d’enseignement, nous pouvons répondre aux besoins d’un plus grand nombre d’apprenants. Plutôt que d’utiliser une « approche universelle », fournir de multiples façons d’engagement, de représentation, d’action et d’expression peut répondre aux besoins d’un plus grand nombre d’apprenants.

La conception universelle pour l’apprentissage (CUA) est un cadre qui vient du concept de conception universelle (UD). Vous avez probablement vu des exemples de conception universelle dans votre vie quotidienne, tels que les sous-titrages, les portes automatiques, les rampes et les caractéristiques d’accessibilité des téléphones intelligents. Ces choses aident les personnes handicapées, mais elles peuvent également être utiles pour les personnes qui n’ont pas de handicap.

La conception universelle pour l’apprentissage (CUA) aide tous les apprenants à réussir. Il encourage les professionnels de l’enseignement et de l’apprentissage à fournir de multiples façons aux apprenants. Cela aide à éliminer les obstacles qui peuvent empêcher certaines personnes d’apprendre et donne à tous les élèves une chance égale de réussite. De plus, ce cadre est flexible et peut être adapté pour répondre aux besoins de chaque élève. La CUA est utile pour tout le monde.

En utilisant les principes de la CUA, les enseignants peuvent éduquer efficacement un groupe diversifié d’apprenants en rendant l’accès à l’information et la démonstration des connaissances plus flexibles. Cela signifie qu’ils peuvent s’adapter aux forces et aux besoins individuels de chaque apprenant, en éliminant les obstacles à l’apprentissage et en offrant des chances égales de réussite pour tous. La CUA profite donc non seulement aux apprenants vivant avec un handicap ou limitation, mais à tous les apprenants.

Il y a trois grands principes de la CUA :

1. Moyens multiples de représentation

Fournir aux apprenants de multiples façons d’accéder à l’information et au contenu. Cela inclut la présentation d’informations dans différents formats tels que le texte, l’audio et la vidéo, et l’offre de différents modes d’interaction tels que les visuels, l’audio et le texte.

2. Moyens d’action et d’expression multiples

Permettre aux apprenants de démontrer ce qu’ils savent de différentes manières. Cela comprend la fourniture d’options permettant aux élèves de s’exprimer par l’écriture, la parole ou d’autres formes de communication.

3. Moyens d’engagement multiples

Fournir aux apprenants de multiples façons de s’engager dans le contenu, les activités et les évaluations. Cela comprend l’offre de choix dans la façon dont ils abordent et interagissent avec le matériel d’apprentissage, ainsi que la création d’opportunités de motivation et d’autoréflexion.

Les avantages

Avantages pour les éducateurs

Tels que les facilitateurs, les entraîneurs, les instructeurs de cours et les développeurs

Avantages pour les apprenants

Trucs et astuces pour créer du contenu de cours accessible

Il est important de rendre l’apprentissage accessible à tous, quelles que soient leurs capacités.

Posez-vous quelques questions pour comprendre comment vous pouvez rendre votre cours accessible.

Commencez par quelques questions :

En tenant compte de ces questions, vous pouvez améliorer l’expérience de tous les élèves, y compris ceux qui utilisent des technologies d’adaptation pour soutenir leur apprentissage.

La création d’une expérience d'apprentissage accessible et universelle est possible en suivant ces conseils simples:

Dans l’ensemble, en suivant ces conseils et en tenant compte des besoins des différents élèves, vous pouvez créer une expérience d’apprentissage accessible et agréable pour tout le monde.

L’importance des mots

Il est important d’utiliser les bons mots lorsque l’on parle de personnes vivant avec un handicap, pour leur montrer du respect. Nous devons utiliser un langage positif et non discriminatoire qui évolue au fil du temps pour refléter l’égalité et l’indépendance croissantes des personnes handicapées. En tant qu’éducateurs, nous avons un rôle à jouer dans l’utilisation du bon vocabulaire et dans le changement de la façon dont nous traitons les sujets qui les concernent. Le gouvernement du Canada a créé un livret, Le pouvoir des mots et des images, pour aider à atteindre cet objectif.

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/concevoir-un-cours/index.html b/fr/concevoir-un-cours/index.html index ff164173e..669661a31 100644 --- a/fr/concevoir-un-cours/index.html +++ b/fr/concevoir-un-cours/index.html @@ -9,4 +9,4 @@ w.gtag('js', new Date()); w.gtag('config', 'G-SM9MSHWDVN'); } - })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Concevoir un cours

Découvrez les rôles et les processus impliqués dans la conception et le développement d'un cours accessible.

Conception universelle pour l’apprentissage (CUA)

La conception universelle pour l’apprentissage (CUA) est un cadre qui évite une « approche unique » du matériel d’apprentissage. Il encourage l’utilisation de multiples façons d’engagement, de représentation, d’action et d’expression peut répondre aux besoins d’un plus grand nombre d’apprenants. Renseignez-vous sur les trois principaux principes, avantages, avantages et conseils de la CUA.

Conseils pour la conception de cours en ligne

Conseils et astuces pour rédiger, concevoir et développer des cours en ligne

Personas handicapés pour la conception d'une expérience utilisateur inclusive (EU)

Le cas d'inclure les handicaps dans les personas des utilisateurs, les types de technologies qu'ils utilisent et les échantillons de personas avec des handicaps.

À faire et à ne pas faire pour développer des cours en ligne

Choses à faire et à ne pas faire pour rédiger, concevoir et développer des cours en ligne

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Concevoir un cours

Découvrez les rôles et les processus impliqués dans la conception et le développement d'un cours accessible.

Conception universelle pour l’apprentissage (CUA)

La conception universelle pour l’apprentissage (CUA) est un cadre qui évite une « approche unique » du matériel d’apprentissage. Il encourage l’utilisation de multiples façons d’engagement, de représentation, d’action et d’expression peut répondre aux besoins d’un plus grand nombre d’apprenants. Renseignez-vous sur les trois principaux principes, avantages, avantages et conseils de la CUA.

Conseils pour la conception de cours en ligne

Conseils et astuces pour rédiger, concevoir et développer des cours en ligne

Personas handicapés pour la conception d'une expérience utilisateur inclusive (EU)

Le cas d'inclure les handicaps dans les personas des utilisateurs, les types de technologies qu'ils utilisent et les échantillons de personas avec des handicaps.

À faire et à ne pas faire pour développer des cours en ligne

Choses à faire et à ne pas faire pour rédiger, concevoir et développer des cours en ligne

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/deficiences-auditives/index.html b/fr/deficiences-auditives/index.html index e3af86195..c479b5888 100644 --- a/fr/deficiences-auditives/index.html +++ b/fr/deficiences-auditives/index.html @@ -1,4 +1,4 @@ -Déficiences auditives - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Déficiences auditives

Les déficiences auditives sont des déficiences sensorielles allant d'une perte auditive partielle à complète.

Les déficiences auditives sont des déficiences sensorielles allant d'une perte auditive partielle à complète. Certaines personnes peuvent aussi avoir une ouïe trop sensible (hyperacousie) dans une ou les deux oreilles.

Surdité

Définition :
La surdité est la perte totale ou quasi totale de l'audition.
Caractéristiques :
Une personne sourde ou malentendante a des difficultés avec les sons, y compris la composante audio des documents multimédias. De nombreuses personnes, mais pas toutes, qui sont sourds connaissent la langue des signes. Pour les personnes nées sourdes, la langue des signes est souvent leur première langue et donc leur langue maternelle préférée. Ils peuvent se sentir moins à l'aise pour lire un texte imprimé ou numérique parce que c'est une langue étrangère pour eux et que la notation phonétique n'aide pas leur compréhension. En revanche, ceux qui perdent leur audition plus tard dans la vie (personne sourde postlinguistique) peuvent ne jamais apprendre la langue des signes, ou s'ils l'apprennent, ils peuvent ne pas se sentir aussi à l'aise de parler par signes et peuvent préférer le texte.

Une personne malentendante

Définition :
Les malentendants font référence aux personnes ayant une perte auditive allant de légère à sévère, qui ont encore une audition utile, et peuvent communiquer par la Langue des signes, langue parlée, ou les deux comprennent la langue parlée dans certaines situations, avec ou sans amplification. La plupart des personnes peuvent utiliser le téléphone et utiliser des appareils auditifs.
Caractéristiques :
Les personnes malentendantes ont d'une déficience auditive partielle dans une ou les deux oreilles, ce qui entraîne une perte auditive légère à modérée. L'audition résiduelle peut être suffisante pour qu'un appareil auditif, tel qu'une aide auditive ou un système de modulation de fréquence (FM), fournisse une assistance suffisante pour traiter la parole. Une personne malentendante a difficulté avec les sons, y compris la composante audio des documents multimédias.

Trouble du traitement auditif central

Définition :

Selon le « American Speech-Language-Hearing Association » :

  • Le trouble du traitement auditif (TTA) est souvent décrit comme plus important que prévu difficulté à entendre et à comprendre la parole même si aucune perte audition mesurable existe. Les personnes atteintes de troubles du traitement auditif peuvent agir comme si un une perte auditive est présente alors qu'en fait, la sensibilité auditive est souvent dans des limites normales. Le TTA est souvent confondue avec d'autres troubles tels que le trouble déficitaire de l’attention avec hyperactivité (TDAH), le langage handicap, troubles d'apprentissage, retards sociaux et émotionnels ou troubles cognitifs déficits.
  • Le TTA n'est pas l'incapacité d'entendre. C'est l'incapacité d'interpréter, d'organiser ou d'analyser ce qui est entendu. Toutes les parties de la voie auditive fonctionnent bien, mais pas celles du cerveau.
Caractéristiques :

Les comportements peuvent varier selon les individus et la présence d'autres troubles. Les personnes atteintes d'un trouble du traitement auditif central peuvent avoir des difficultés avec, entre autres :

  • Localiser la source d'un son
  • Comprendre ce que quelqu'un dit dans un environnement bruyant ou avec des sons concurrents
  • Suivre des instructions orales
  • Apprendre des chansons ou des instruments
  • Prêter attention
  • Réagir en temps opportun
  • Apprendre une nouvelle langue

Obstacles pour les personnes ayant une déficience auditive

De l’initiative Web Accessibility de W3C et d'autres sources :

Défis et solutions pour la surdité et les malentendants

Impossible d'entendre les conférences, les présentations et les performances :

Impossible d'entendre la partie audio des vidéos :

Impossible d'entendre les sonnettes, les alarmes et autres alertes :

Technologies adaptive et stratégies d'adaptation

Voici quelques produits couramment utilisés :

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Déficiences auditives

Les déficiences auditives sont des déficiences sensorielles allant d'une perte auditive partielle à complète.

Les déficiences auditives sont des déficiences sensorielles allant d'une perte auditive partielle à complète. Certaines personnes peuvent aussi avoir une ouïe trop sensible (hyperacousie) dans une ou les deux oreilles.

Surdité

Définition :
La surdité est la perte totale ou quasi totale de l'audition.
Caractéristiques :
Une personne sourde ou malentendante a des difficultés avec les sons, y compris la composante audio des documents multimédias. De nombreuses personnes, mais pas toutes, qui sont sourds connaissent la langue des signes. Pour les personnes nées sourdes, la langue des signes est souvent leur première langue et donc leur langue maternelle préférée. Ils peuvent se sentir moins à l'aise pour lire un texte imprimé ou numérique parce que c'est une langue étrangère pour eux et que la notation phonétique n'aide pas leur compréhension. En revanche, ceux qui perdent leur audition plus tard dans la vie (personne sourde postlinguistique) peuvent ne jamais apprendre la langue des signes, ou s'ils l'apprennent, ils peuvent ne pas se sentir aussi à l'aise de parler par signes et peuvent préférer le texte.

Une personne malentendante

Définition :
Les malentendants font référence aux personnes ayant une perte auditive allant de légère à sévère, qui ont encore une audition utile, et peuvent communiquer par la Langue des signes, langue parlée, ou les deux comprennent la langue parlée dans certaines situations, avec ou sans amplification. La plupart des personnes peuvent utiliser le téléphone et utiliser des appareils auditifs.
Caractéristiques :
Les personnes malentendantes ont d'une déficience auditive partielle dans une ou les deux oreilles, ce qui entraîne une perte auditive légère à modérée. L'audition résiduelle peut être suffisante pour qu'un appareil auditif, tel qu'une aide auditive ou un système de modulation de fréquence (FM), fournisse une assistance suffisante pour traiter la parole. Une personne malentendante a difficulté avec les sons, y compris la composante audio des documents multimédias.

Trouble du traitement auditif central

Définition :

Selon le « American Speech-Language-Hearing Association » :

  • Le trouble du traitement auditif (TTA) est souvent décrit comme plus important que prévu difficulté à entendre et à comprendre la parole même si aucune perte audition mesurable existe. Les personnes atteintes de troubles du traitement auditif peuvent agir comme si un une perte auditive est présente alors qu'en fait, la sensibilité auditive est souvent dans des limites normales. Le TTA est souvent confondue avec d'autres troubles tels que le trouble déficitaire de l’attention avec hyperactivité (TDAH), le langage handicap, troubles d'apprentissage, retards sociaux et émotionnels ou troubles cognitifs déficits.
  • Le TTA n'est pas l'incapacité d'entendre. C'est l'incapacité d'interpréter, d'organiser ou d'analyser ce qui est entendu. Toutes les parties de la voie auditive fonctionnent bien, mais pas celles du cerveau.
Caractéristiques :

Les comportements peuvent varier selon les individus et la présence d'autres troubles. Les personnes atteintes d'un trouble du traitement auditif central peuvent avoir des difficultés avec, entre autres :

  • Localiser la source d'un son
  • Comprendre ce que quelqu'un dit dans un environnement bruyant ou avec des sons concurrents
  • Suivre des instructions orales
  • Apprendre des chansons ou des instruments
  • Prêter attention
  • Réagir en temps opportun
  • Apprendre une nouvelle langue

Obstacles pour les personnes ayant une déficience auditive

De l’initiative Web Accessibility de W3C et d'autres sources :

Défis et solutions pour la surdité et les malentendants

Impossible d'entendre les conférences, les présentations et les performances :

Impossible d'entendre la partie audio des vidéos :

Impossible d'entendre les sonnettes, les alarmes et autres alertes :

Technologies adaptive et stratégies d'adaptation

Voici quelques produits couramment utilisés :

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/deficiences-visuelles/index.html b/fr/deficiences-visuelles/index.html index 6acd4fdab..da804d374 100644 --- a/fr/deficiences-visuelles/index.html +++ b/fr/deficiences-visuelles/index.html @@ -1,4 +1,4 @@ -Déficiences visuelles - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Déficiences visuelles

Les déficiences visuelles sont des déficiences sensorielles qui peuvent aller d'une certaine perte de vision, d'une perte d'acuité visuelle ou d'une sensibilité accrue ou diminuée à des couleurs spécifiques ou vives, jusqu'à une perte complète ou non corrigible de la vision de l'un ou des deux yeux.

Cécité

Définition :
La cécité est un handicap sensoriel impliquant une perte de vision presque complète.
Caractéristiques :
Certaines personnes sont complètement aveugles, sans pouvoir voir quoi que ce soit. D'autres peuvent percevoir la lumière par rapport à l'obscurité, ou les formes générales de grands objets, mais ne peuvent pas lire le texte ou reconnaître les gens à vue.

Daltonisme

Définition :
Le daltonisme est un handicap sensoriel qui altère la capacité d'une personne à distinguer certaines combinaisons de couleurs.
Caractéristiques :
Les formes les plus courantes de daltonisme affectent la capacité d'un individu à distinguer les rouges et les verts, bien que d'autres couleurs puissent être affectées.

Basse vision

Définition :

La basse vision est une perte de vision incorrigible qui interfère avec les activités quotidiennes. Elle est mieux définie en termes de fonction plutôt que de résultats de tests numériques.

Caractéristiques :
  • En d'autres termes, la basse vision est « une vision insuffisante pour faire tout ce dont vous avez besoin de faire », qui peut varier d'une personne à l'autre.
  • La plupart des professionnels de la vue préfèrent utiliser le terme « basse vision » pour décrire vision réduite de façon permanente qui ne peut pas être corrigée avec des lunettes ordinaires, lentilles de contact, médicaments ou chirurgie.

Technologies adaptive et stratégies d'adaptation

Voici quelques produits couramment utilisés :

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Déficiences visuelles

Les déficiences visuelles sont des déficiences sensorielles qui peuvent aller d'une certaine perte de vision, d'une perte d'acuité visuelle ou d'une sensibilité accrue ou diminuée à des couleurs spécifiques ou vives, jusqu'à une perte complète ou non corrigible de la vision de l'un ou des deux yeux.

Cécité

Définition :
La cécité est un handicap sensoriel impliquant une perte de vision presque complète.
Caractéristiques :
Certaines personnes sont complètement aveugles, sans pouvoir voir quoi que ce soit. D'autres peuvent percevoir la lumière par rapport à l'obscurité, ou les formes générales de grands objets, mais ne peuvent pas lire le texte ou reconnaître les gens à vue.

Daltonisme

Définition :
Le daltonisme est un handicap sensoriel qui altère la capacité d'une personne à distinguer certaines combinaisons de couleurs.
Caractéristiques :
Les formes les plus courantes de daltonisme affectent la capacité d'un individu à distinguer les rouges et les verts, bien que d'autres couleurs puissent être affectées.

Basse vision

Définition :

La basse vision est une perte de vision incorrigible qui interfère avec les activités quotidiennes. Elle est mieux définie en termes de fonction plutôt que de résultats de tests numériques.

Caractéristiques :
  • En d'autres termes, la basse vision est « une vision insuffisante pour faire tout ce dont vous avez besoin de faire », qui peut varier d'une personne à l'autre.
  • La plupart des professionnels de la vue préfèrent utiliser le terme « basse vision » pour décrire vision réduite de façon permanente qui ne peut pas être corrigée avec des lunettes ordinaires, lentilles de contact, médicaments ou chirurgie.

Technologies adaptive et stratégies d'adaptation

Voici quelques produits couramment utilisés :

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/directives-pour-la-description-sonore/index.html b/fr/directives-pour-la-description-sonore/index.html index a6b5776e6..c23691682 100644 --- a/fr/directives-pour-la-description-sonore/index.html +++ b/fr/directives-pour-la-description-sonore/index.html @@ -1,4 +1,4 @@ -Directives pour la description sonore - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Directives pour la description sonore

La description sonore permet à tout utilisateur souffrant d’un handicap visuel ou cognitif de recevoir une expérience très détaillée et descriptive de ce qui se passe à l’écran pour chaque aspect de la vidéo.

La description sonore (DS) est parfois appelée vidéo décrite (VD), vidéodescription ou interprétation visuelle. Elle permet à tout utilisateur souffrant d’un handicap visuel ou cognitif de recevoir une expérience très détaillée et descriptive de ce qui se passe à l’écran pour chaque aspect de la vidéo. Un certain nombre d’organismes exigent la description sonore et la vidéo décrite, ou la description vidéo dans la vidéo, comme le CRTC.

La description sonore est également utilisée par les personnes voyantes, de sorte que les éléments audio et vidéo sont tous deux nécessaires (p. ex. une personne souffrant d’une légère perte de vision qui n’a pas pu lire le texte, mais souhaite voir le reste).

La description sonore et la vidéo décrite rendent les programmes télévisés accessibles aux personnes aveugles ou ayant une déficience visuelle :

Description sonore
Elle consiste en une voix hors champ produite par un animateur ou un annonceur qui lit à haute voix le texte de l’émission ou qui décrit les éléments-clés, les images ou les graphiques diffusés à l’écran. Elle est souvent utilisée pour les émissions d’information, notamment les bulletins de nouvelles, les bulletins météorologiques, les résultats sportifs ou les informations financières. La plupart des télédiffuseurs sont tenus d’offrir une description sonore.
Vidéodescription
Elle offre une description orale des principaux éléments visuels d’une émission, comme les décors, les costumes ou le langage corporel. La description est ajoutée pendant les pauses dans le dialogue et elle permet au téléspectateur de se représenter mentalement ce qui se passe dans l’émission. La vidéodescription utilise une piste audio distincte.

Source : CRTC – Accès à la télévision pour les personnes ayant une déficience visuelle : Vidéodescription et description sonore.

Remarque : Si une description sonore est utilisée pour une vidéo, elle doit être incluse dans la transcription.

Liste de contrôle pour la description sonore

La description audio :

La description audio est-elle :

Directives d’accès au clavier

Les lecteurs multimédias accessibles fournissent une interface utilisateur qui fonctionne sans souris, par le biais d'une interface vocale, lorsque la page est agrandie et avec des lecteurs d'écran. Par exemple, les lecteurs multimédias doivent :

Certains lecteurs multimédias offrent des fonctionnalités d'accessibilité supplémentaires aux utilisateurs, telles que :

Liste de contrôle d’accès au clavier

En utilisant un clavier, le lecteur média :

Le lecteur média temporel prend-il en charge (possède-t-il une icône/un lien pour) ce qui suit :

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Directives pour la description sonore

La description sonore permet à tout utilisateur souffrant d’un handicap visuel ou cognitif de recevoir une expérience très détaillée et descriptive de ce qui se passe à l’écran pour chaque aspect de la vidéo.

La description sonore (DS) est parfois appelée vidéo décrite (VD), vidéodescription ou interprétation visuelle. Elle permet à tout utilisateur souffrant d’un handicap visuel ou cognitif de recevoir une expérience très détaillée et descriptive de ce qui se passe à l’écran pour chaque aspect de la vidéo. Un certain nombre d’organismes exigent la description sonore et la vidéo décrite, ou la description vidéo dans la vidéo, comme le CRTC.

La description sonore est également utilisée par les personnes voyantes, de sorte que les éléments audio et vidéo sont tous deux nécessaires (p. ex. une personne souffrant d’une légère perte de vision qui n’a pas pu lire le texte, mais souhaite voir le reste).

La description sonore et la vidéo décrite rendent les programmes télévisés accessibles aux personnes aveugles ou ayant une déficience visuelle :

Description sonore
Elle consiste en une voix hors champ produite par un animateur ou un annonceur qui lit à haute voix le texte de l’émission ou qui décrit les éléments-clés, les images ou les graphiques diffusés à l’écran. Elle est souvent utilisée pour les émissions d’information, notamment les bulletins de nouvelles, les bulletins météorologiques, les résultats sportifs ou les informations financières. La plupart des télédiffuseurs sont tenus d’offrir une description sonore.
Vidéodescription
Elle offre une description orale des principaux éléments visuels d’une émission, comme les décors, les costumes ou le langage corporel. La description est ajoutée pendant les pauses dans le dialogue et elle permet au téléspectateur de se représenter mentalement ce qui se passe dans l’émission. La vidéodescription utilise une piste audio distincte.

Source : CRTC – Accès à la télévision pour les personnes ayant une déficience visuelle : Vidéodescription et description sonore.

Remarque : Si une description sonore est utilisée pour une vidéo, elle doit être incluse dans la transcription.

Liste de contrôle pour la description sonore

La description audio :

La description audio est-elle :

Directives d’accès au clavier

Les lecteurs multimédias accessibles fournissent une interface utilisateur qui fonctionne sans souris, par le biais d'une interface vocale, lorsque la page est agrandie et avec des lecteurs d'écran. Par exemple, les lecteurs multimédias doivent :

Certains lecteurs multimédias offrent des fonctionnalités d'accessibilité supplémentaires aux utilisateurs, telles que :

Liste de contrôle d’accès au clavier

En utilisant un clavier, le lecteur média :

Le lecteur média temporel prend-il en charge (possède-t-il une icône/un lien pour) ce qui suit :

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/ecole-de-la-fonction-publique-du-canada-efpc/index.html b/fr/ecole-de-la-fonction-publique-du-canada-efpc/index.html index 41d808273..43504e2ea 100644 --- a/fr/ecole-de-la-fonction-publique-du-canada-efpc/index.html +++ b/fr/ecole-de-la-fonction-publique-du-canada-efpc/index.html @@ -1,4 +1,4 @@ -École de la fonction publique du Canada (EFPC) - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

École de la fonction publique du Canada (EFPC)

L'École de la fonction publique du Canada dirige l'approche pangouvernementale en matière d'apprentissage en offrant un programme de cours commun normalisé qui appuie les fonctionnaires aux points tournants de leur carrière, afin d'assurer qu'ils sont outillés pour servir les Canadiens en respectant les plus hauts critères d'excellence. Plusieurs équipes de l’École soutiennent l'accessibilité numérique dans le but de créer un environnement d'apprentissage sans obstacles pour ses apprenants.

L'équipe des politiques, des priorités et des partenariats

L'équipe des politiques, des priorités et des partenariats de l'École de la fonction publique du Canada (EFPC) a élaboré la stratégie sur l’accessibilité de l'École. Alors que l’ensemble du gouvernement du Canada veille à atteindre l’objectif d’un Canada sans obstacle d'ici 2040, à l'École, nous nous assurons que tous nos outils liés aux politiques internes sont conformes aux exigences d'accessibilité prévues par la Loi sur l'accessibilité. En collaboration avec l'équipe de l'Avenir du travail, le Forum sur la diversité et l'inclusion et la Plateformes d’apprentissage – Expérience utilisateur (UX), nous travaillons d’arrache-pied à la réalisation des initiatives actuelles et futures inclues dans la stratégie sur l’accessibilité.

L'équipe de l’Avenir du travail/Expérience employé de l'EFPC

L’équipe de l’Avenir du travail / Expérience employé de l'EFPC travaille à la création du plan d'accessibilité de l’organisation, comme l'exige la Loi sur l'accessibilité du Canada. Le plan est basé sur la stratégie d'accessibilité actuelle de l'EFPC, tout en s'assurant que l'EFPC est conforme aux nouveaux règlements techniques d'accessibilité du Canada.

L'équipe de l'Avenir du travail coordonnera avec tous les secteurs d'activité de l'EFPC concernés par la politique d'accessibilité, tant du point de vue des employeurs que des fournisseurs de services. De plus, nous mènerons des consultations avec les employés qui s'identifient comme des personnes handicapées pendant le processus de préparation du plan d'accessibilité qui devrait être publié avant décembre 2022.

L'équipe de l’Académie du numérique

L'École de la fonction publique du Canada (EFPC) a créé l'Académie du numérique de l'EFPC en 2018. L'objectif de ce secteur d'activité est d'apprendre aux fonctionnaires fédéraux du Canada les compétences, les approches et les mentalités numériques nécessaires pour transformer les services publics en cette ère numérique. L'Académie du numérique soutient les principes de l'initiative Au-delà de 2020 pour un milieu de travail agile, inclusif et mieux outillé, et milite pour une approche axée sur la numérique qui s'harmonise aux normes numériques du gouvernement du Canada. Ces 10 normes numériques constituent les fondements de la transition vers un gouvernement plus agile, ouvert et axé sur le numérique. L'une des normes numériques consiste à intégrer l'accessibilité dès le départ. L'Académie du numérique de l'EFPC s'efforce de le faire dans son travail, et nous cocréons du contenu pour aider d'autres fonctionnaires à faire de même.

Le secteur d'activité Milieu de travail respectueux et inclusif (MTRI)

Le secteur d'activité Milieu de travail respectueux et inclusif (MTRI) de l'EFPC est responsable du développement et de la livraison de produits d'apprentissage sur l'accessibilité pour les fonctionnaires fédéraux. MTRI travaille en étroite collaboration avec des partenaires tels que le Bureau de l'accessibilité de la fonction publique (BASP), le Bureau du dirigeant principal des ressources humaines (BDPRH), l'équipe de l'accessibilité, de l'adaptation et de la technologie informatique adaptée (AA) et de nombreux autres intervenants pour créer des expériences d'apprentissage informatives, novatrices et engageantes sur le thème de l'accessibilité.

L'équipe de l’Accessibilité numérique en apprentissage

L'équipe d'accessibilité numérique en apprentissage de l'EFPC, qui fait partie de la division de l'expérience utilisateur, fournit à nos secteurs d'activité une formation, des outils, des directives et des conseils pour répondre aux normes d'accessibilité afin qu'ils puissent offrir aux apprenants une expérience d'apprentissage significative, inclusive et accessible. L'accessibilité doit se faire par conception et par défaut. Nous sommes là pour :

  • Mener le changement de culture vers une conception accessible et inclusive par la formation et le soutien technologique.
  • Établir et renforcer les meilleures pratiques de conception accessible et inclusive dès le départ.
  • Soutenir l'achat de solutions d'apprentissage accessibles et d'outils de création accessibles.
  • Collaborer avec d'autres spécialistes de l'accessibilité, de la conception, de la recherche et de l'utilisabilité au sein de l'École et dans l'ensemble de la fonction publique.
  • Établir des lignes directrices, des pratiques exemplaires et des processus pour la mise en œuvre et le maintien de produits et services accessibles et inclusifs.
  • Assurer l'encadrement et le perfectionnement professionnel des employés de l'École en matière d'accessibilité.

Pour en savoir plus sur l'inclusion et l'accessibilité, ou pour obtenir de l'aide pour la conception ou le développement de votre apprentissage, veuillez contacter

digitalaccessibilityinlearning-accessibilitenumerique@csps-efpc.gc.ca

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

École de la fonction publique du Canada (EFPC)

L'École de la fonction publique du Canada dirige l'approche pangouvernementale en matière d'apprentissage en offrant un programme de cours commun normalisé qui appuie les fonctionnaires aux points tournants de leur carrière, afin d'assurer qu'ils sont outillés pour servir les Canadiens en respectant les plus hauts critères d'excellence. Plusieurs équipes de l’École soutiennent l'accessibilité numérique dans le but de créer un environnement d'apprentissage sans obstacles pour ses apprenants.

L'équipe des politiques, des priorités et des partenariats

L'équipe des politiques, des priorités et des partenariats de l'École de la fonction publique du Canada (EFPC) a élaboré la stratégie sur l’accessibilité de l'École. Alors que l’ensemble du gouvernement du Canada veille à atteindre l’objectif d’un Canada sans obstacle d'ici 2040, à l'École, nous nous assurons que tous nos outils liés aux politiques internes sont conformes aux exigences d'accessibilité prévues par la Loi sur l'accessibilité. En collaboration avec l'équipe de l'Avenir du travail, le Forum sur la diversité et l'inclusion et la Plateformes d’apprentissage – Expérience utilisateur (UX), nous travaillons d’arrache-pied à la réalisation des initiatives actuelles et futures inclues dans la stratégie sur l’accessibilité.

L'équipe de l’Avenir du travail/Expérience employé de l'EFPC

L’équipe de l’Avenir du travail / Expérience employé de l'EFPC travaille à la création du plan d'accessibilité de l’organisation, comme l'exige la Loi sur l'accessibilité du Canada. Le plan est basé sur la stratégie d'accessibilité actuelle de l'EFPC, tout en s'assurant que l'EFPC est conforme aux nouveaux règlements techniques d'accessibilité du Canada.

L'équipe de l'Avenir du travail coordonnera avec tous les secteurs d'activité de l'EFPC concernés par la politique d'accessibilité, tant du point de vue des employeurs que des fournisseurs de services. De plus, nous mènerons des consultations avec les employés qui s'identifient comme des personnes handicapées pendant le processus de préparation du plan d'accessibilité qui devrait être publié avant décembre 2022.

L'équipe de l’Académie du numérique

L'École de la fonction publique du Canada (EFPC) a créé l'Académie du numérique de l'EFPC en 2018. L'objectif de ce secteur d'activité est d'apprendre aux fonctionnaires fédéraux du Canada les compétences, les approches et les mentalités numériques nécessaires pour transformer les services publics en cette ère numérique. L'Académie du numérique soutient les principes de l'initiative Au-delà de 2020 pour un milieu de travail agile, inclusif et mieux outillé, et milite pour une approche axée sur la numérique qui s'harmonise aux normes numériques du gouvernement du Canada. Ces 10 normes numériques constituent les fondements de la transition vers un gouvernement plus agile, ouvert et axé sur le numérique. L'une des normes numériques consiste à intégrer l'accessibilité dès le départ. L'Académie du numérique de l'EFPC s'efforce de le faire dans son travail, et nous cocréons du contenu pour aider d'autres fonctionnaires à faire de même.

Le secteur d'activité Milieu de travail respectueux et inclusif (MTRI)

Le secteur d'activité Milieu de travail respectueux et inclusif (MTRI) de l'EFPC est responsable du développement et de la livraison de produits d'apprentissage sur l'accessibilité pour les fonctionnaires fédéraux. MTRI travaille en étroite collaboration avec des partenaires tels que le Bureau de l'accessibilité de la fonction publique (BASP), le Bureau du dirigeant principal des ressources humaines (BDPRH), l'équipe de l'accessibilité, de l'adaptation et de la technologie informatique adaptée (AA) et de nombreux autres intervenants pour créer des expériences d'apprentissage informatives, novatrices et engageantes sur le thème de l'accessibilité.

L'équipe de l’Accessibilité numérique en apprentissage

L'équipe d'accessibilité numérique en apprentissage de l'EFPC, qui fait partie de la division de l'expérience utilisateur, fournit à nos secteurs d'activité une formation, des outils, des directives et des conseils pour répondre aux normes d'accessibilité afin qu'ils puissent offrir aux apprenants une expérience d'apprentissage significative, inclusive et accessible. L'accessibilité doit se faire par conception et par défaut. Nous sommes là pour :

  • Mener le changement de culture vers une conception accessible et inclusive par la formation et le soutien technologique.
  • Établir et renforcer les meilleures pratiques de conception accessible et inclusive dès le départ.
  • Soutenir l'achat de solutions d'apprentissage accessibles et d'outils de création accessibles.
  • Collaborer avec d'autres spécialistes de l'accessibilité, de la conception, de la recherche et de l'utilisabilité au sein de l'École et dans l'ensemble de la fonction publique.
  • Établir des lignes directrices, des pratiques exemplaires et des processus pour la mise en œuvre et le maintien de produits et services accessibles et inclusifs.
  • Assurer l'encadrement et le perfectionnement professionnel des employés de l'École en matière d'accessibilité.

Pour en savoir plus sur l'inclusion et l'accessibilité, ou pour obtenir de l'aide pour la conception ou le développement de votre apprentissage, veuillez contacter

digitalaccessibilityinlearning-accessibilitenumerique@csps-efpc.gc.ca

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/emploi-et-developpement-social-canada-edsc/index.html b/fr/emploi-et-developpement-social-canada-edsc/index.html index e8455ee64..d2ebf16c2 100644 --- a/fr/emploi-et-developpement-social-canada-edsc/index.html +++ b/fr/emploi-et-developpement-social-canada-edsc/index.html @@ -1,4 +1,4 @@ -Emploi et Développement social Canada (EDSC) - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Emploi et Développement social Canada (EDSC)

Emploi et Développement social Canada (EDSC) travaille à améliorer le niveau de vie et la qualité de vie de tous les Canadiens en faisant la promotion d'une main-d'œuvre mobile et hautement spécialisée ainsi que d'un marché du travail efficace et favorable à l'inclusion. EDSC compte plusieurs équipes travaillant dans le domaine de l'accessibilité numérique dans le but de créer un environnement sans obstacle pour les Canadiens et les employés !

Bureau de l'accessibilité de EDSC

Le Bureau de l’accessibilité de EDSC est responsable de l’élaboration et de la mise en œuvre du plan d’accessibilité du Ministère, notamment de veiller à ce que les exigences de la Loi canadienne sur l’accessibilité relatives à la publication du plan, à la réception de la rétroaction et aux rapports sur les progrès soient respectées. Le Bureau de l'Accessibilité de EDSC collabore avec des partenaires à l’intérieur et à l’extérieur d’EDSC et les réunit en travaillant horizontalement ensemble pour atteindre l’objectif consistant à cerner, éliminer et prévenir les obstacles à l’accessibilité.

Bureau de l’accessibilité des TI

Le Bureau de l’accessibilité des TI (BATI) demeure un fournisseur de la technologie adaptative, ainsi qu’un défenseur de l’inclusion des personnes ayant un handicap en milieu de travail. Nous sommes des chefs reconnus, engagés dans notre mandat d’accessibilité, et continuons à offrir du soutien aux employés ayant un handicap. Conformément à la Loi canadienne sur l’accessibilité, et en collaboration avec nos partenaires des agences centrales nous recommandons des normes, des lignes directrices et des pratiques exemplaires reconnues à l'échelle internationale. L'éventail de nos services couvre des sujets tels que l'approvisionnement, la formation, la sensibilisation, l'évaluation de produits ainsi que des conseils d’experts sur l’Accessibilité en Technologie de l’information et des communications (TIC).

Centre d'expertise pour le service à la clientèle accessible

Le Centre d'expertise pour le service à la clientèle accessible aide à promouvoir une culture axée sur l'accessibilité en offrant des conseils et un soutien afin :

  • d’intégrer les principes de conception universelle aux initiatives nouvelles ou existantes axées sur la conception de programmes et l'amélioration des services;
  • de comprendre le mode de vie des personnes ayant un handicap et les obstacles qu'elles doivent surmonter pour avoir accès aux services;
  • de trouver des moyens de faciliter l'accès aux programmes et aux services qu'il offre;
  • de diriger la conception et la prestation de programmes et de services pour atteindre l’objectif 4 de la Stratégie sur l’accessibilité au sein de la fonction publique du Canada.

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Emploi et Développement social Canada (EDSC)

Emploi et Développement social Canada (EDSC) travaille à améliorer le niveau de vie et la qualité de vie de tous les Canadiens en faisant la promotion d'une main-d'œuvre mobile et hautement spécialisée ainsi que d'un marché du travail efficace et favorable à l'inclusion. EDSC compte plusieurs équipes travaillant dans le domaine de l'accessibilité numérique dans le but de créer un environnement sans obstacle pour les Canadiens et les employés !

Bureau de l'accessibilité de EDSC

Le Bureau de l’accessibilité de EDSC est responsable de l’élaboration et de la mise en œuvre du plan d’accessibilité du Ministère, notamment de veiller à ce que les exigences de la Loi canadienne sur l’accessibilité relatives à la publication du plan, à la réception de la rétroaction et aux rapports sur les progrès soient respectées. Le Bureau de l'Accessibilité de EDSC collabore avec des partenaires à l’intérieur et à l’extérieur d’EDSC et les réunit en travaillant horizontalement ensemble pour atteindre l’objectif consistant à cerner, éliminer et prévenir les obstacles à l’accessibilité.

Bureau de l’accessibilité des TI

Le Bureau de l’accessibilité des TI (BATI) demeure un fournisseur de la technologie adaptative, ainsi qu’un défenseur de l’inclusion des personnes ayant un handicap en milieu de travail. Nous sommes des chefs reconnus, engagés dans notre mandat d’accessibilité, et continuons à offrir du soutien aux employés ayant un handicap. Conformément à la Loi canadienne sur l’accessibilité, et en collaboration avec nos partenaires des agences centrales nous recommandons des normes, des lignes directrices et des pratiques exemplaires reconnues à l'échelle internationale. L'éventail de nos services couvre des sujets tels que l'approvisionnement, la formation, la sensibilisation, l'évaluation de produits ainsi que des conseils d’experts sur l’Accessibilité en Technologie de l’information et des communications (TIC).

Centre d'expertise pour le service à la clientèle accessible

Le Centre d'expertise pour le service à la clientèle accessible aide à promouvoir une culture axée sur l'accessibilité en offrant des conseils et un soutien afin :

  • d’intégrer les principes de conception universelle aux initiatives nouvelles ou existantes axées sur la conception de programmes et l'amélioration des services;
  • de comprendre le mode de vie des personnes ayant un handicap et les obstacles qu'elles doivent surmonter pour avoir accès aux services;
  • de trouver des moyens de faciliter l'accès aux programmes et aux services qu'il offre;
  • de diriger la conception et la prestation de programmes et de services pour atteindre l’objectif 4 de la Stratégie sur l’accessibilité au sein de la fonction publique du Canada.

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/evenements-virtuels-accessibles/index.html b/fr/evenements-virtuels-accessibles/index.html index baa5fbb36..8c2b11f60 100644 --- a/fr/evenements-virtuels-accessibles/index.html +++ b/fr/evenements-virtuels-accessibles/index.html @@ -9,4 +9,4 @@ w.gtag('js', new Date()); w.gtag('config', 'G-SM9MSHWDVN'); } - })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Événements virtuels accessibles

Afin de vous aider à organiser et offrir une réunion/un événement virtuel entièrement accessible, qu'il s'agisse d'une session de formation, d'une réunion, d'un kiosque ou d'un événement portes ouvertes.

Bonnes pratiques pour les événements virtuels accessibles

Ce guide porte sur la planification d’événements, couvrant un large éventail d’activités comme des conférences, des réunions, et des présentations. Il comprend les obstacles courants auxquels les personnes en situation d’handicap sont confrontées lors des événements et un calendrier suggéré pour l’organisation de votre événement. L’objectif est de travailler ensemble pour créer des expériences plus inclusives et accessibles.

Services CART et interprètes en langue des signes (SLI)

Les services d'hébergement les plus courants pour les réunions ou les événements sont les services de transcription en temps réel assistés par ordinateur (CART) et d'interprétation.

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Événements virtuels accessibles

Afin de vous aider à organiser et offrir une réunion/un événement virtuel entièrement accessible, qu'il s'agisse d'une session de formation, d'une réunion, d'un kiosque ou d'un événement portes ouvertes.

Bonnes pratiques pour les événements virtuels accessibles

Ce guide porte sur la planification d’événements, couvrant un large éventail d’activités comme des conférences, des réunions, et des présentations. Il comprend les obstacles courants auxquels les personnes en situation d’handicap sont confrontées lors des événements et un calendrier suggéré pour l’organisation de votre événement. L’objectif est de travailler ensemble pour créer des expériences plus inclusives et accessibles.

Services CART et interprètes en langue des signes (SLI)

Les services d'hébergement les plus courants pour les réunions ou les événements sont les services de transcription en temps réel assistés par ordinateur (CART) et d'interprétation.

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/exigences-en-matiere-de-technologies-de-l-information-et-des-communications-tic-accessibles/index.html b/fr/exigences-en-matiere-de-technologies-de-l-information-et-des-communications-tic-accessibles/index.html index 32dfd54d6..b41886a34 100644 --- a/fr/exigences-en-matiere-de-technologies-de-l-information-et-des-communications-tic-accessibles/index.html +++ b/fr/exigences-en-matiere-de-technologies-de-l-information-et-des-communications-tic-accessibles/index.html @@ -1,4 +1,4 @@ -Exigences en matière de technologies de l’information et des communications (TIC) accessibles - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Exigences en matière de technologies de l’information et des communications (TIC) accessibles

Cette page a pour but de partager une partie du travail effectué par Services partagés Canada (SPC) pour le pilotage des normes harmonisées d'accessibilité des technologies de l’information et des communications (TIC) EN 301 549 (2021). Il ne s'agit pas d'un copier / coller / traduction complet des normes, l'EN 301 549 (2021) ou le Web Content Accessibility Guidelines (WCAG) 2.1.

Exigences en matière de technologies de l’information et des communications (TIC) accessibles ( Word, 636 ko)

Que sont les TIC?

Les technologies de l’information et des communications (TIC) comprennent le matériel, les logiciels, les communications vocales, les capacités vidéo et le contenu numérique (y compris l’information sur le Web et ailleurs).

Qu’est-ce que l’accessibilité des TIC et pourquoi est-elle importante?

« L’accessibilité des TIC permet aux personnes handicapées et non handicapées d’accéder aux mêmes informations, d’accomplir les mêmes tâches et de recevoir les mêmes services grâce aux technologies de l’information. C’est l’équivalent numérique de l’accessibilité dans l’environnement physique – les bateaux de trottoir, les rampes d’accès, les garde-corps, etc. L’accessibilité des TIC peut offrir des avantages en termes d’ergonomie à tous ceux qui utilisent les TIC, mais elle est essentielle pour de nombreuses personnes handicapées. » - NASCIO - Accessibilité en matière d’acquisition de TI (en anglais seulement).

À propos du présent document et avis de droit d’auteur

Ce document reproduit les exigences pertinentes du EN 301 549 v3.2.1 (2021-03) norme européenne harmonisée « Exigences en accessibilité pour les produits et services en TIC », disponible en anglais seulement, (© utilisé sous la licence de l’Institut Européen de Normalisation des Télécommunications 2021. © Comité Européen de Normalisation 2021. © Comité Européen de Normalisation Électrotechnique 2021. Tous droits réservés.), ce qui inclut les Règles pour l'accessibilité des contenus Web (WCAG) 2.1 de niveau AA.

Les droits de propriété intellectuelle (DPI) essentiels ou potentiellement essentiels aux livrables normatifs peuvent avoir été déclarés à l'ETSI. Les informations relatives à ces DPI essentiels, le cas échéant, sont accessibles au public pour les membres et les non-membres de l'ETSI, dans ETSI SR 000 314 : « Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards », disponible auprès du secrétariat de l'ETSI. Les dernières mises à jour sont disponibles sur le serveur Web ETSI (https://ipr.etsi.org/) (en anglais seulement). Veuillez consulter la base de données ETSI IPR (en anglais seulement) pour la recherche de DPI.

Le présent document contient des exigences qui, à première vue, peuvent sembler sans rapport avec ce produit ou de service. Elles ont été incluses aux fins de considération puisqu’il est impossible de savoir ce qui pourrait être inclus dans le produit ou service d’un fournisseur. Par exemple, une vidéo peut être intégrée à la documentation d’un produit et les exigences en matière d’accessibilité pour la vidéo et l’audio peuvent devenir pertinentes.

Les annexes comprennent des définitions, des références et un guide pratique portant sur la création d’une documentation accessible.

Sources utilisées pour compiler le présent document

Sur cette page

Vous pouvez trouver ici des informations partielles et les présenter en deux langues à titre informatif. Les marchés publics spécifiques auront les exigences appropriées en matière de TIC dans le dossier d'appel d'offres.

Partie A - Énoncés de rendement fonctionnel

Il s’agit d’énoncés explicatifs (non testables) qui présentent les aspects essentiels que le produit ou le service offert doit fournir pour être jugé accessible.

4.2.1 Utilisation sans vision: Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas la vision.

4.2.2 Utilisation avec vision limitée: Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec des fonctions leur permettant de mieux utiliser leur vision limitée.

4.2.3 Utilisation sans perception des couleurs: Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec un mode de fonctionnement visuel qui n’exige pas la perception des couleurs par les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une perception limitée des couleurs et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.4 Utilisation sans audition: Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas l’audition. Ceci est essentiel pour les utilisateurs sans audition et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.5 Utilisation avec audition limitée: Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin des TIC avec des fonctions audio améliorées. Ceci est essentiel pour les utilisateurs ayant une audition limitée et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.6 Utilisation sans capacité vocale: Lorsque les TIC nécessitent la contribution vocale des utilisateurs, certains utilisateurs auront besoin des TIC pour fournir au moins un mode de fonctionnement qui n’exige pas d’entrée vocale. Ceci est essentiel pour les utilisateurs sans capacité vocale ou ayant une capacité vocale limitée et est bénéfique à plusieurs autres dans différentes situations.

4.2.7 Utilisation avec une capacité de manipulation ou de force limitée: Lorsque les TIC nécessitent des actions manuelles, certains utilisateurs auront besoin de TIC avec des caractéristiques qui permettent aux utilisateurs d’utiliser les TIC par d’autres actions ne nécessitant aucune manipulation ou force de la main. Ceci est essentiel pour les utilisateurs ayant une capacité de manipulation ou de force limitée et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.8 Utilisation à portée limitée: Lorsque les produits des TIC sont autonomes ou installés, les éléments opérationnels doivent être à la portée de tous les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une portée limitée et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.9 Minimiser les déclencheurs de convulsions liées à une condition photosensible: lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs ont besoin de TIC avec au moins un mode de fonctionnement qui minimise le risque de déclencher des convulsions liées à une condition photosensible. Ceci est essentiel pour les utilisateurs présentant des déclencheurs de crise photosensibles.

4.2.10 Utilisation avec des capacités cognitives, linguistiques ou d’apprentissage limitées: Les TIC fournissent des fonctions et/ou une présentation qui simplifient la compréhension, le fonctionnement et l’utilisation. Ceci est essentiel pour les utilisateurs ayant des capacités cognitives, linguistiques ou d’apprentissage limitées et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.11. Confidentialité : Lorsque les TIC fournissent des fonctions d’accessibilité, elles préservent la confidentialité des utilisateurs de ces fonctions au même niveau que celle des autres utilisateurs.

Partie B - Exigences en matière d’accessibilité fonctionnelle

Explication des colonnes du tableau

Portée

Les exigences en matière d’accessibilité fonctionnelle suivantes s’appliquent aux énoncés de rendement fonctionnel de la partie A. Si une solution répond à toutes ces exigences, elle est considérée comme ayant satisfait aux énoncés de rendement fonctionnel et est donc jugée conforme à la norme EN 301 549 V3.2.1.

Clauses jugées pertinentes pour ce TIC

Clauses jugées pertinentes pour ce TIC

  • 5
  • 5.1
  • 5.1.1
  • 5.1.2
  • 5.1.2.1
  • 5.1.2.2
  • 5.1.3
  • 5.1.3.1
  • 5.1.3.2
  • 5.1.3.3
  • 5.1.3.4
  • 5.1.3.5
  • 5.1.3.6
  • 5.1.3.7
  • 5.1.3.8
  • 5.1.3.9
  • 5.1.3.10
  • 5.1.3.11
  • 5.1.3.12
  • 5.1.3.13
  • 5.1.3.14
  • 5.1.3.15
  • 5.1.3.16
  • 5.1.4
  • 5.1.5
  • 5.1.6
  • 5.1.6.1
  • 5.1.6.2
  • 5.1.7
  • 5.2
  • 5.3
  • 5.4
  • 5.5
  • 5.5.1
  • 5.5.2
  • 5.6
  • 5.6.1
  • 5.6.2
  • 5.7
  • 5.8
  • 5.9
  • 6
  • 6.1
  • 6.2
  • 6.2.1
  • 6.2.1.1
  • 6.2.1.2
  • 6.2.2
  • 6.2.2.1
  • 6.2.2.2
  • 6.2.2.3
  • 6.2.2.4
  • 6.2.3
  • 6.2.4
  • 6.5.5
  • 6.5.6
  • 6.6
  • 7
  • 7.1
  • 7.1.1
  • 7.1.2
  • 7.1.3
  • 7.1.4
  • 7.1.5
  • 7.2
  • 7.2.1
  • 7.2.2
  • 7.2.3
  • 7.3
  • 8
  • 8.1
  • 8.1.1
  • 8.1.2
  • 8.1.3
  • 8.2
  • 8.2.1
  • 8.2.1.1
  • 8.2.1.2
  • 8.2.2
  • 8.2.2.1
  • 8.2.2.2
  • 8.3
  • 8.3.0
  • 8.3.1
  • 8.3.2
  • 8.3.2.1
  • 8.3.2.2
  • 8.3.2.3
  • 8.3.2.3.1
  • 8.3.2.3.2
  • 8.3.2.3.3
  • 8.3.2.4
  • 8.3.2.5
  • 8.3.2.6
  • 8.3.3
  • 8.3.3.1
  • 8.3.3.2
  • 8.3.3.3
  • 8.3.3.3.1
  • 8.3.3.3.2
  • 8.3.4
  • 8.3.4.1
  • 8.3.4.2
  • 8.3.4.3
  • 8.3.4.3.1
  • 8.3.4.3.2
  • 8.3.4.3.3
  • 8.3.5
  • 8.3.6
  • 8.4
  • 8.4.1
  • 8.4.2
  • 8.3.4.3
  • 8.3.4.3.1
  • 8.3.4.3.2
  • 8.3.4.3.3
  • 8.3.5
  • 8.3.6
  • 8.4
  • 8.4.1
  • 8.4.2
  • 8.4.2.1
  • 8.4.2.2
  • 8.4.3
  • 8.5
  • 9
  • 9.0
  • 9.1
  • 9.1.1
  • 9.1.1.1
  • 9.1.2
  • 9.1.2.1
  • 9.1.2.2
  • 9.1.2.3
  • 9.1.2.4
  • 9.1.2.5
  • 9.1.3
  • 9.1.3.1
  • 9.1.3.2
  • 9.1.3.3
  • 9.1.3.4
  • 9.1.3.5
  • 9.1.4
  • 9.1.4.1
  • 9.1.4.2
  • 9.1.4.3
  • 9.1.4.4
  • 9.1.4.5
  • 9.1.4.10
  • 9.1.4.11
  • 9.1.4.12
  • 9.1.4.13
  • 9.2
  • 9.2.1
  • 9.2.1.1
  • 9.2.1.2
  • 9.2.1.4
  • 9.2.2
  • 9.2.2.1
  • 9.2.2.2
  • 9.2.3
  • 9.2.3.1
  • 9.2.4
  • 9.2.4.1
  • 9.2.4.2
  • 9.2.4.3
  • 9.2.4.4
  • 9.2.4.5
  • 9.2.4.6
  • 9.2.4.7
  • 9.2.5
  • 9.2.5.1
  • 9.2.5.2
  • 9.2.5.3
  • 9.2.5.4
  • 9.3
  • 9.3.1
  • 9.3.1.1
  • 9.3.1.2
  • 9.3.2
  • 9.3.2.1
  • 9.3.2.2
  • 9.3.2.3
  • 9.3.2.4
  • 9.3.3
  • 9.3.3.1
  • 9.3.3.2
  • 9.3.3.3
  • 9.3.3.4
  • 9.4
  • 9.4.1
  • 9.4.1.1
  • 9.4.1.2
  • 9.4.1.3
  • 9.5
  • 9.6
  • 10
  • 10.0
  • 10.1
  • 10.1.1
  • 10.1.1.1
  • 10.1.2
  • 10.1.2.1
  • 10.1.2.2
  • 10.1.2.3
  • 10.1.2.4
  • 10.1.2.5
  • 10.1.3
  • 10.1.3.1
  • 10.1.3.2
  • 10.1.3.3
  • 10.1.3.4
  • 10.1.3.5
  • 10.1.4
  • 10.1.4.1
  • 10.1.4.2
  • 10.1.4.3
  • 10.1.4.4
  • 10.1.4.5
  • 10.1.4.10
  • 10.1.4.11
  • 10.1.4.12
  • 10.1.4.13
  • 10.2
  • 10.2.1
  • 10.2.1.1
  • 10.2.1.2
  • 10.2.1.4
  • 10.2.2
  • 10.2.2.1
  • 10.2.2.2
  • 10.2.3
  • 10.2.3.1
  • 10.2.4
  • 10.2.4.2
  • 10.2.4.3
  • 10.2.4.4
  • 10.2.4.6
  • 10.2.4.7
  • 10.2.5
  • 10.2.5.1
  • 10.2.5.2
  • 10.2.5.3
  • 10.2.5.4
  • 10.3
  • 10.3.1
  • 10.3.1.1
  • 10.3.1.2
  • 10.3.2
  • 10.3.2.1
  • 10.3.2.2
  • 10.3.3
  • 10.3.3.1
  • 10.3.3.2
  • 10.3.3.3
  • 10.3.3.4
  • 10.4
  • 10.4.1
  • 10.4.1.1
  • 10.4.1.2
  • 10.4.1.3
  • 10.5
  • 10.6
  • 11
  • 11.0
  • 11.1
  • 11.1.1
  • 11.1.1.1
  • 11.1.1.1.1
  • 11.1.1.1.2
  • 11.1.2
  • 11.1.2.1
  • 11.1.2.1.1
  • 11.1.2.1.2
  • 11.1.2.1.2.1
  • 11.1.2.1.2.2
  • 11.1.2.2
  • 11.1.2.3
  • 11.1.2.3.1
  • 11.1.2.3.2
  • 11.1.2.4
  • 11.1.2.5
  • 11.1.3
  • 11.1.3.1
  • 11.1.3.1.1
  • 11.1.3.1.2
  • 11.1.3.2
  • 11.1.3.2.1
  • 11.1.3.2.2
  • 11.1.3.3
  • 11.1.3.4
  • 11.1.3.5
  • 11.1.3.5.1
  • 11.1.3.5.2
  • 11.1.4.1
  • 11.1.4.2
  • 11.1.4.3
  • 11.1.4.4
  • 11.1.4.4.1
  • 11.1.4.4.2
  • 11.1.4.5
  • 11.1.4.5.1
  • 11.1.4.5.2
  • 11.1.4.10
  • 11.1.4.11
  • 11.1.4.12
  • 11.1.4.13
  • 11.2
  • 11.2.1
  • 11.2.1.1
  • 11.2.1.1.1
  • 11.2.1.1.2
  • 11.2.1.2
  • 11.2.1.4
  • 11.2.1.4.1
  • 11.2.1.4.2
  • 11.2.2
  • 11.2.2.1
  • 11.2.2.2
  • 11.2.3
  • 11.2.3.1
  • 11.2.4
  • 11.2.4.3
  • 11.2.4.4
  • 11.2.4.6
  • 11.2.4.7
  • 11.2.5
  • 11.2.5.1
  • 11.2.5.2
  • 11.2.5.3
  • 11.2.5.3.1
  • 11.2.5.3.2
  • 11.2.5.4
  • 11.3
  • 11.3.1
  • 11.3.1.1
  • 11.3.1.1.1
  • 11.3.1.1.2
  • 11.3.2
  • 11.3.2.1
  • 11.3.2.2
  • 11.3.3
  • 11.3.3.1
  • 11.3.3.1.1
  • 11.3.3.1.2
  • 11.3.3.2
  • 11.3.3.3
  • 11.3.3.4
  • 11.4
  • 11.4.1
  • 11.4.1.1
  • 11.4.1.1.1
  • 11.4.1.1.2
  • 11.4.1.2
  • 11.4.1.2.1
  • 11.4.1.2.2
  • 11.4.1.3
  • 11.4.1.3.1
  • 11.4.1.3.2
  • 11.5
  • 11.5.1
  • 11.5.2
  • 11.5.2.1
  • 11.5.2.2
  • 11.5.2.3
  • 11.5.2.4
  • 11.5.2.5
  • 11.5.2.6
  • 11.5.2.7
  • 11.5.2.8
  • 11.5.2.9
  • 11.5.2.10
  • 11.5.2.11
  • 11.5.2.12
  • 11.5.2.13
  • 11.5.2.14
  • 11.5.2.15
  • 11.5.2.16
  • 11.5.2.17
  • 11.6
  • 11.6.1
  • 11.6.2
  • 11.7
  • 11.8
  • 11.8.1
  • 11.8.2
  • 11.8.3
  • 11.8.4
  • 11.8.5
  • 12
  • 12.1
  • 12.1.1
  • 12.1.2
  • 12.2
  • 12.2.1
  • 12.2.2
  • 12.2.3
  • 12.2.4
  • 13
  • 13.1
  • 13.1.1
  • 13.1.2
  • 13.1.3
  • 13.1.4
  • 13.1.5
  • 13.1.6
  • 13.2
  • 13.3

Se trouve dans cette section

5 Exigences génériques

5.1 Fonction restreinte
Clause de la norme EN 301 549Détermination de la conformité

5.1.1 Introduction (informative)

Les TIC ont des fonctions restreintes pour de nombreuses raisons, y compris en matière de conception ou de politique. Certaines fonctions des produits peuvent être restreinte parce que le produit est autonome et qu’il est interdit aux utilisateurs d’ajouter des périphériques ou des logiciels afin d’accéder à ces fonctions.

Dans la pratique, les TIC peuvent avoir une fonction restreinte même si elles n’ont pas été conçues, développées ou fournies pour être restreinte.

Les ordinateurs qui ne permettent pas aux utilisateurs finaux de régler les paramètres ou d’installer des logiciels sont fonctionnellement restreints.

C.5.1.1 Introduction (informative)

La clause 5.1.1 a une valeur informative et ne contient aucune exigence en matière de tests.

5.1.2 Généralités
Clause de la norme EN 301 549Détermination de la conformité

5.1.2.1 Fonction restreinte

Lorsque les TIC ont une fonctionnalité restreinte, elles doivent satisfaire aux exigences énoncées dans les clauses 5.2 à 13, selon le cas.

REMARQUE 1: Les TIC peuvent restreinte certaines de leurs fonctions, mais pas toutes. Seules les fonctions restreintes doivent être conformes aux exigences de la clause 5.1.

REMARQUE 2: Les dispositions de cette clause sont des exigences relatives à la fonctionnalité restreinte des TIC qui remplacent les exigences des clauses 5.2 à 13 qui stipulent spécifiquement qu’elles ne s’appliquent pas à la fonction restreinte. Cela peut être dû au fait qu’elles sont liées à la compatibilité avec la technologie d’assistance ou à la capacité de l’utilisateur d’ajuster les paramètres d’accessibilité du système dans les produits à fonction restreinte (par exemple, les produits qui empêchent l’accès au panneau de contrôle des paramètres du système).

C.5.1.2.1 Fonction restreinte

Voir les clauses C.5.2 à C.13, selon le cas.

5.1.2.2 Technologie d’assistance

Lorsque les TIC ont une fonction restreinte, cette fonction restreinte doit pouvoir fonctionner sans que l’utilisateur ait à joindre, connecter ou installer une technologie d’assistance et doit être conforme aux exigences génériques des clauses 5.1.3 à 5.1.6 selon le cas. Les casques d’écoute personnels et les boucles inductives ne doivent pas être considérés comme une technologie d’assistance aux fins de la présente clause.

C.5.1.2.2 Technologie d’assistance

Type d’évaluation

Examen

Conditions préalables

1. Les TIC ont des fonctions restreintes.

Procédure

1. Déterminer les fonctions restreintes des TIC.

2. Vérifier que les essais C.5.1.3 à C.5.1.6 peuvent être effectués sans installation d’une technologie d’assistance, à l’exception des casques personnels ou des boucles inductives.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.3 Accès non visuel
Clause de la norme EN 301 549Détermination de la conformité

5.1.3.1 Général

Lorsque des informations visuelles sont nécessaires pour permettre l’utilisation des fonctions des TIC restreintes aux technologies d’assistance pour la lecture d’écran, les TIC doivent prévoir au moins un mode de fonctionnement utilisant un accès non visuel pour permettre l’utilisation de ces fonctions.

REMARQUE 1: L’accès non visuel peut se faire sous forme audio, y compris la parole, ou sous forme tactile.

REMARQUE 2: Les informations visuelles nécessaires pour permettre l’utilisation de certaines fonctions peuvent inclure les instructions d’utilisation et l’orientation, les invites de transaction, la vérification des entrées utilisateur, les messages d’erreur et le contenu non textuel.

C.5.1.3.1 Général

Type d’évaluation

Examen

Conditions préalables

1. L’information visuelle est nécessaire pour permettre l’utilisation des fonctions des TIC restreintes à la technologie d’assistance pour la lecture d’écran.

Procédure

1. Déterminer les fonctions des TIC fermées à la lecture d’écran.

2. Vérifier qu’elles sont toutes utilisables avec un accès non visuel.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les fonctions sonores doivent être utilisées:

1. soit directement au moyen d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci;

2. soit au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

REMARQUE 1: Les mécanismes intégrés ou fournis peuvent comprendre, mais sans s’y limiter, un haut-parleur, un combiné ou casque intégré ou un autre périphérique accrédité par l’industrie.

REMARQUE 2: Par connexion accréditée par l’industrie, on entend par exemple une connexion sans fil.

REMARQUE 3: Certains utilisateurs pourraient tirer parti d’un équipement à boucle inductive.

C.5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Type d’évaluation

Inspection

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

Procédure

1. Vérifier que la sortie sonore est fournie par le biais d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci.

2. Vérifier que la sortie sonore est fournie au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

Résultat

Réussite: Les énoncés testables nos 1 ou 2 sont vrais.

Échec: Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.3.3 Corrélation de sortie sonore

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que l’information est affichée à l’écran, les TIC doivent fournir des informations auditives qui permettent à l’utilisateur de corréler l’audio avec l’information affichée à l’écran.

REMARQUE 1: De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que la Au focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2: Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées par la présentation.

C.5.1.3.3 Corrélation de sortie sonore

La clause 5.1.3.3 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit pouvoir être interrompue et répétée à la demande de l’utilisateur, lorsque les exigences de sécurité le permettent.

REMARQUE 1: Il est préférable de permettre à l’utilisateur de faire une pause plutôt que de simplement interrompre la sortie vocale.

REMARQUE 2: Il est préférable de permettre à l’utilisateur de ne répéter que la partie la plus récente plutôt que de recommencer depuis le début.

C.5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Type d’évaluation

Inspection

Conditions préalables

1. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

Procédure

1. Vérifier que la sortie vocale peut être interrompue à la demande de l’utilisateur.

2. Vérifier que la sortie vocale peut être répétée à la demande de l’utilisateur.

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: N’importe quel énoncé testable est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.3.5 Interruption automatique de la sortie vocale

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC doivent interrompre la sortie vocale actuelle lorsqu’une action de l’utilisateur se produit et lorsque la nouvelle sortie vocale débute.

REMARQUE: Lorsqu’il est essentiel que l’utilisateur entende l’intégralité du message, par exemple une instruction de sécurité ou un avertissement, les TIC peuvent devoir bloquer toute action de l’utilisateur afin que la parole ne soit pas interrompue.

C.5.1.3.5 Interruption automatique de la sortie vocale

Type d’évaluation

Inspection

Conditions préalables

1. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

Procédure

1. Déterminer les fonctions restreintes des TIC.

2. Vérifier que la sortie vocale de chaque fonction est interrompue lors d’une action de l’utilisateur.

3. Vérifier que la sortie vocale de chaque fonction est interrompue lorsqu’une nouvelle sortie vocale débute.

Résultat

Réussite: Les énoncés testables nos 1, 2 et 3 sont vrais.

Échec: Les énoncés testables nos 2 ou 3 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.3.6 Sortie vocale pour les contenus non textuels

Lorsque les TIC présentent un contenu non textuel, la solution de rechange pour le contenu non textuel doit être présentée aux utilisateurs par le biais d’une sortie vocale, sauf si le contenu non textuel est purement décoratif ou n’est utilisé que pour le formatage visuel. La sortie vocale pour les contenus non textuels doit suivre les indications relatives à « l’équivalent textuel » décrit dans les critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

C.5.1.3.6 Sortie vocale pour les contenus non textuels

Type d’évaluation

Examen

Conditions préalables

1. Le contenu non textuel est présenté aux utilisateurs via la sortie vocale.

Procédure

1. Vérifier que la sortie vocale est fournie comme solution de rechange au contenu non textuel.

2. Vérifier que le contenu non textuel n’est pas seulement présent à titre décoratif.

3. Vérifier que le contenu non textuel n’est pas utilisé uniquement pour le formatage visuel.

4. Vérifier que la sortie vocale est conforme aux indications relatives à l’” équivalent textuel » décrit dans les critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite: Les énoncés testables nos 1, 2, 3 et 4 sont vrais; ou le no 1 et le no 2 sont faux; ou le no 1 et le no 3 sont faux.

Échec: L’énoncé testable no 1 est vrai et le no 2 faux; ou le 1 est vrai et le 3 est faux; ou les nos 1, 2 et 3 sont vrais et le no 4 est faux.

Non applicable: La condition préalable 1 n’est pas remplie.

5.1.3.7 Sortie vocale pour l’information vidéo

Lorsqu’un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation de fonctions restreintes des TIC et que la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit présenter des informations équivalentes pour le contenu vidéo préenregistré.

REMARQUE: Cette sortie vocale peut prendre la forme d’une description audio ou d’une transcription auditive du contenu vidéo.

C.5.1.3.7 Sortie vocale pour l’information vidéo

Type d’évaluation

Examen

Conditions préalables

1. Un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation des fonctions restreintes des TIC.

2. La sortie vocale est fournie comme mode alternatif à une utilisation sans vision du contenu non textuel affiché sur une fonction restreinte.

Procédure

1. Vérifier que la sortie vocale présente des informations équivalentes pour le contenu vidéo préenregistré.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1: Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2: La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

C.5.1.3.8 Entrée masquée

Type d’évaluation

Examen

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. Les caractères affichés sont des caractères de masquage.

3. Toute option permettant d’autoriser une sortie sonore non privée n’a pas été activée.

Procédure

1. Vérifier que la sortie sonore n’est pas une version orale des caractères saisis.

2. Vérifier que la sortie sonore est reconnue comme étant fournie uniquement par le biais d’un mécanisme d’écoute privée.

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: Tous les énoncés testables sont faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies

5.1.3.9 Accès privé aux données personnelles

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que la sortie contient des données considérées comme étant privées conformément à la politique de confidentialité applicable, la sortie sonore correspondante ne peut être fournie que par le biais d’un mécanisme d’écoute privée qui peut être connecté sans nécessiter l’utilisation de la vision, ou par tout autre mécanisme explicitement choisi par l’utilisateur.

REMARQUE 1: Cette exigence ne s’applique pas dans les cas où les données ne sont pas définies comme étant privées conformément à la politique de confidentialité applicable ou lorsqu’il n’existe aucune politique de confidentialité applicable.

REMARQUE 2: La sortie non privée peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

C.5.1.3.9 Accès privé aux données personnelles

Type d’évaluation

Examen

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. La fonction contient des données.

3. Il existe une politique de confidentialité applicable qui considère que ces données sont privées.

Procédure

1. Vérifier que la sortie sonore est fournie uniquement par le biais d’un mécanisme d’écoute privée.

2. Vérifier que le mécanisme d’écoute privée peut être connecté sans nécessiter l’utilisation de la vision.

3. Vérifier que la sortie sonore est fournie par tout autre mécanisme qui peut être choisi par l’utilisateur.

Résultat

Réussite: Les énoncés testables nos 1, 2 et 3 sont vrais.

Échec: Les énoncés testables nos 1, 2 et 3 sont faux.

Non applicable : Les conditions préalables 1 et 3 ne sont pas remplies.

5.1.3.10 Sortie sonore non interférente

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC ne doivent pas lire automatiquement, en même temps, toute sortie audible interférente d’une durée supérieure à trois secondes.

C.5.1.3.10 Sortie sonore non interférente

Type d’évaluation

Examen

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. Les TIC lisent automatiquement la sortie audible interférente.

Procédure

1. Vérifier que la sortie audible interférente ne dure pas plus de trois secondes.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.3.11 Volume d’écoute privé

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, et ce, par le biais d’un mécanisme d’écoute privée, les TIC doivent prévoir au moins un mode de fonctionnement non visuel pour contrôler le volume.

C.5.1.3.11 Volume d’écoute privé

Type d’évaluation

Inspection

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. La sortie sonore est fournie par le biais d’un mécanisme d’écoute privée.

Procédure

1. Vérifier qu’il existe au moins un mode de fonctionnement non visuel pour régler le volume sonore.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.3.12 Volume de l’enceinte

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et qu’elle est fournie par des haut-parleurs sur les TIC, une commande de volume incrémentielle non visuelle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

REMARQUE: Pour les environnements bruyants, 65 dBA peut ne pas être suffisant.

C.5.1.3.12 Volume de l’enceinte

Type d’évaluation

Inspection et établissement de mesures

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. La sortie sonore est fournie par le biais de haut-parleurs.

Procédure

1. Vérifier qu’une commande de volume incrémentielle non visuelle est fournie.

2. Vérifier que l’amplification de sortie est disponible jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.3.13 Réinitialisation du volume

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, une fonction qui réinitialise le volume à un niveau inférieur ou égal à 65 dBA après chaque utilisation doit être fournie, sauf si les TIC sont destinées à un seul utilisateur.

REMARQUE: Une fonction permettant de désactiver la fonction de réinitialisation du volume peut être fournie afin de permettre de respecter l’exception de l’utilisateur unique.

C.5.1.3.13 Réinitialisation du volume

Type d’évaluation

Inspection et établissement de mesures

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. Les TIC ne sont pas dédiées à un seul utilisateur.

Procédure

1. Vérifier qu’une fonction qui réinitialise automatiquement le volume à un niveau de 65 dBA ou moins après chaque utilisation est fournie.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.3.14 Langues parlées

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit être dans la même langue humaine que le contenu affiché fourni, sauf:

1. pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement;

2. lorsque le contenu est généré à l’extérieur et n’est pas sous le contrôle du fournisseur de TIC, La clause présente n’est pas tenue de s’appliquer aux langues non prises en charge par le synthétiseur vocal de TIC;

3. pour les langues affichées qui ne peuvent pas être sélectionnées à l’aide d’un accès non visuel;

4. lorsque l’utilisateur choisit explicitement une langue vocale différente de la langue du contenu affiché.

C.5.1.3.14 Langues parlées

Type d’évaluation

Examen

Conditions préalables

1. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

2. La sortie vocale n’est pas utilisée pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement.

3. Le contenu n’est pas généré à l’extérieur et est sous le contrôle du fournisseur de TIC.

4. Les langues affichées peuvent être sélectionnées à l’aide d’un accès non visuel.

5. L’utilisateur n’a pas sélectionné une langue vocale différente de la langue du contenu affiché.

Procédure

1. Vérifier que la sortie vocale est dans la même langue humaine que le contenu affiché.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : Les conditions préalables 1 et 3 ne sont pas remplies.

5.1.3.15 Détermination non visuelle des erreurs

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte et qu’une erreur d’entrée est automatiquement détectée, la sortie vocale doit identifier et décrire l’élément qui est en erreur.

C.5.1.3.15 Détermination non visuelle des erreurs

Type d’évaluation

Examen

Conditions préalables

1. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

2. Une erreur de saisie est automatiquement détectée.

Procédure

1. Vérifier que la sortie vocale identifie l’élément qui est en erreur.

2. Vérifier que la sortie vocale décrit l’élément qui est en erreur.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.3.16 Reçus, billets et sorties transactionnelles

Lorsque les TIC sont restreints à l’accès visuel et qu’elles fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service, une sortie vocale doit être fournie, comprenant tous les renseignements nécessaires pour conclure ou vérifier la transaction. Dans le cas des distributeurs automatiques de billets, les copies imprimées des itinéraires et des cartes n’ont pas à être audibles.

REMARQUE: La sortie vocale peut être fournie par n’importe quel élément de l’ensemble du système de TIC.

C.5.1.3.16 Reçus, billets et sorties transactionnelles

Type d’évaluation

Examen

Conditions préalables

1. Les TIC sont restreintes à l’accès visuel.

2. Les TIC fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service.

3. Les renseignements vérifiés ne sont pas des copies imprimées des itinéraires et des cartes.

Procédure

1. Vérifier que la sortie vocale est fournie et qu’elle contient tous les renseignements nécessaires pour conclure ou vérifier la transaction.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : Les conditions préalables 1, 2 et 3 ne sont pas remplies.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante:

Ψ = (180 x H)/(π x D)

Où:

· ψ est l’angle sous-tendu en degrés;

· H est la hauteur du texte;

· D est la distance de visibilité;

· D et H sont exprimés dans les mêmes unités.

REMARQUE 1: L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

REMARQUE 2: Le tableau 5.1 et la figure 1 illustrent la relation entre la distance de vision maximale et la hauteur minimale des caractères pour l’angle sous-tendu minimal spécifié.

(Voir le tableau 5.1 et la figure 1.)

C.5.1.4 Fonction restreinte à l’agrandissement du texte

Type d’évaluation

Inspection et établissement de mesures

Conditions préalables

1. Une fonction des TIC ne prend pas en charge les fonctions d’agrandissement de la plateforme ou de la technologie d’assistance.

2. Une distance de visualisation est définie par le fournisseur.

Procédure

1. Mesurer la hauteur de la lettre H en majuscule.

2. Vérifier qu’il sous-tend un angle d’au moins 0,7 degré à la distance de visualisation définie.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.5 Sortie visuelle pour renseignement audio

Lorsque des renseignements audio préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, les TIC doivent fournir des renseignements visuels équivalents aux résultats sonores préenregistrés.

REMARQUE: Ce renseignement visuel peut prendre la forme de sous-titre ou de transcriptions textuelles.

C.5.1.5 Sortie visuelle pour renseignement audio

Type d’évaluation

Inspection

Conditions préalables

1. Un contenu audio préenregistré est nécessaire pour permettre l’utilisation des fonctions restreintes des TIC.

Procédure

1. Vérifier que l’information visuelle est équivalente à la sortie sonore préenregistrée.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

5.1.6 Fonctionnement sans interface clavier
Clause de la norme EN 301 549Détermination de la conformité

5.1.6.1 Fonction restreinte

Lorsque la fonction des TIC est restreinte aux claviers ou aux interfaces clavier, toutes les fonctions doivent pouvoir fonctionner sans vision, comme l’exige la clause 5.1.3.

C.5.1.6.1 Fonction restreinte

Type d’évaluation

Inspection

Conditions préalables

1. La fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier.

Procédure

1. Vérifier que toutes les fonctions sont utilisables sans vision.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.6.2 Focus de la saisie

Lorsque la fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier et que le point d’entrée peut être déplacé vers un élément d’interface utilisateur, il doit être possible d’éloigner le point d’entrée de cet élément en utilisant le même mécanisme, afin d’éviter de piéger le focus de la saisie.

C.5.1.6.2 Focus de la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier.

2. La Au focus d’entrée peut être déplacée vers un élément d’interface utilisateur.

Procédure

1. Vérifier qu’il est possible d’éloigner la Au focus d’entrée de cet élément en utilisant le même mécanisme.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

5.1.7 Accès sans capacité vocale

Lorsque la capacité vocale est nécessaire pour faire fonctionner des fonctions restreintes des TIC, celles-ci doivent prévoir au moins un mode de fonctionnement utilisant un autre mécanisme de saisie ne nécessitant pas la capacité vocale.

C.5.1.7 Accès sans capacité vocale

Type d’évaluation

Inspection

Conditions préalables

1. La capacité vocale est nécessaire pour permettre l’utilisation des fonctions restreintes de TIC.

Procédure

1. Vérifier que les fonctions restreintes peuvent être activées par un autre mécanisme de saisie qui ne nécessite pas la capacité vocale.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.2 Activation des caractéristiques d’accessibilité

Lorsque les TIC sont dotées de caractéristiques d’accessibilité documentées, est-il possible d’activer les caractéristiques requises pour répondre à un besoin particulier sans avoir recours à une méthode qui ne répond pas à ce besoin?

C.5.2 Activation des caractéristiques d’accessibilité

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées de caractéristiques d’accessibilité documentées pour répondre à un besoin spécifique.

Procédure

1. Vérifier qu’il est possible d’activer les caractéristiques d’accessibilité sans avoir recours à une méthode qui ne répond pas à ce besoin.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.3 Données biométriques

Lorsque les TIC utilisent des caractéristiques biologiques, elles ne s’appuient pas sur l’utilisation d’une caractéristique biologique particulière comme seul moyen d’identification de l’utilisateur ou de contrôle des TIC.

REMARQUE 1: D’autres moyens d’identification des utilisateurs ou de contrôle des TIC pourraient être non biométriques ou biométriques.

REMARQUE 2: Les méthodes biométriques fondées sur des caractéristiques biologiques dissemblables augmentent la probabilité que les personnes handicapées possèdent au moins une des caractéristiques biologiques précisées. Les empreintes digitales, les motifs rétiniens des yeux, la voix et le visage sont des exemples de caractéristiques biologiques dissemblables.

C.5.3 Données biométriques

Type d’évaluation

Examen no 1

Conditions préalables

1. Les TIC utilisent des caractéristiques biologiques pour l’identification des utilisateurs.

Procédure

1. Vérifier que plus d’un moyen peut être utilisé pour identifier l’utilisateur.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Type d’évaluation

Examen no 2

Conditions préalables

1. Les TIC utilisent des caractéristiques biologiques pour le contrôle des TIC.

Procédure

1. Vérifiez que plus d’un moyen peut être utilisé pour le contrôle des TIC.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

C.5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Type d’évaluation

Inspection

Conditions préalables

1. Les renseignements libres fournis aux fins d’accessibilité sont documentés.

2. Les TIC convertissent les renseignements ou les communications.

3. Les renseignements libres fournis aux fins d’accessibilité peuvent être contenus dans le format de destination.

4. Les renseignements libres fournis aux fins d’accessibilité peuvent être pris en charge dans le format de destination.

Procédure

1. Vérifier que les renseignements libres fournis aux fins d’accessibilité sont préservés lorsque les TIC convertissent les renseignements ou les communications.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2, 3 ou 4 n’est pas remplie.

5.5 Pièces manœuvrables
Clause de la norme EN 301 549Détermination de la conformité

5.5.1 Moyens de fonctionnement

Lorsque les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

C.5.5.1 Moyens de fonctionnement

Type d’évaluation

Examen

Conditions préalables

Les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner.

Procédure

1. Vérifier qu’il y a un autre moyen de fonctionnement qui n’exige pas de telles actions.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE: Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

C.5.5.2 Perceptibilité des pièces manœuvrables

Type d’évaluation

Examen

Conditions préalables

Les TIC sont dotées de pièces manœuvrables.

Procédure

1. Déterminer qu’il y a moyen de percevoir chaque pièce manœuvrable sans avoir besoin de la vision.

2. Vérifier que l’action associée à la pièce manœuvrable n’a pas été effectuée en utilisant les moyens de perception de chaque pièce manœuvrable de l’étape 1.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.6 Commandes de verrouillage ou de basculement
Clause de la norme EN 301 549Détermination de la conformité

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1: Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2: La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

C.5.6.1 État tactile ou auditif

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées d’une commande de verrouillage ou de basculement.

2. La commande de verrouillage ou de basculement se présente visuellement à l’utilisateur.

Procédure

1. Vérifier qu’au moins un mode de fonctionnement permet de déterminer au toucher l’état de toutes les commandes de verrouillage ou de basculement sans qu’il soit nécessaire d’actionner la commande.

2. Vérifier qu’au moins un mode de fonctionnement permet de déterminer au son l’état de toutes les commandes de verrouillage ou de basculement sans qu’il soit nécessaire d’actionner la commande.

Résultat

Réussite: Les énoncés testables nos 1 ou 2 sont vrais.

Échec: Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

5.6.2 État visuel

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que la commande ne se présente pas visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement permettant de déterminer visuellement l’état de la commande.

REMARQUE 1: Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2: La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. Un indicateur visuel d’état sur un clavier est un exemple de détermination de l’état d’une commande.

C.5.6.2 État visuel

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées d’une commande de verrouillage ou de basculement.

2. La commande de verrouillage ou de basculement se présente à l’utilisateur.

Procédure

1. Vérifier qu’il existe au moins un mode de fonctionnement dans lequel l’état de toutes les commandes de verrouillage ou de basculement peut être déterminé visuellement lorsque la commande se présente.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée:

1. le délai de répétition des touches doit être réglable à au moins 2 secondes;

2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.

C.5.7 Répétition des touches

Type d’évaluation

Examen

Conditions préalables

1. Les TIC sont dotées d’un clavier ou d’un pavé numérique avec une fonction de répétition des touches.

2. La fonction de répétition des touches ne peut pas être désactivée.

Procédure

1. Vérifier que le délai de répétition des touches peut être réglé à au moins 2 secondes.

2. Vérifier que la fréquence de répétition des touches peut être réglée à 2 secondes par caractère.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

5.8 Acceptation de la double frappe

Lorsque les TIC sont dotées d’un clavier ou d’un pavé numérique, le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la pression précédente, doit être réglable jusqu’à au moins 0,5 seconde.

C.5.8 Acceptation de la double frappe

Type d’évaluation

Examen

Conditions préalables

1. Les TIC sont dotées d’un clavier ou d’un pavé numérique.

Procédure

1. Vérifier qu’un mécanisme permet de régler le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la pression précédente.

2. Régler ce mécanisme à son niveau maximal.

3. Appuyer sur n’importe quelle touche.

4. Après un délai de 0,5 seconde, appuyer sur la même touche qu’à l’étape 3.

5. Vérifier si la touche de l’étape 4 a été acceptée.

Résultat

Réussite: L’énoncé testable no 1 est vrai et l’énoncé testable no 5 est faux.

Échec: L’énoncé testable no 1 est faux et l’énoncé testable no 5 est vrai.

Non applicable : La condition préalable 1 n’est pas remplie.

5.9 Actions simultanées de la part de l’utilisateur

Lorsque les TIC requièrent des actions simultanées de la part de l’utilisateur pour fonctionner, ces TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas d’actions simultanées de la part de l’utilisateur pour fonctionner.

REMARQUE: L’utilisation des deux mains pour ouvrir le couvercle d’un ordinateur portable, la pression simultanée de deux ou plusieurs touches ou le contact d’une surface avec plus d’un doigt sont des exemples d’actions simultanées de la part de l’utilisateur.

C.5.9 Actions simultanées de la part de l’utilisateur

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC ont un mode de fonctionnement exigeant des actions simultanées de la part de l’utilisateur.

Aucune

Procédure

1. Vérifier qu’il existe un mode de fonctionnement qui n’exige pas d’actions simultanées de la part de l’utilisateur.

2. Déterminer toutes les fonctions contrôlables par l’utilisateur des TIC.

3. Vérifier que chaque fonction contrôlable par l’utilisateur peut être commandée par une seule action.

Résultat

Réussite: L’énoncé testable no 3 est vrai.

Échec: L’énoncé testable no 3 est faux pour tous les modes de fonctionnement.

Non applicable : La condition préalable 1 n’est pas remplie.

6 Les TIC permettent la communication vocale bidirectionnelle.

Clause de la norme EN 301 549Détermination de la conformité

6.1 Largeur de bande sonore pour la parole

Lorsque les TIC permettent la communication vocale bidirectionnelle, pour offrir une bonne qualité sonore, elles doivent pouvoir coder et décoder la communication vocale bidirectionnelle selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

REMARQUE 1: aux fins de l’interopérabilité, la Recommandation G.722[i.21] de l’UIT-T est largement utilisée.

REMARQUE 2: lorsqu’il y a négociation de codecs, d’autres codecs normalisés tels que la Recommandation G.722.2[i.22] de l’UIT-T sont parfois utilisés afin d’éviter le transcodage.

C.6.1 Largeur de bande sonore pour la parole

Type d’évaluation

Mesure

Conditions préalables

1. Les TIC testées permettent une communication vocale bidirectionnelle.

Procédure

1. Vérifier que les TIC peuvent encoder et décoder selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

6.2 Fonctionnalité de texte en temps réel (TTR)
6.2.1 Fourniture du TTR
Clause de la norme EN 301 549Détermination de la conformité

6.2.1.1 Communication par TTR

Lorsque le mode des TIC prévoit un moyen de communication vocale bidirectionnelle, les TIC doivent fournir un moyen de communication vocale bidirectionnelle par TTR, sauf si cela nécessite des modifications de conception pour ajouter du matériel d'entrée ou de sortie aux TIC.

REMARQUE 1 : Cette exigence inclut les produits qui ne sont pas dotés de fonctionnalités d’affichage physique ou de saisie de texte mais qui ont la capacité de se connecter à des périphériques qui possèdent de telles fonctionnalités. Elle inclut également les TIC intermédiaires situés entre les points finaux de la communication.

REMARQUE 2 : Il n’est pas nécessaire d’ajouter : un écran matériel, un clavier matériel ou du matériel pour permettre de se connecter à un écran ou à un clavier, filaire ou sans fil, si ce matériel n’est normalement pas fourni.

REMARQUE 3 : Aux fins de l’interopérabilité, la Recommandation ITU-T T.140 [i.36] est largement utilisée.

C.6.2.1.1 Communication par TTR

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC testées possèdent un mode qui permet une communication vocale bidirectionnelle.

2. Les TIC sont dans le mode qui permet la communication vocale bidirectionnelle

3. Un « terminal de TTR de référence » est disponible.

Procédure

1. Vérifier que les TIC permettent une communication par TTR bidirectionnelle avec les TIC de « référence ».

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de TTR de référence » est un terminal spécialement conçu pour tester les dispositifs de TTR de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de TTR de référence » compatible.

6.2.1.2 Voix et texte simultanés

Lorsque les TIC prévoient un moyen de communication vocale bidirectionnelle et permettent aux utilisateurs de communiquer par TTR, elles doivent permettre la communication vocale et textuelle simultanément par l’intermédiaire d’une connexion utilisateur unique.

REMARQUE 1 : Dans le cas d’une communication entre plusieurs participants, comme dans un système de conférence, il est permis (mais pas obligatoire ou nécessairement recommandé) que le TTR soit traité dans un champ d’affichage unique et que « la prise de parole à tour de rôle » soit nécessaire afin d’éviter toute confusion (de la même manière que la prise de parole à tour de rôle est requise pour ceux qui présentent ou parlent avec la parole).

REMARQUE 2 : Dans le cas d’une communication entre plusieurs participants, la pratique exemplaire consiste à lever la main pour que les utilisateurs de capacité vocale et les utilisateurs du TTR soient traités de la même manière, afin que les utilisateurs de capacité vocale et de TTR soient placés dans la même file d’attente.

REMARQUE 3 : Dans le cas d’un système de conférence entre plusieurs participants dont l’une des fonctions est le clavardage – le TTR (tout comme la capacité vocale) est généralement séparé de la fonction de clavardage pour que celle-ci n’interfère pas avec le TTR (c.-à-d. les personnes peuvent envoyer des messages dans la zone de clavardage pendant qu’une personne présente ou parle avec le TTR – de la même manière que les personnes s’envoient des messages en utilisant la fonction de clavardage pendant que des personnes utilisent la parole pour parler). Les utilisateurs de TTR utiliseraient alors le TTR pour présenter et la fonction de clavardage pour envoyer des messages pendant que les autres présentent (par la parole ou le TTR).

REMARQUE 4 : La possibilité de faire fonctionner la capacité vocale et le TTR simultanément (et séparément de la fonction de clavardage) peut également permettre à la zone de TTR de prendre en charge le sous-titrage lorsque quelqu’un parle (et elle n’est donc pas utilisée pour le TTR puisque ce n’est pas au tour de l’utilisateur du TTR de prendre la parole).

REMARQUE 5 : Lorsque le logiciel côté serveur tout comme le matériel et les logiciels locaux sont nécessaires pour fournir la communication vocale, mais qu’aucune partie ne peut prendre en charge la communication vocale sans l’autre et qu’elles sont vendues comme une seule unité pour la fonction de communication vocale, les composants des logiciels locaux et du serveur sont considérés comme un seul produit.

C.6.2.1.2 Voix et texte simultanés

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC permettent la communication vocale bidirectionnelle.

2. Les TIC prévoient un moyen de communication par TTR bidirectionnelle.

Procédure

1. Vérifier que les TIC permettent la communication vocale et le TTR simultanément par l’intermédiaire d’une connexion utilisateur unique.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

6.2.2 Affichage du TTR (texte en temps réel)
Clause de la norme EN 301 549Détermination de la conformité

6.2.2.1 Affichage visuellement reconnaissable

Lorsque les TIC sont dotées de capacités d’envoi et de réception de TTR, l’affichage du texte envoyé doit être visuellement différenciable et séparé de l’affichage du texte reçu.

REMARQUE : La possibilité de choisir entre l’affichage du texte d’envoi et de réception sur une ligne ou séparément et avec des options de sélection, permet aux utilisateurs d’afficher le TTR dans le format qui leur convient le mieux. Cela permettrait aux utilisateurs de texte en braille d’utiliser un seul champ et d’intervenir à tour de rôle ainsi que de faire apparaître le texte de manière séquentielle s’ils en ont besoin ou s’ils préfèrent.

C.6.2.2.1 Affichage visuellement reconnaissable

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC testées ont des capacités d’envoi et de réception de TTR.

2. Les TIC permettent les mécanismes de TTR.

3. Un appareil de TTR de référence compatible qui utilise des mécanismes pris en charge par le système des TIC est branché à l’autre extrémité du système sous épreuve

Procédure

1. Les TIC testées sont raccordées au système des TIC auquel le terminal de référence est raccordé.

2. Les différents éléments des TIC sont fonctionnels (le raccordement est actif et les terminaux sont en mode TTR correspondant) et les deux terminaux communiquent entre eux.

3. Une séquence de textes courts est envoyée par les TIC testées.

4. Une séquence de textes courts est envoyée par le terminal de référence.

5. Vérifier, sur les TIC testées, que l’affichage du texte envoyé est visuellement différenciable et séparé de l’affichage du texte reçu.

Résultat

Réussite: L’énoncé testable no 5 est vrai.

Échec: L’énoncé testable no 5 est faux.

REMARQUE: Un terminal de référence est un terminal doté de capacités d’envoi et de réception de TTR qui utilise des mécanismes de TTR pris en charge par le système des TIC. Ce terminal de référence est la responsabilité du laboratoire d’évaluation.

6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Lorsque les TIC présentent des capacités d’envoi et de réception de TTR, la direction de l’envoi et de la réception du texte doit pouvoir être déterminée par un programme informatique, à moins que la fonction de TTR soit une fonctionnalité restreinte.

REMARQUE: Le but de cette clause est de permettre aux lecteurs d’écran de différencier le texte entrant du texte sortant lorsque la fonction de TTR est utilisée.

C.6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC testées ont des capacités d’envoi et de réception de TTR.

2. La TTR a une fonction non restreinte.

3. Un « terminal de TTR de référence » est disponible.

Procédure

1. Les TIC testées sont connectés au « terminal de TTR de référence ».

2. Les différents éléments des TIC sont fonctionnels (le raccordement est actif et les terminaux sont en mode TTR correspondant) et les deux terminaux communiquent entre eux.

3. Une séquence de textes courts est envoyée par les TIC testées.

4. Une séquence de textes courts est envoyée par le « terminal de TTR de référence ».

5. Vérifier que la direction d’envoi et réception de texte peut être déterminée par un programme informatique.

Résultat

Réussite: L’énoncé testable no 5 est vrai.

Échec: L’énoncé testable no 5 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de TTR de référence » est un terminal spécialement conçu pour tester les dispositifs de TTR de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de TTR de référence » compatible.

6.2.2.3 Identification des interlocuteurs

Lorsque les TIC sont dotées de capacités de TTR et offrent l’identification des interlocuteurs par capacité vocale, elles doivent fournir l’identification des interlocuteurs par TTR.

REMARQUE : Cela est nécessaire pour permettre aux participants utilisant la fonction de capacité vocale comme ceux utilisant la fonction de TTR de savoir qui communique à un moment donné, que ce soit par TTR ou capacité vocale.

C.6.2.2.3 Identification des interlocuteurs

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC disposent de capacités de TTR.

2. Les TIC fournissent l’identification des interlocuteurs pour la capacité vocale.

3. Un « terminal de TTR de référence » est disponible.

Procédure

1. Les TIC testées sont connectées au « terminal de TTR de référence ».

2. Le TTR est envoyé à partir du « terminal de TTR de référence ».

3. Vérifier par observation si les TIC testées permettent l’identification des interlocuteurs pour le TTR entrant.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de TTR de référence » est un terminal spécialement conçu pour tester les dispositifs de TTR de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de TTR de référence » compatible.

6.2.2.4 Indicateur visuel de l’audio avec TTR

Lorsque les TIC offrent une communication vocale bidirectionnelle dotées de capacités de TTR, elles doivent fournir un indicateur visuel en temps réel de l’activité audio à l’écran.

REMARQUE 1 : L’indicateur visuel peut être une position de caractère simple sur l’écran qui clignote pour refléter l’activité audio ou la présentation des renseignements d’une autre manière étant à la fois visible par les utilisateurs voyants et transmis aux utilisateurs sourds-aveugles qui utilisent un écran braille.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

C.6.2.2.4 Indicateur visuel de l’audio avec TTR

Inspection

Conditions préalables

1. Les TIC offrent une communication vocale bidirectionnelle.

2. Les TIC sont dotées de capacités de TTR.

Procédure

1. La TIC testée est connectée à une autre TIC fournissant une communication vocale bidirectionnelle qui est compatible avec la voix de celle-ci.

2. Une personne parle dans l’autre TIC.

3. Vérifier par observation s’il y a un indicateur visuel en temps réel de l’activité audio.

Résultat

Réussite: L’énoncé testable no 3 est vrai.

Échec: L’énoncé testable no 3 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

REMARQUE : L’indicateur devrait clignoter en temps réel d’une manière qui reflète l’activité audio.

6.2.3 Interopérabilité

Lorsque les TIC dotées d’une fonction de TTR fonctionnent avec d’autres TIC dotées d’une fonction de TTR (comme l’exige la clause 6.2.1.1), elles doivent prendre en charge au moins un des quatre mécanismes d’interopérabilité de TTR décrits ci-dessous:

1. l’interopérabilité des TIC sur le réseau téléphonique public commuté (RTPC), avec d’autres TIC qui se raccordent directement au RTPC, comme le décrit la Recommandation V.18[i.23] de l’UIT-T ou l’une de ses annexes pour les signaux de téléphonie texte à l’interface du RTPC;

2. l’interopérabilité des TIC avec d’autres TIC à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initialisation de session (PIS) et du TTR conforme à RFC 4103 [i.13] de l’IETF. Pour l’interopérabilité des TIC avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, l’ensemble des protocoles spécifiés dans TS 126 114 [i.10], TS 122 173 [i.11] et TS 134 229 [i.12] de l’ETSI décrivent la façon dont RFC 4103 [i.13] de l’IETF s’appliquerait;

3. l’interopérabilité des TIC avec d’autres TIC utilisant des technologies autres que a ou b, ci-dessus, utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible pour les environnements dans lesquels elles fonctionneront. Cette spécification commune doit comprendre une méthode permettant d’indiquer la perte ou la corruption de caractères

4. l’interopérabilité des TIC avec d’autres TIC utilisant une norme pour TTR qui a été mise en place aux fins d’utilisation dans un des environnements susmentionnés, et qui est compatible avec toutes les autres TIC actives qui prennent en charge la capacité vocale et le TTR dans l’environnement en question.

C.6.2.3 Interopérabilité

a)

Type d’évaluation

Test

Conditions préalables

1. Vérifier l’interopérabilité des TIC avec le réseau téléphonique public commuté (RTPC), le terminal de référence V.18 étant raccordé au RTPC comme il est décrit dans la Recommandation V.18 [i.23] de UIT-T ou l’une de ses annexes pour les signaux de téléphonie à l’interface RTPC.

2. Vérifier que les TIC fonctionnent avec d’autres TIC à l’aide de la technologie VoIP dotée du protocole d’initiation de session (PIS) et du texte en temps réel conforme à RFC 4103[i.13]de l’IETF;

3. Vérifier que les TIC fonctionnent avec d’autres TIC dotées de TTR conformes aux protocoles du sous-système multimédia IP (IMS) conformément aux spécifications TS 126 114[i.10], TS 122 173[i.11] et TS 134 229[i.12] de l’ETSI;

Procédure

1. Vérifier l’interopérabilité des TIC avec le réseau téléphonique public commuté (RTPC), le terminal de référence V.18 étant raccordé au RTPC comme il est décrit dans la Recommandation V.18 [i.23] de UIT-T ou l’une de ses annexes pour les signaux de téléphonie à l’interface RTPC.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de référence V.18 » est un terminal spécialement conçu pour tester les dispositifs V.18 de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de référence » compatible.

b)

Type d’évaluation

Test

Conditions préalables

1. Les TCI fournissent un moyen de communication vocale bidirectionnelle à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initialisation de session (PIS).

2. Les TIC fournissent un moyen de communication bidirectionnelle par TTR.

3. Un « terminal de TTR de référence » est disponible.

Procédure

1. Vérifier l’interopérabilité des TIC avec le « terminal de TTR de référence » à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initialisation de session (PIS) et du TTR conforme à RFC 4103 [i.13] de l’IETF.

2. Si les TIC interopèrent avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, vérifier qu’elles respectent l’ensemble des protocoles spécifiés dans TS 126 114 [i.10], TS 122 173 [i.11] et TS 134 229 [i.12] de l’ETSI décrivant la façon dont RFC 4103 [i.13] de l’IETF s’applique.

Résultat

Réussite : L’énoncé testable no 1 est vrai et si les TIC interopèrent avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, l’énoncé testable no 2 est vrai.

Échec : L’énoncé testable no 1 est faux ou, si les TIC interopèrent avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, l’énoncé testable no 2 est faux.

Non applicable: La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de TTR de référence » est un terminal spécialement conçu pour tester les dispositifs de TTR de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de TTR de référence » compatible.

c)

Type d’évaluation

Test

Conditions préalables

1. Les TCI fournissent un moyen de communication vocale bidirectionnelle à l’aide de technologies autres que le RTPC ou Voix sur IP (VoIP) dotée du protocole d’initialisation de session (PIS).

2. Les TIC fournissent un moyen de communication bidirectionnelle par TTR.

3. Un « terminal de TTR de référence » est disponible pour ce mode de communication par TTR.

Procédure

1. Vérifier l’interopérabilité des TIC avec le « terminal de TTR de référence » utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible pour les environnements dans lesquels les TIC fonctionneront.

2. Vérifier que la spécification commune dans l’énoncé testable no 1 comprend une méthode permettant d’indiquer la perte ou la corruption de caractères.

Résultat

Réussite : Les énoncés testables nos 1 et 2 sont vrais.

Échec : Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de TTR de référence » est un terminal spécialement conçu pour tester les dispositifs de TTR de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de TTR de référence » compatible.

d)

Type d’évaluation

Test

Conditions préalables

1. Les TIC fournissent un moyen de communication vocale bidirectionnelle.

2. Les TIC fournissent un moyen de communication par TTR bidirectionnelle.

3. Un « terminal de TTR de référence » est disponible utilisant la nouvelle norme de TTR.

Procédure

1. Vérifier que les TIC testées interopèrent avec le « terminal de TTR de référence » pour la nouvelle norme de TTR qui a été mise en place aux fins d’utilisation.

2. Vérifier que la nouvelle norme de TTR est supporté par toutes les autres TIC actives qui supportent la capacité vocale et le TTR dans le même environnement.

Résultat

Réussite : Les énoncés testables nos 1 et 2 sont vrais.

Échec : Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

6.2.4 Réactivité du TTR (texte en temps réel)

Lorsque les TIC permettent la saisie de TTR, cette saisie doit être transmise au réseau des TIC ou à la plateforme sur laquelle fonctionne les TIC dans un délai de 500 ms à compter du moment où la plus petite unité de saisie de texte fiable est accessible aux TIC jusqu’à la fin de la transmission. Les retards attribuables à la performance de la plateforme ou du réseau ne doivent pas être inclus dans la limite de 500 ms.

REMARQUE 1 : Pour la saisie de caractère par caractère, la « plus petite unité de saisie de texte fiable » serait un caractère. Pour la prédiction des mots, ce serait un mot. Pour certains systèmes de reconnaissance vocale, le texte pourrait ne pas quitter le logiciel de reconnaissance tant qu’un mot entier (ou une expression entière) n’a pas été prononcé. Dans ce cas, la plus petite unité de saisie de texte fiable accessible aux TIC serait le mot (ou la phrase).

REMARQUE 2 : La limite de 500 ms permet de conserver en mémoire tampon les caractères avant leur transmission de sorte que la transmission caractère par caractère ne soit pas nécessaire à moins qu’ils soient générés plus lentement qu’un caractère par 500 ms.

REMARQUE 3 : Un délai de 300 ms, ou moins, produit une meilleure impression de fluidité pour l'utilisateur.

C.6.2.4 Réactivité du TTR (texte en temps réel)

Type d’évaluation

Inspection des mesures ou examen

Conditions préalables

1. Les TIC testées permettent la saisie de TTR.

2. Les TIC testée sont connectées à un dispositif ou un logiciel qui peut déterminer quand les caractères sont transmis.

Procédure

1. Saisir des caractères uniques dans le terminal testé.

2. Vérifier le temps à laquelle la saisie a eu lieu (p. ex. les caractères apparaissent sur l’écran).

3. Vérifier le délai entre le moment où la saisie est exécutée dans les TIC testées et le moment où le texte est transmis au réseau ou à la plate-forme des TIC.

Résultat

Réussite : Le résultat de l’énoncé testable no 3 est inférieur ou égal à 500 ms.

Échec : Le résultat de l’énoncé testable no 3 est supérieur à 500 ms.

Non applicable : La condition préalable 1 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Comme l’indiquent les remarques à la clause 6.2.4, la détermination du moment où la saisie a été exécutée peut différer selon le système TTR testé.

6.3 Identification de l’appelant

Lorsque les TIC sont dotées de la fonction d’identification de l’appelant ou d’une fonction de télécommunications similaire, la fonction d’identification de l’appelant ou de télécommunications similaire doit être offerte en mode textuel ainsi qu’être déterminable par un programme informatique, à moins que la fonction ne soit restreinte.

C.6.3 Identification de l’appelant

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC permettent la fonction d’identification de l’appelant ou de télécommunications similaire.

Procédure

1. Vérifier que les renseignements fournis par chaque fonction sont accessibles en mode textuel.

2. Vérifier que les renseignements fournis par chaque fonction sont déterminables par la programmation.

Résultat

Réussite : L’énoncé testable no 1 est vrai et l’énoncé testable no 2 est vrai ou la fonction est restreinte.

Échec : L’énoncé testable no 1 est faux ou l’énoncé testable no 2 est faux lorsque la fonction n’est pas restreinte.

Non applicable : La condition préalable 1 n’est pas remplie.

6.4 Autres solutions de services vocaux

Lorsque les TIC permettent la communication vocale en temps réel ainsi que la messagerie vocale, la réception automatique ou la réponse vocale interactive, elles doivent permettre à l’utilisateur d’accéder aux renseignements et d’exécuter les tâches sans recourir à l’ouïe ou à la parole.

REMARQUE 1: Les tâches qui impliquent à la fois l’utilisation de l'interface et la perception des informations exigeraient que celles-ci soient accessibles sans recourir à la parole ou à l’ouïe.

REMARQUE 2: Des solutions permettant de traiter les supports sons, texte et vidéo en temps réel pourraient répondre au besoin susmentionné.

C.6.4 Autres solutions de services vocaux

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC permettent la communication vocale en temps réel.

2. Les TIC permettent la messagerie vocale, la réception automatique ou la réponse vocale interactive.

Procédure

1. Vérifier que les TIC permettent à l’utilisateur d’accéder aux renseignements sans recourir à l’ouïe ou à la parole.

2. Vérifier que l’utilisateur peut exécuter les tâches que permet le système sans avoir à recourir à l’ouïe ou à la parole.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

6.5 Communication vidéo
Clause de la norme EN 301 549Détermination de la conformité

6.5.1 Généralités (information)

La clause 6.5 (Communication vidéo) décrit les exigences fonctionnelles supportant les utilisateurs qui communiquent en utilisant le langage des signes et la lecture labiale. Pour ces utilisateurs une résolution au moins QVGA (320 x 240), une vitesse de défilement d’au moins 20 images par seconde et un écart entre le son et la vidéo de 100 ms ou moins permettent une bonne utilisabilité.

L'augmentation de la résolution et de la vitesse de défilement des images améliore encore plus le langage des signes (en particulier l'orthographe digitale) et la lecture labiale, la vitesse de défilement des images étant plus importante que la résolution.

Les écarts temporels entre l’audio et la vidéo (asynchronicité) peuvent avoir un impact important sur la lecture labiale - une vidéo en retard sur l’audio a un effet négatif plus important.

La latence de bout en bout peut être un problème dans la communication vidéo (signes). Des valeurs d’écart inférieur à 400 ms avec une augmentation allant jusqu’à 100 ms sont préférables. L’écart global dépend de plusieurs facteurs, dont le délai de transmission du réseau et le traitement vidéo. Voilà pourquoi il est impossible d’établir une exigence testable des valeurs minimales d’écart global.

REMARQUE : La Recommandation UIT-T F.703 [i.37] définit et donne les exigences relatives à la conversation totale qui a trait à l’intégration de l’audio, au TTR et à la vidéo dans une connexion utilisateur unique.

C.6.5.1 Généralités (information)

La clause 6.5.1 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

6.5.2 Résolution

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles:

1. doivent prendre en charge au moins la résolution QVGA;

2. doivent de préférence prendre en charge au moins la résolution VGA.

C.6.5.2 Résolution

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC permettent la communication vocale bidirectionnelle.

2. Les TIC permettent la fonctionnalité vidéo en temps réel.

Procédure

1. Vérifier que la résolution de la communication vidéo est de résolution QVGA ou supérieure.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

6.5.3 Vitesse de défilement des images

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles:

1. doivent prendre en charge une vitesse de défilement d’au moins 20 images par seconde (IPS);

2. doivent de préférence prendre en charge une vitesse de défilement d’au moins 30 images par seconde (IPS) avec ou sans langage gestuel dans le flux vidéo.

C.6.5.3 Vitesse de défilement des images

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC permettent la communication vocale bidirectionnelle.

2. Les TIC permettent la fonctionnalité vidéo en temps réel.

Procédure

1. Vérifier que la vitesse de défilement des images de la communication vidéo est égale ou supérieure à 12 images par seconde.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

6.5.4 Synchronisation entre le son et la vidéo

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles doivent présenter à l’utilisateur un écart temporel maximal de 100 ms entre la parole et la vidéo.

REMARQUE : Des recherches récentes montrent que si l’audio mène la vidéo, l’intelligibilité en souffre beaucoup plus que dans le cas inverse.

C.6.5.4 Synchronisation entre le son et la vidéo

Type d’évaluation

Mesure

Conditions préalables

1. Les TIC permettent la communication vocale bidirectionnelle.

2. Les TIC permettent la fonctionnalité vidéo en temps réel.

Procédure

1. Vérifier que l’écart temporel entre la parole et la vidéo présentée à l’utilisateur est égal ou inférieur à 100 ms.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

6.5.5 Indicateur visuel de l’audio avec vidéo

Lorsque les TIC offrent une communication vocale bidirectionnelle et qu’elles comprennent une fonctionnalité de vidéo en temps réel, elles doivent fournir un indicateur visuel en temps réel de l’activité audio.

REMARQUE 1 : L’indicateur visuel peut être un simple point visuel, une LED ou d’autre type d’indicateur marche-arrêt, qui clignote pour refléter l’activité audio.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

C.6.5.5 Indicateur visuel de l’audio avec vidéo

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC prévoient une communication vocale bidirectionnelle.

2. Les TIC comprennent une fonctionnalité de vidéo en temps réel.

Procédure

1. La TIC testée est connectée à une autre TIC fournissant une communication vocale bidirectionnelle compatible avec la communication vocale de la TIC testée.

2. Une personne parle dans l’autre TIC.

3. Vérifier par observation s’il y a un indicateur visuel en temps réel de l’activité audio.

Résultat

Réussite : L’énoncé testable no 3 est vrai.

Échec : L’énoncé testable no 3 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

REMARQUE : L’indicateur devrait clignoter en temps réel d’une manière qui reflète l’activité audio.

6.5.6 Identification des interlocuteurs avec communication vidéo (langue des signes)

Lorsque les TIC offrent une fonction d’identification des interlocuteurs pour les utilisateurs de la capacité vocale, elles doivent fournir un moyen d’identification des interlocuteurs pour les utilisateurs de signes en temps réel et pour le langage des signes dès que celui-ci est utilisé.

REMARQUE 1 : L’identification des interlocuteurs peut se trouver au même emplacement que celui des utilisateurs de capacité vocale dans le cas des appels avec plusieurs interlocuteurs.

REMARQUE 2 : Ce mécanisme peut être déclenché manuellement par un utilisateur ou automatiquement lorsque cela est techniquement réalisable.

C.6.5.6 Identification des interlocuteurs avec communication vidéo (langue des signes)

Type d’évaluation

Mesure

Conditions préalables

1. Les TIC prévoient une communication vocale bidirectionnelle

2. Les TIC comprennent la vidéo en temps réel.

Procédure

1. La TIC testée est connectée à une TIC compatible qui supporte la vidéo et une personne communique en langue des signes.

2. Vérifier par l'observation si les TIC testées fournissent un moyen d’identification des interlocuteurs pour les utilisateurs de la langue des signes.

Résultat

Réussite : L’énoncé testable no 2 est vrai.

Échec : L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Lorsque les TIC offrent une fonction d’identification des interlocuteurs pour les utilisateurs de la capacité vocale, elles doivent fournir un moyen d’identification des interlocuteurs pour les utilisateurs de signes en temps réel et pour le langage des signes dès que celui-ci est utilisé.

REMARQUE 1 : L’identification des interlocuteurs peut se trouver au même emplacement que celui des utilisateurs de capacité vocale dans le cas des appels avec plusieurs interlocuteurs.

REMARQUE 2 : Ce mécanisme peut être déclenché manuellement par un utilisateur ou automatiquement lorsque cela est techniquement réalisable.

6.6 Autres solutions de services vidéo

Lorsque les TIC sont dotées de la communication vidéo en temps réel ainsi que d’un répondeur, d’un standard automatique ou de moyens de réponse interactifs, elles doivent permettre aux utilisateurs d’accéder aux renseignements et d’exécuter les tâches liées à ces moyens:

1. pour des renseignements audibles, sans recourir à l’ouïe;

2. pour les commandes vocales, sans recourir à la parole;

3. pour les renseignements visuels, sans recourir à la vision.

REMARQUE: Les solutions pouvant produire des sous-titres en temps réel ou traiter du texte en temps réel pourraient répondre au besoin susmentionné.

C.6.6 Autres solutions de services vidéo

La clause 6.6 n’a qu’une valeur informative et ne contient aucune exigence relative aux tests de conformité.

7 TIC avec capacités vidéo

7.1 Technologie de traitement des sous-titres
Clause de la norme EN 301 549Détermination de la conformité

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1: Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un dispositif braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

REMARQUE 3 : La clause 7.1.1 fait référence à la capacité du lecteur d’afficher des sous-titres. Les clauses 9.1.2.2, 10.1.2.2 et 11.1.2.2 font référence à la fourniture de sous-titres pour le contenu (la vidéo).

C.7.1.1 Lecture du sous-titrage

Type d’évaluation

Examen no 1

Conditions préalables

1. Les TIC affichent ou traitent la vidéo et la synchronisation sonore.

2. Les sous-titres sont fournis dans la vidéo.

Procédure

1. Vérifier qu’il y a un mécanisme d’affichage des sous-titres.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Type d’évaluation

Examen no 2

Conditions préalables

1. Les TIC affichent ou traitent la vidéo et la synchronisation sonore.

2. Les sous-titres sont fournis dans le contenu.

Procédure

1. Vérifier qu’il y a un mécanisme d’affichage des sous-titres.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

7.1.2 Synchronisation du sous-titrage

Lorsque les TIC affichent des sous-titres, le mécanisme d’affichage doit préserver la synchronisation entre le son et les sous-titres correspondants comme suit :

  • Sous-titres dans le matériel enregistré : dans les 100 ms de l’estampille temporelle du sous-titre.
  • Sous-titres en direct : dans les 100 ms suivant la disponibilité du sous-titre pour le lecteur.

C.7.1.2 Synchronisation du sous-titrage

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées d’un mécanisme d’affichage des sous-titres.

Procédure

1. Vérifier que le mécanisme d’affichage des sous-titres préserve la synchronisation entre le son et les sous-titres correspondants dans un dixième de seconde de l’estampille temporelle du sous-titre ou suivant la disponibilité du sous-titre pour le lecteur dans le cas d’un sous-titre en direct.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

7.1.3 Préservation du sous-titrage

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

D’autres aspects d’affichage du texte (p. ex. le positionnement à l’écran, la couleur et le style du texte ainsi que la police de caractères) peuvent être significatifs selon les conventions régionales. La modification de ces aspects pourrait en changer le sens et devrait être évitée dans la mesure du possible.

C.7.1.3 Préservation du sous-titrage

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC transmettent des conversions ou des enregistrements vidéo avec synchronisation sonore.

Procédure

1. Vérifier que les TIC préservent les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

7.1.4 Caractéristiques des sous-titres

Lorsque les TIC affichent des sous-titres, elles doivent permettre à l’utilisateur d’adapter les caractéristiques affichées des sous-titres à ses besoins individuels, sauf lorsque les sous-titres sont affichés sous forme de caractères non modifiables.

REMARQUE 1 : La définition de la couleur d’arrière-plan et d’avant-plan des sous-titres, du type de police, de l’opacité de la zone d’arrière-plan des sous-titres et du contour ou de la bordure des polices peut contribuer à répondre à cette exigence.

REMARQUE 2 : Les sous-titres qui sont des images bitmap sont des exemples de caractères non modifiables.

C.7.1.4 Caractéristiques des sous-titres

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC affichent les sous-titres.

2. Les sous-titres testés sont affichés sous forme de caractères modifiables.

Procédure

1. Vérifier que les TIC permettent à l’utilisateur d’adapter les caractéristiques affichées des sous-titres à ses besoins individuels.1. Check that the ICT provides a way for the user to adapt the displayed characteristics of captions to their individual requirements.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

7.1.5 Sous-titres vocaux

Lorsque les TIC affichent des vidéos avec son synchronisé, elles doivent fournir un mode de fonctionnement qui fournit une sortie vocale pour les sous-titres disponibles, sauf lorsque le contenu des sous-titres affichés n’est pas déterminable par programmation.

REMARQUE 1 : Il est préférable pour la plupart des utilisateurs de pouvoir gérer la gamme de sortie vocale pour les sous-titres vocaux indépendamment de la capacité vocale générale des TIC. Cela est possible lorsque le fichier audio avec sous-titres vocaux est reçu dans une piste audio distincte puis mixé sur l’appareil des utilisateurs.

REMARQUE 2 : Présenter la piste audio distincte avec des sous-titres vocaux en synchronisme avec les sous-titres affichés améliore la compréhension des sous-titres.

REMARQUE 3 : Fournir les sous-titres sous forme de flux de texte distincts facilite la conversion des textes respectifs en audio.

REMARQUE 4 : Les sous-titres qui sont des images bitmap sont des exemples pour lesquels le contenu de sous-titres affichés n’est pas déterminable par programmation.

C.7.1.5 Sous-titres vocaux

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC affichent des vidéos avec son synchronisé.

2. Le contenu des sous-titres testés est déterminable par programmation.

Procédure

1. Vérifier qu’il existe un mode de fonctionnement fournissant une sortie vocale pour les sous-titres disponibles.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

7.2 Technologie de description audio
Clause de la norme EN 301 549Détermination de la conformité

7.2.1 Lecture de la description audio

Lorsque les TIC affichent la vidéo avec synchronisation sonore, elles doivent fournir un mécanisme permettant de sélectionner et de lire la description audio accessible pour le canal sonore par défaut.

Lorsque les technologies vidéo ne fournissent pas de mécanismes explicites et distincts de description audio, une TIC est réputée répondre à ce besoin si elle permet à l’utilisateur de sélectionner et de lire plusieurs pistes sonores.

REMARQUE 1: Dans ce cas, le contenu vidéo peut présenter la description audio dans l’une des pistes sonores offertes.

REMARQUE 2: Les descriptions audio dans les médias numériques incluent parfois des renseignements permettant des descriptions plus longues que les temps morts entre les répliques. La fonction de description audio prolongée dans les lecteurs multimédias numériques est utile, en particulier pour les médias numériques consultés de manière individuelle.

C.7.2.1 Lecture de la description audio

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC affichent la vidéo et la synchronisation sonore.

Procédure

1. Vérifier qu’il existe un mécanisme explicite et distinct de description audio.

2. Vérifier qu’il existe un mécanisme permettant de sélectionner et de lire la description audio sur le canal sonore par défaut.

3. Vérifier que les TIC permettent à l’utilisateur de sélectionner et de lire plusieurs pistes sonores.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais, ou l’énoncé testable no 1 est faux et l’énoncé testable no 3 est vrai.

Échec: L’énoncé testable no 1 est vrai et l’énoncé testable no 2 est faux ou l’énoncé testable no 1 est faux et l’énoncé testable no 3 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

7.2.2 Synchronisation de la description audio

Lorsque les TIC sont dotées d’un mécanisme de lecture de description sonore, elles doivent préserver la synchronisation entre le contenu sonore ou visuel et la description sonore correspondante.

C.7.2.2 Synchronisation de la description audio

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées d’un mécanisme de lecture de la description audio.

Procédure

1. Vérifier que la synchronisation entre le contenu sonore ou visuel et la description audio correspondante sont préservées.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

C.7.2.3 Préservation de la description audio

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC transmettent des conversions ou des enregistrements vidéo avec synchronisation sonore.

Procédure

1. Vérifier que les TIC préservent la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1: Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2: Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3: Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio.

C.7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC affichent principalement du contenu vidéo et du contenu sonore associé

Procédure

1. Vérifier que les commandes de l’utilisateur pour activer le sous-titrage et les descriptions audio sont fournies à l’utilisateur au même niveau d’interaction que les principales commandes médias.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8 Matériel

8.1 Généralités
Clause de la norme EN 301 549Détermination de la conformité

8.1.1 Exigences génériques

Les exigences génériques de la clause 5 s’appliquent également aux TIC qui sont du matériel.

C.8.1.1 Exigences génériques

La clause 8.1.1 ne contient aucune exigence en matière de test.

8.1.2 Raccordements standard

Lorsque les TIC fournissent des points de raccordement de dispositif d’entrée ou de sortie à l’utilisateur, elle comprend au moins un raccordement d’entrée ou de sortie conforme à un format standard de l’industrie librement accessible, directement ou au moyen d’adaptateurs offerts sur le marché.

REMARQUE 1: L’exigence de raccordements standard vise à garantir la compatibilité avec les technologies d’assistance.

REMARQUE 2: Le terme raccordement s’applique à la fois aux raccordements matériels et sans fil.

REMARQUE 3: Les raccordements USB et Bluetooth sont des exemples de formats standard de l’industrie librement accessibles.

C.8.1.2 Raccordements standard

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC fournissent des points de raccordement d’entrée ou de sortie à l’utilisateur.

Procédure

1. Vérifier qu’un type de raccordement est conforme à un format standard de l’industrie librement accessible.

2. Vérifier qu’un type de raccordement est conforme à un format standard de l’industrie librement accessible au moyen d’adaptateurs offerts sur le marché.

Résultat

Réussite: Les énoncés testables nos 1 ou 2 sont vrais.

Échec: Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

REMARQUE: Les raccordements peuvent être matériels ou sans-fil.

8.1.3 Couleur

Lorsque les TIC sont dotées d’aspects matériels utilisant la couleur, la couleur n’est pas utilisée comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

C.8.1.3 Couleur

Type d’évaluation

Inspection

Conditions préalables

1. Les aspects matériels des TIC véhiculent de l’information visuelle à l’aide d’un code de couleur comme moyen d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

Procédure

1. Vérifier qu’une autre forme de codage visuel est fournie.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.2 Produits matériels avec sortie vocale
8.2.1 Gain de volume de la parole
Clause de la norme EN 301 549Détermination de la conformité

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE: Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965[i.2] sont réputés conformes à cette exigence.

C.8.2.1.1 Gamme de volume de la parole

Type d’évaluation

Inspection reposant sur les mesures

Conditions préalables

1. Le matériel de TIC est doté d’une sortie vocale.

Procédure

1. Vérifier que les TIC sont conformes à la norme ANSI/TIA-4965[i.2].

2. Mesurer le niveau (en dB) de la sortie vocale au réglage le plus bas.

3. Mesurer le niveau (en dB) de la sortie vocale au réglage le plus élevé.

4. Vérifier que la gamme entre 1 et 2 est supérieure ou égale à 18 dB.

Résultat

Réussite: Les énoncés testables nos 1 ou 4 sont vrais.

Échec: Les énoncés testables nos 1 et 4 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

C.8.2.1.2 Réglage incrémentiel du volume

Type d’évaluation

Inspection reposant sur les mesures

Conditions préalables

1. Le matériel de TIC est doté d’une sortie vocale.

2. Le réglage du volume est incrémentiel.

Procédure

1. Mesurer le niveau (en dB) de la sortie vocale au réglage le plus bas.

2. Vérifier si une étape intermédiaire fournit un niveau de 12 dB au-dessus du niveau de volume le plus bas mesuré à l’étape 1.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.2.2 Couplage magnétique
Clause de la norme EN 301 549Détermination de la conformité

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille et qui porte le symbole « T » spécifié dans la norme ETS 300 381[1] de l’ETSI, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1[2] de l’ETSI.

REMARQUE 1: Les TIC répondant aux exigences de la norme TIA-1083-A[i.24] sont réputées conformes aux exigences de la présente clause.

REMARQUE 2 : Le couplage magnétique est également appelé couplage inductif pour bobine en T.

C.8.2.2.1 Dispositifs de téléphonie fixe

Type d’évaluation

Inspection reposant sur les données de mesure

Conditions préalables

1. Le matériel de TIC est un dispositif de communication fixe avec sortie audio qui est normalement tenu à l’oreille.

Procédure

1. Vérifier que le matériel de TIC est conforme à la norme TIA-1083[i.24].

2. Les mesures effectuées conformément à la norme ES 200 381-1[2] de l’ETSI indiquent que les exigences définies dans cette norme sont satisfaites.

3. Les TIC portent le symbole « T » spécifié dans la norme ETS 300 381[1] de l’ETSI.

Résultat

Réussite: Les énoncés testables nos 1 ou 2 sont vrais et l’énoncé testable no 3 est vrai.

Échec: Les énoncés testables nos 1 et 2 sont faux ou l’énoncé testable no 3 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2[3] de l’ETSI.

REMARQUE: Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19[i.1] sont réputées conformes aux exigences de la présente clause.

C.8.2.2.2 Dispositifs de communication sans fil

Type d’évaluation

Inspection reposant sur les les données de mesure

Conditions préalables

1. Le matériel de TIC est un dispositif de communication sans fil qui est normalement tenu à l’oreille.

Procédure

1. Vérifier que le matériel de TIC est conforme à la norme ANSI/IEEE C63.19[i.1].

2. Vérifier que les TIC fournissent un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2[3] de l’ETSI.

Résultat

Réussite: Les énoncés testables nos 1 ou 2 sont vrais.

Échec: Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.3 TIC fixes
Clause de la norme EN 301 549Détermination de la conformité

8.3.0 Généralités (information)

Le présent document définit les dimensions pour accéder aux TIC fixes qui peuvent être placées dans un environnement bâti, mais ne définit pas les normes de l’environnement bâti en général.

Le champ d’application inclut les TIC fixes, dont les planchers et les espaces de circulation font « partie intégrante » (généralement les kiosques et les cabines), et où il existe des plages de portée externe qui sont importantes pour le fonctionnement des TIC fixes.

Les clauses 8.3.2 à 8.3.4 précisent les limites obligatoires pour la hauteur maximale et minimale des pièces manœuvrables et des écrans. Selon les dimensions indiquées à la figure 53 de la norme ISO 21542:2011 [i.34], il est recommandé que la portée possible en hauteur soit ramenée :

  • aux hauteurs minimale et maximale des pièces manœuvrables : 800 mm et 1100 mm respectivement, et.
  • aux hauteurs minimale et maximale des écrans : 1200 mm et 1400 mm respectivement.

C.8.3.0 Généralités (information)

La clause 8.3.0 n’a qu’une valeur informative et ne contient aucune exigence relative aux tests de conformité.

8.3.1 Portée avant ou latérale

Les TIC fixes doivent être conformes à la clause 8.3.2 ou à la clause 8.3.3.

REMARQUE 1 : Cela n'empêche pas de se conformer aux deux clauses.

REMARQUE 2 : Les dimensions indiquées dans les clauses 407.8.3 et 407.8.2 de l’article 508 du Rehabilitation Act, telles que publiées en janvier 2017 [i.25], sont identiques à celles indiquées dans les clauses 8.3.2 et 8.3.3 du présent document.

REMARQUE 3 : L’accès physique à une TIC fixe dépend des dimensions de la TIC et de l’environnement dans lequel elle est installée et exploitée. La clause 8.3 ne s’applique pas à l’accessibilité de l’environnement physique extérieur à la TIC.

C.8.3.1 Portée avant ou latérale

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes.

Procédure

1. Vérifier si les TIC sont conformes à la clause 8.3.2.2.

2. Vérifier si les TIC sont conformes à la clause 8.3.2.3.

Résultat

Réussite : L’énoncé testable no 1 ou no 2 est vrais

Échec : Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.3.2 Portée avant
Clause de la norme EN 301 549Détermination de la conformité

8.3.2.1 Hauteur maximum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins une pièce manœuvrable de chaque type ne doit pas être située à plus de 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès. Cela est illustré à la figure 2.

8.3.2.1 Hauteur maximum de la portée avant libre

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Aucune pièce des TIC fixes n’obstrue la portée avant.

Procédure

1. Vérifier qu’au moins une pièce manœuvrable de chaque type n’est pas située à plus de 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.2 Hauteur minimum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins une pièce manœuvrable de chaque type ne doit pas être située à moins de 380 mm (15 po) au-dessus du plancher de l’espace d’accès. Cela est illustré à la figure 2.

C.8.3.2.2 Hauteur minimum de la portée avant libre

Type d’évaluation

Inspection and mesures

Conditions préalables

1. Les TIC sont fixes.

2. Aucune pièce des TIC fixes n’obstrue la portée avant.

Procédure

1. Vérifier qu’au moins une pièce manœuvrable de chaque type n’est pas située à moins de 380 mm (15 po) au-dessus du plancher de l’espace d’accès

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.3 Portée avant obstruée
Clause de la norme EN 301 549Détermination de la conformité

8.3.2.3.1 Espace libre

Lorsqu’une obstruction faisant partie intégrante des TIC fixes empêche l’accès à tout type de pièce manœuvrable, les TIC doivent prévoir un espace libre qui s’étend sous l’élément obstruant sur une distance qui n’est pas inférieure à la profondeur d’atteinte requise au-dessus de l’obstruction.

REMARQUE : Le fait de prévoir un libre « accès à tout type de partie manœuvrable » garantit qu’un utilisateur pourra accéder à au moins une pièce manœuvrable de chaque type.

C.8.3.2.3.1 Espace libre

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes.

2. Une obstruction faisant partie intégrante des TIC empêche l’accès à tout type de pièce manœuvrable.

Procédure

1. Vérifier que les TIC prévoient un espace libre qui s’étend sous l’élément obstruant sur une distance qui n’est pas inférieure à la profondeur d’atteinte requise au-dessus de l’obstruction.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.3.2 Portée avant obstruée (<510 mm)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins une pièce manœuvrable de chaque type ne doit pas être supérieure à 1220 mm (48 po) au-dessus du point de contact au sol des TIC. Cela est illustré à la figure 3 (a).

C.8.3.2.3.2 Portée avant obstruée (<510 mm)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Une partie intégrante des TIC fixes forme une obstruction de moins de 510 mm (20 pouces) de profondeur.

Procédure

1. Vérifier que la portée avant à au moins une pièce manœuvrable de chaque type n’est pas supérieure à 1220 mm (48 pouces) au-dessus du contact avec le sol des TIC.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.3.3 Portée avant obstruée (<635 mm)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins une pièce manœuvrable de chaque type ne doit pas être supérieure à 1120 mm (44 po) au-dessus du point de contact au sol des TIC. Cela est illustré à la figure 3 (b).

8.3.2.3.3 Portée avant obstruée (<635 mm)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Une partie intégrante des TIC fixes forme une obstruction de pas moins de 510 mm (20 pouces) mais de moins de 635 mm (25 pouces) de profondeur.

Procédure

1. Vérifier que la portée avant à au moins une pièce manœuvrable de chaque type n’est pas supérieure à 1120 mm (44 pouces) au-dessus du contact avec le sol des TIC.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.4 Largeur libre pour les genoux et les pieds

Lorsque l’espace sous un obstacle faisant partie intégrante des TIC fait partie de l’espace d’accès, la largeur libre doit être d’au moins 760 mm (30 po).

C.8.3.2.4 Largeur libre pour les genoux et les pieds

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. L’espace sous un obstacle faisant partie intégrante des TIC fait partie d’un espace d’accès.

Procédure

1. Vérifier que la largeur de l’espace libre pour les genoux est supérieure à 760 mm (30 po).

2. Vérifier que la largeur de l’espace libre pour les pieds est supérieure à 760 mm (30 po).

Résultat

Réussite : Les énoncés testables nos 1 et 2 sont vrais.

Échec : Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.5 Espace libre pour les pieds

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle d’au moins 230 mm (9 po) au-dessus du plancher est considéré comme un espace libre pour les pieds et il devrait :

1. s’étendre sur au plus 635 mm (25 po) sous tout l’obstacle;

2. procurer un espace d’au moins 430 mm (17 po) de profondeur et 230 mm (9 po) au-dessus du plancher sous l’obstacle;

3. ne pas dépasser de plus de 150 mm (6 po) toute obstruction à 230 mm (9 po) au-dessus du plancher.

Cela est illustré à la figure 4.

C.8.3.2.5 Espace libre pour les pieds

a)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. L’espace sous un obstacle faisant partie intégrante des TIC fait partie d’un espace d’accès.

Procédure

1. Vérifier que la largeur de l’espace libre pour les genoux est supérieure à 760 mm (30 po).

2. Vérifier que la largeur de l'espace libre pour les pieds est supérieure à 760 mm (30 po).

Résultat

Réussite : Les énoncés testables nos 1 et 2 sont vrais.

Échec : Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

b)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Sous tout obstacle faisant partie intégrante des TIC, l’espace libre pour les pieds est d’au moins 230 mm (9 po) au-dessus du plancher.

Procédure

1. Vérifier que l’espace libre pour les orteils a au moins 430 mm (17 po) de profondeur et est à 230 mm (9 po) au-dessus du plancher sous l’obstacle.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie

c)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Sous tout obstacle faisant partie intégrante des TIC, l'espace libre pour les pieds est d’au moins 230 mm (9 po) au-dessus du plancher.

Procédure

1. Vérifier que l'espace libre pour les pieds ne dépasse pas de plus de 150 mm (6 po) tout obstacle à 230 mm (9 po) au-dessus du plancher.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

8.3.2.6 Espace libre pour les genoux

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (27 po) au-dessus du plancher est considéré comme un espace libre pour les genoux et il doit :

1. ne pas s’étendre sur plus de 635 mm (25 pouces) sous l’obstacle à une hauteur de 230 mm (9 po) au-dessus du plancher;

2. s’étendre sur au moins 280 mm (11 pouces) sous l’obstacle à une hauteur de 230 mm (9 po) au-dessus du plancher;

3. s'étendre sur au moins 205 mm (8 po) sous l’obstacle à une hauteur de 685 mm (27 po) au-dessus du plancher;

4. être autorisé à être réduit en profondeur à raison de 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.

Cela est illustré à la figure 5.

C.8.3.2.6 Espace libre pour les genoux

a)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Il y a un espace libre pour les genoux sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher.

Procédure

1. Vérifier qu’il y a un espace libre pour les genoux qui s’étend sur moins de 635 mm (25 po) sous l’obstacle à une hauteur de 230 mm (9 po) au-dessus du plancher.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

b)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Il y a un espace libre pour les genoux sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher.

Procédure

1. Vérifier qu’il y a un espace libre pour les genoux qui s’étend sur au moins 280 mm (11 po) sous l’obstacle à une hauteur de 230 mm (9 po) au-dessus du plancher.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

c)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Il y a un espace libre pour les genoux sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher.

Procédure

1. Vérifier qu’il y a un espace libre pour les genoux qui s’étend sur plus de 205 mm (9 po) sous l’obstacle à une hauteur de 685 mm (25 po) au-dessus du plancher.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

d)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Il y a un espace libre pour les genoux sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher.

Procédure

1. Vérifier que la réduction de la profondeur de l’espace libre pour les genoux n’est pas supérieure à 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

8.3.3 Portée latérale
Clause de la norme EN 301 549Détermination de la conformité

8.3.3.1 Hauteur maximum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant fait partie intégrante des TIC fixes qui est inférieur à 255 mm (10 po), la hauteur maximum de la portée latérale d’au moins une pièce manœuvrable de chaque type doit être inférieure ou égale à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

C.8.3.3.1 Hauteur maximum de la portée latérale libre

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. La portée latérale est libre ou obstruée par un élément faisant fait partie intégrante des TIC fixes qui est inférieur à 510 mm (20 po).

Procédure

1. Vérifier que la hauteur maximum de la portée latérale à au moins une pièce manœuvrable de chaque type n’est pas supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.3.2 Hauteur minimum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes qui est inférieur à 255 mm (10 po), la hauteur minimum de la portée latérale à au moins une pièce manœuvrable de chaque type doit être supérieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès. Cela est illustré à la figure 6.

C.8.3.3.2 Hauteur minimum de la portée latérale libre

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. La portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes qui est inférieur à 510 mm (20 po).

Procédure

1. Vérifier que la hauteur minimum de la portée latérale à au moins une pièce manœuvrable de chaque type est supérieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.3.3 Portée latérale obstruée
Clause de la norme EN 301 549Détermination de la conformité

8.3.3.3.1 Portée latérale obstruée (≤ 255 mm)

Lorsque les TIC fixes présentent une obstruction qui fait partie intégrante des TIC, la hauteur de l’obstruction doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est inférieure ou égale à 255 mm (10 po), la hauteur maximum de la portée latérale à au moins une pièce manœuvrable de chaque type ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès. Cela est illustré à la figure 7 (a).

C.8.3.3.3.1 Portée latérale obstruée (≤ 255 mm)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Une obstruction dont la profondeur est inférieure ou égale à 255 mm (10 po) fait partie intégrante des TIC.

Procédure

1. Vérifier que la hauteur maximum de la portée latérale à au moins une pièce manœuvrable de chaque type n’est pas supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.3.3.2 Portée latérale obstruée (≤ 610 mm)

Lorsque les TIC fixes présentent une obstruction qui fait partie intégrante des TIC, la hauteur de l’obstruction doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est supérieure à 255 mm (10 po) et inférieure à 610 mm (24 po), la hauteur maximum de la portée latérale à au moins un de chaque type de pièce manœuvrable ne doit pas être supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès. Cela est illustré à la figure 7 (b).

C.8.3.3.3.2 Portée latérale obstruée (≤ 610 mm)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Une obstruction dont la profondeur est supérieure à 255 mm (10 po) et inférieure à 610 mm (24 po) fait partie intégrante des TIC.

Procédure

1. Vérifier que la hauteur maximum de la portée latérale à au moins une pièce manœuvrable de chaque type n’est pas supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.4 Surface de plancher ou de sol dégagée
Clause de la norme EN 301 549Détermination de la conformité

8.3.4.1 Changement de niveau

Lorsque des TIC fixes comportent un plancher, tout changement de niveau du plancher qui y est intégré doit être aménagé d’une rampe présentant une pente d’au plus 1:48. Exceptions :

1. Si le changement de niveau du plancher est inférieur ou égal à 6,4 mm (1/4 po), le changement peut être vertical comme l’indique la figure 8.

2. Si le changement de niveau du plancher est inférieur ou égal à 13 mm (1/2 po), le changement peut présenter une pente d’au plus 1:2 comme il est illustré à la figure 9.

C.8.3.4.1 Changement de niveau

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Les TIC comportent un plancher.

3. Le plancher présente un changement de niveau..

Procédure

1. Si le changement de niveau est aménagé d’une rampe, vérifier qu’il présente une pente inférieure à 1:48.

2. Si le changement de niveau du plancher est vertical, vérifier qu’il est inférieur ou égal à 6,4 mm.

3. Si le changement de niveau du plancher est vertical ou présente une pente, vérifier que la pente n’est pas supérieure à 1:2.

Résultat

Réussite : L’énoncé testable no 1 ou no 2 ou no 3 est vrai.

Échec : Les énoncés testables nos 1, 2 et 3 sont faux.

Non applicable : La condition préalable 1 ou 2 ou 3 n’est pas remplie.

8.3.4.2 Surface de plancher ou de sol dégagée

Lorsque des TIC fixes intègrent un espace opérationnel, elles doivent prévoir une surface de plancher dégagée d’au moins 760 mm (30 po) par 1 220 mm (48 po) à partir de laquelle il est possible d’exploiter les TIC. Cela est illustré à la figure 10.

C.8.3.4.2 Surface de plancher ou de sol dégagée

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Elles intègrent un espace opérationnel.

Procédure

1. Vérifier qu’il y a une surface de plancher dégagée avec des dimensions rectangulaires minimales de 760 mm sur un bord et de 1220 mm sur l’autre bord.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.4.3 Approche
Clause de la norme EN 301 549Détermination de la conformité

8.3.4.3.1 Généralités

Lorsque des TIC fixes comportent un espace d’accès, au moins un côté complet de l’espace doit être dégagé.

C.8.3.4.3.1 Généralités

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes.

2. Elles comportent un espace d’accès.

Procédure

1. Vérifier qu’un côté complet de l’espace est dégagé.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.4.3.2 Approche avant

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 610 mm (24 po), et lorsqu’une approche avant est nécessaire, l’espace d’accès doit être d’au moins 915 mm (36 po) de largeur. Cela est illustré à la figure 11.

C.8.3.4.3.2 Approche avant

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes et comportent une alcôve

2. L’espace opérationnel se trouve dans l’alcôve.

3. La profondeur de l’alcôve est supérieure à 610 mm.

4. Une approche avant est nécessaire.

Procédure

1. Vérifier que la largeur de l’alcôve est supérieure à 915 mm.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2, 3 ou 4 n’est pas remplie.

8.3.4.3.3 Approche parallèle

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 380 mm (15 po), et lorsqu’une approche parallèle est nécessaire, l’espace d’accès doit être d’au moins 1525 mm (60 po) de largeur. Cela est illustré à la figure 12.

C.8.3.4.3.3 Approche parallèle

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes et comportent une alcôve

2. L’espace opérationnel se trouve dans l’alcôve.

3. La profondeur de l’alcôve est supérieure à 380 mm.

4. Une approche parallèle est possible.

Procédure

1. Vérifier que la largeur de l’espace d’accès est supérieure à 1525 mm.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2, 3 ou 4 n’est pas remplie.

8.3.5 Visibilité

Lorsque les TIC fixes fournissent un ou plusieurs écrans d’affichage, au moins un écran d'affichage de chaque type doit être positionné de telle sorte que les renseignements à l'écran soient lisibles depuis un point situé à 1015 mm (40 pouces) au-dessus du centre du plancher de l’espace opérationnel.

REMARQUE : Cette exigence vise à ce que l’information à l’écran soit lisible par des utilisateurs ayant une vision normale et des compétences linguistiques appropriées, lorsqu’ils sont assis dans un fauteuil roulant.

C.8.3.5 Visibilité

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes.

2. Un ou plusieurs écrans d’affichage sont fournis.

Procédure

1. Vérifier qu’au moins un écran d'affichage de chaque type est positionné de telle sorte que les renseignements à l'écran soient lisibles depuis un point situé à 1015 mm (40 pouces) au-dessus du centre du plancher de l’espace opérationnel.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.6 Instructions d’installation

Les instructions d’installation doivent être disponibles pour toutes les TIC fixes. Ces instructions doivent indiquer comment installer les TIC en tenant compte des exigences applicables en matière d’accessibilité de l’environnement bâti dans la mesure où elles s’appliquent à l’installation des TIC. Lorsque de telles exigences n’existent pas, les instructions devraient exiger que les dimensions des TIC installées soient conformes aux clauses 8.3.2 à 8.3.5 du présent document.

C.8.3.6 Instructions d’installation

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes.

Procédure

1. Vérifier que les instructions d’installation sont disponibles.

2. Vérifier que les instructions indiquent comment installer les TIC de façon à s’assurer que les dimensions des TIC installées sont conformes aux clauses 8.3.2 à 8.3.4.

3. Vérifier que les instructions indiquent que les installateurs doivent également tenir compte des exigences applicables en matière d’accessibilité de l’environnement bâti dans la mesure où elles s’appliquent à l’installation des TIC.

Résultat

Réussite : Les énoncés testables nos 1, 2 et 3 sont vrais.

Échec : Les énoncés testables nos 1, 2 et 3 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.4 Pièces mécaniquement manœuvrable
Clause de la norme EN 301 549Détermination de la conformité

8.4.1 Touches numériques

Lorsqu’elles sont fournies, les touches numériques formant un pavé rectangulaire doivent permettre de distinguer le numéro cinq de manière tactile des autres touches du pavé numérique.

REMARQUE: La Recommandation E.161[i.20] de l’UIT-T décrit la disposition du clavier du téléphone à 12 touches et fournit des détails supplémentaires sur la forme des marqueurs tactiles.

C.8.4.1 Touches numériques

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées de touches numériques physiques disposées sur un clavier téléphonique à 12 touches.

Procédure

1. Vérifier que le numéro cinq se distingue de manière tactile des autres touches du clavier.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.4.2 Fonctionnement des pièces mécaniques
Clause de la norme EN 301 549Détermination de la conformité

8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

C.8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner.

Procédure

1. Vérifier qu’il y a un autre moyen de fonctionnement qui n’exige pas de telles actions.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.4.2.2 Force de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite une force supérieure à 22,2 N pour fonctionner, un autre moyen de fonctionnement nécessitant une force inférieure à 22,2 N doit être prévu.

REMARQUE : ISO 21542:2011 [i.34] : Building Construction - Accessibility and Usability of the Built Environment recommande une valeur comprise entre 2,5 et 5 newtons.

C.8.4.2.2 Force de fonctionnement des pièces mécaniques

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées d’une commande qui nécessite une force supérieure à 22,2 N pour fonctionner.

Procédure

1. Vérifier qu’un autre moyen de fonctionnement nécessitant une force inférieure ou égale à 22,2 N est prévu.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.4.3 Clés, billets et cartes tarifaires

Lorsque les TIC fournissent des touches, des billets ou des cartes tarifaires, et que leur orientation est importante pour une utilisation ultérieure, elles doivent avoir une orientation qui est perceptible au toucher.

REMARQUE: La norme ETSI ETS 300 767[i.6] définit les indications tactiles appropriées pour les cartes plastiques.

C.8.4.3 Clés, billets et cartes tarifaires

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC fournissent des clés, des billets ou des cartes tarifaires, et leur orientation est importante pour une utilisation ultérieure.

Procédure

1. Vérifier que les clés, les billets ou les cartes tarifaires ont une orientation perceptible au toucher.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.5 Indication tactile du mode vocal

Lorsque les TIC sont conçues pour une utilisation partagée et qu’une sortie vocale est disponible, une indication tactile des moyens permettant de lancer le mode de fonctionnement vocal doit être fournie.

REMARQUE: L’indication tactile peut inclure des instructions en braille.

C.8.5 Indication tactile du mode vocal

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont conçues pour une utilisation partagée.

2. La sortie vocale est disponible.

Procédure

1. Vérifier qu’une indication tactile des moyens de lancement du mode vocal est fournie.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie..

9 Web

Clause de la norme EN 301 549Détermination de la conformité

9.0 Généralités (information)

Les exigences de la clause 9 s’appliquent aux pages Web (telles que définies à La clause 3.1), y compris:

  • La conformité avec le niveau AA des WCAG 2.0 équivaut à la conformité avec les clauses 9.1.1, 9.1.2, 9.1.3.1 à 9.1.3.3, 9.1.4.1 à 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.1.4, 9.2.1.1, 9.2.1.2, 9.2.2, 9.2.3, 9.2.4, 9.3, 9.4.1.1, 9.4.1.2 et avec les exigences de conformité de la clause 9.5 du présent document.
  • La conformité au niveau AA des WCAG 2.1 équivaut à la conformité à toutes les clauses 9.1 à 9.4 et aux exigences de conformité de La clause 9.5 du présent document.
  • Les exigences relatives aux autres documents et logiciels sont énoncées aux articles 10 et 11, respectivement.

REMARQUE 1: Les sites Web sont évalués en tant que pages Web individuelles. Les applications Web, les applications Web mobiles, etc., sont couvertes par la définition de page Web qui est très large et qui englobe tous les types de contenu Web.

Les exigences en matière de contenu Web énoncées aux articles 9.1 à 9.4 établissent tous les critères de succès des niveaux A et AA à partir des Règles pour l’accessibilité des contenus Web 2.0 de W3C (WCAG 2.1) [5]:

  • Les pages Web qui sont conformes aux niveaux A et AA des WCAG 2.0 sont également conformes aux clauses 9.1.1.1 à 9.1.3.3, 9.1.4.1 à 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.2.1 à 9.2.4.7, 9.3.1.1 à 9.4.1.2 ainsi qu’aux exigences de conformité de la clause 9.5.
  • Les pages Web qui sont conformes au niveau AA des WCAG 2.1 sont conformes à toutes les clauses 9.1 à 9.4 ainsi qu’aux exigences de conformité de La clause 9.5.
  • Les pages Web qui sont conformes aux clauses 9.1.1.1 à 9.1.3.3, 9.1.4.1 à 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.2.1 à 9.2.4.7, 9.3.1.1 à 9.4.1.2 ainsi qu’aux exigences de conformité de la clause 9.5, sont également conformes au niveau AA des WCAG 2.0.
  • Les pages Web qui sont conformes à toutes les clauses 9.1 à 9.4 et aux exigences de conformité de la clause 9.5, sont conformes au Niveau AA des WCAG 2.1.

REMARQUE 2: WCAG 2.0 est identique à la norme ISO/CEI 40500 (2012): « Technologies de l’information – Règles pour l’accessibilité des contenus Web 2.0 (WCAG 2.0) de World Wide Web Consortium (W3C)» [4].

Les exigences des clauses 9.1 à 9.4 sont rédigées selon le concept de la satisfaction des critères de succès (défini à la clause 3.1).

Une page Web satisfait à un critère de succès des WCAG lorsque ce critère ne se révèle pas « faux » lors de l’évaluation de la page Web. Cela implique que si le critère de succès place des conditions sur une caractéristique spécifique et que cette caractéristique spécifique n’apparaît pas dans la page Web, alors cette page satisfait au critère de succès.

REMARQUE 3: Par exemple, une page Web qui ne contient pas de contenu audio pré-enregistré dans un support synchronisé satisfera automatiquement au critère de succès 1.2.2 des WCAG (Sous-titres [pré-enregistrés]) et, par conséquent, sera également conforme à la clause 9.1.2.2.

En plus des critères de réussite du Niveau AA, les lignes directrices pour l’accessibilité aux contenus Web comprennent également des critères de succès pour le niveau AAA.

REMARQUE 4: Le corps du présent document n’inclut pas les critères de succès du niveau AAA, et ce, à la fois pour éviter toute confusion avec les exigences fondées sur le niveau A et le niveau AA et pour assurer l’harmonisation avec les autres normes d’approvisionnement.

Les auteurs de sites Web et les spécialistes de l’accessibilité en matière d’approvisionnement sont encouragés à améliorer l’accessibilité au-delà des exigences du présent document. Par conséquent, ils doivent examiner si l’un ou l’autre des critères de succès du niveau AAA des WCAG offre des suggestions qui peuvent être applicables et pertinentes à leur projet, de même que potentiellement bénéfiques pour certains utilisateurs.

REMARQUE 5: Le W3C énonce ce qui suit: « il n’est pas recommandé d’exiger la conformité au niveau AAA puisqu’il est impossible de respecter tous les critères de succès liés à ce niveau pour certains éléments du contenu ».

C.9.0 Généralités (information)

La clause 9.0 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

9.1 Perceptible
9.1.1 Équivalents textuels
Clause de la norme EN 301 549Détermination de la conformité

9.1.1.1 Contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

C.9.1.1.1 Contenu non textuel

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez que la page Web n’échoue pas au critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

9.1.2 Médias temporels
Clause de la norme EN 301 549Détermination de la conformité

9.1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés)

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 1.2.1 Contenu audio ou vidéo seulement (préenregistré) des WCAG 2.1.

C.9.1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés) des WCAG 2.1.

Résultat.

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.1 Contenu seulement audio et seulement vidéo (pré-enregistrés) des WCAG 2.1.

9.1.2.2 Sous-titres (pré-enregistrés)

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.2.2 Sous-titres (pré-enregistrés).

Critères de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1

Comprendre le critère Sous-titres (pré-enregistrés)(en anglais seulement)

Comment satisfaire au critère Sous-titres (pré-enregistrés)(en anglais seulement)

(Niveau A)

Fournir des sous-titres pour tout contenu audio pré-enregistré dans un média synchronisé, excepté lorsque le média est un média de remplacement pour un texte et qu'il est clairement identifié comme tel.

C.9.1.2.2 Sous-titres (pré-enregistrés)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez que la page Web n’échoue pas au critère de succès 1.2.2 Sous-titres (pré-enregistrées) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

9.1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré)

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1

C.9.1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

9.1.2.4 Sous-titres (en direct)

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1 .

C.9.1.2.4 Sous-titres (en direct)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez que la page Web n’échoue pas au critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

9.1.2.5 Audio-description (pré-enregistrée)

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès 1.2.5 Audio-description (pré-enregistré) des WCAG 2.1. 

C.9.1.2.5 Audio-description (pré-enregistrée)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

1. Vérifier que la page Web n’échoue pas au critère de succès 1.2.5 Audio-description (pré-enregistrée) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.5 Audio-description (pré-enregistrée) des WCAG 2.1.

9.1.3 Adaptable
Clause de la norme EN 301 549Détermination de la conformité

9.1.3.1 Information et relations

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

C.9.1.3.1 Information et relations

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.1 Information et relations des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.1 Information et relations des WCAG 2.1.

9.1.3.2 Ordre séquentiel logique

Dans le cas où la TIC est une page Web, elle satisfait au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

C.9.1.3.2 Ordre séquentiel logique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

9.1.3.3 Caractéristiques sensorielles

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.3 Caractéristiques sensorielles de WCAG 2.1.

C.9.1.3.3 Caractéristiques sensorielles

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

9.1.3.4 Orientation

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.4 Orientation des WCAG 2.1.

C.9.1.3.4 Orientation

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez si la page Web n’échoue pas au critère de succès 1.3.4 Orientation des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.4 Orientation des WCAG 2.1.

9.1.3.5 Identifier la finalité de la saisie

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 1.3.5 Finalité d’un champ de saisie des WCAG 2.1.

C.9.1.3.5 Identifier la finalité de la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

9.1.4 Distinguable
Clause de la norme EN 301 549Détermination de la conformité

9.1.4.1 Utilisation de la couleur

Dans le cas où la TIC est une page Web, elle remplit le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

C.9.1.4.1 Utilisation de la couleur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

9.1.4.2 Contrôle du son

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.2 Contrôle du son des WCAG 2.1.

C.9.1.4.2 Contrôle du son

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.2 Contrôle du son des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.2 Contrôle du son des WCAG 2.1.

9.1.4.3 Contraste (minimum)

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.3 Contraste (minimum).

C.9.1.4.3 Contraste (minimum)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

9.1.4.4 Redimensionnement du texte

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.4 Redimensionnement du texte (en direct) des WCAG 2.1.

C.9.1.4.4 Redimensionnement du texte

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

9.1.4.5 Texte sous forme d’image

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

C.9.1.4.5 Texte sous forme d’image

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

9.1.4.10 Redistribution

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.10 Redistribution des WCAG 2.1.

C.9.1.4.10 Redistribution

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez si la page Web n’échoue pas au critère de succès 1.4.10 Redistribution des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.10 Redistribution des WCAG 2.1.

9.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

C.9.1.4.11 Contraste du contenu non textuel

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.11 Contraste des éléments non textuels des WCAG 2.1.

9.1.4.12 Espacement du texte

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

C.9.1.4.12 Espacement du texte

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

9.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est une page Web, elle remplit le Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

C.9.1.4.13 Contenu au survol ou au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que le document n’échoue pas au Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

9.2 Utilisable
9.2.1 Accessibilité au clavier
Clause de la norme EN 301 549Détermination de la conformité

9.2.1.1 Clavier

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 2.1.1 Clavier de WCAG 2.1.

C.9.2.1.1 Clavier

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez si la page Web n’échoue pas au critère de succès 2.1.1 Clavier des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.1 Clavier des WCAG 2.1.

9.2.1.2 Pas de piège au clavier

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 2.1.2 Pas de piège au clavier de WCAG 2.1.

C.9.2.1.2 Pas de piège au clavier

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez que la page Web n’échoue pas le critère de succès 2.1.2 Pas de piège à clavier des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.2 Pas de piège à clavier des WCAG 2.1.

9.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier des caractères des WCAG 2.1.

C.9.2.1.4 Raccourcis clavier utilisant des caractères

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.1.4 Raccourcis clavier des caractères de WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.4 Raccourcis clavier utilisant des caractères de WCAG 2.1.

9.2.2 Délai suffisant
Clause de la norme EN 301 549Détermination de la conformité

9.2.2.1 Réglage du délai

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.2.1 Réglage du délai de WCAG 2.1.

C.9.2.2.1 Réglage du délai

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez si la page Web n’échoue pas au critère de succès 2.2.1 Réglage du délai des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.2.1 Réglage du délai des WCAG 2.1.

9.2.2.2 Mettre en pause, arrêter, masquer

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.2.2 Mettre en pause, arrêter, masquer de WCAG 2.1.

C.9.2.2.2 Mettre en pause, arrêter, masquer

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.2.2 Mettre en pause, arrêter, masquerdes WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.2.2 Mettre en pause, arrêter, masquer des WCAG 2.1.

9.2.3 Crises et réactions physiques
Clause de la norme EN 301 549Détermination de la conformité

9.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.3.1 Pas plus de trois flashs ou sous le seuil critique.

C.9.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.3.1 Pas plus de trois flashs ou sous le seuil critique des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.3.1 Pas plus de trois flashs ou sous le seuil critique des WCAG 2.1.

9.2.4 Navigable
Clause de la norme EN 301 549Détermination de la conformité

9.2.4.1 Contourner des blocs

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.1 Contourner des blocs.

C.9.2.4.1 Contourner des blocs

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.1 Contourner des blocs des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.1 Contourner des blocs des WCAG 2.1.

9.2.4.2 Titre de page

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.2 Titre de page.

C.9.2.4.2 Titre de page

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.2 Titre de page des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.2 Titre de page des WCAG 2.1.

9.2.4.3 Parcours du focus

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.3 Parcours de la cible de saisie.

C.9.2.4.3 Parcours du focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.3 Parcours de la cible de saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.3 Parcours du focus des WCAG 2.1.

9.2.4.4 Fonction du lien (selon le contexte)

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.4 Fonction du lien (selon le contexte).

C.9.2.4.4 Fonction du lien (selon le contexte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.4 Objectif du lien (selon le contexte) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

9.2.4.5 Accès multiples

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.5 Accès multiples.

C.9.2.4.5 Accès multiples

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.5 Accès multiples des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.5 Accès multiples des WCAG 2.1.

9.2.4.6 En-têtes et étiquettes

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.6 En-têtes et étiquettes.

C.9.2.4.6 En-têtes et étiquettes

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

9.2.4.7 Visibilité Au focus

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.7 Visibilité de la cible de saisie.

C.9.2.4.7 Visibilité Au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au Critère de succès 2.4.7 Visibilité Au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.7 Visibilité du focus des WCAG 2.1..

9.2.5 Modalités d’entrée
Clause de la norme EN 301 549Détermination de la conformité

9.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.1 Mouvements du pointeur.

C.9.2.5.1 Gestes pour le contrôle du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.5.1 Mouvements du pointeur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1.

9.2.5.2 Annulation de l’action du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.2 Annulation de l’action du pointeur.

C.9.2.5.2 Annulation de l’action du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.5.2 Annulation du pointeur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1.

9.2.5.3 Étiquette dans le nom

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom de WCAG 2.1.

C.9.2.5.3 Étiquette dans le nom

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

9.2.5.4 Activation par le mouvement

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement.

C.9.2.5.4 Activation par le mouvement

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

9.3 Compréhensible
9.3.1 Lisible
Clause de la norme EN 301 549Détermination de la conformité

9.3.1.1 Langue de la page

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.1.1 Langue de la page.

C.9.3.1.1 Langue de la page

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.1.1 Langue de la page des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.1.1 Langue de la page des WCAG 2.1.

9.3.1.2 Langue d’un passage

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.1.2 Langue d’un passage.

C.9.3.1.2 Langue d’un passage

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.1.2 Langue d’un passage des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.1.2 Langue d’un passage des WCAG 2.1.

9.3.2 Prévisible
Clause de la norme EN 301 549Détermination de la conformité

9.3.2.1 Au focus

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.2.1 Au focus.

C.9.3.2.1 Au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.2.1 Au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.1 Au focus des WCAG 2.1.

9.3.2.2 À la saisie

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès À la saisie.

C.9.3.2.2 À la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.2.2 À la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.2 À la saisie des WCAG 2.1

9.3.2.3 Navigation cohérente

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.2.3 Navigation cohérente.

C.9.3.2.3 Navigation cohérente

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.2.3 Navigation cohérente des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.3 Navigation cohérente des WCAG 2.1.

9.3.2.4 Identification cohérente

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.2.4 Identification cohérente.

C.9.3.2.4 Identification cohérente

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.2.4 Identification cohérente des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.4 Identification cohérente des WCAG 2.1.

9.3.3 Assistance à la saisie
Clause de la norme EN 301 549Détermination de la conformité

9.3.3.1 Identification des erreurs

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.3.1 Identification des erreurs.

C.9.3.3.1 Identification des erreurs

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

9.3.3.2 Étiquettes ou instructions

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.3.2 Étiquettes ou instructions.

C.9.3.3.2 Étiquettes ou instructions

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

9.3.3.3 Suggestion après une erreur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.3.3 Suggestion après une erreur.

C.9.3.3.3 Suggestion après une erreur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

9.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.3.4 Prévention des erreurs (juridiques, financières, de données).

C.9.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.3.4 Identification des erreurs des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.4 Prévention des erreurs (juridiques, financières, de données) des WCAG 2.1.

9.4 Robuste
9.4.1 Compatible
Clause de la norme EN 301 549Détermination de la conformité

9.4.1.1 Analyse syntaxique

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.1 Analyse syntaxique.

C.9.4.1.1 Analyse syntaxique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 4.1.1 Analyse syntaxique des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 4.1.1 Analyse syntaxique des WCAG 2.1.

9.4.1.2 Nom, rôle et valeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.2 Nom, rôle et valeur.

C.9.4.1.2 Nom, rôle et valeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 4.1.2 Nom, rôle et valeur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 4.1.2 Nom, rôle et valeur des WCAG 2.1.

9.4.1.3 Messages d’état

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

C.9.4.1.3 Messages d’état

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 4.1.3 Messages d’état des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 4.1.3 Messages d’état des WCAG 2.1.

9.5 Critères de succès de niveau AAA des WCAG 2.1

Outre les critères de succès de niveau AA, les Règles pour l’accessibilité des contenus Web comprennent les critères de succès pour le niveau AAA, aux clauses 9.1 à 9.4. Ces critères sont énumérés dans le tableau 9.1. Les auteurs de sites Web et les spécialistes de l’approvisionnement en matière d’accessibilité sont invités à tenir compte des critères de succès de niveau AAA des WCAG 2.1 qui, lorsqu’il est possible de les appliquer, peuvent fournir un accès au-delà de ce qui est requis dans le présent document.

REMARQUE : Le W3C stipule qu’« il n’est pas recommandé de se fixer le niveau AAA comme objectif à l’échelle de sites entiers car il n’est pas possible de satisfaire à tous les critères de succès du niveau AAA pour certains contenus ». Consulter le Tableau 9.1 : Critères de succès de niveau AAA des WCAG 2.1 dans l'Annexe - Tableaux et figures (de la norme EN 301 549).

9.5 Critères de succès de niveau AAA des WCAG 2.1

La clause 9.5 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

9.6 Exigences de conformité aux WCAG

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire aux cinq exigences de conformité aux WCAG 2.1 de niveau AA énumérées ci-dessous [5].

1. Niveau de conformité

2. Pages complètes

3. Processus complets

4. L’usage des technologies selon des méthodes exclusivement compatibles avec l’accessibilité

5. Non-interférence

REMARQUE 1: Une page Web qui satisfait aux exigences 9.1 à 9.4, ou lorsqu’une version de remplacement conforme au niveau AA (tel que défini dans la WCAG 2.1[5]) est fournie, satisfera à l’exigence de conformité 1.

REMARQUE 2: Selon le W3C: « Les WCAG 2.1 élargissent les Directives pour l’accessibilité des contenus Web 2.0[4], qui ont été publiées comme Recommandation du W3C en décembre 2008. Le contenu qui est conforme aux WCAG 2.1 est également conforme aux WCAG 2.0, et, par conséquent, aux politiques qui font référence aux WCAG 2.0. » [4]

REMARQUE 3: L’exigence de conformité 5 stipule que tout le contenu de la page, y compris le contenu dont on ne dépend pas autrement pour atteindre la conformité, respecte les clauses 9.1.4.2, 9.2.1.2, 9.2.2.2 et 9.2.3.1.

Critères de succès de niveau AAA des WCAG 2.1 2.1 de niveau AA[5]

C.9.6 Exigences de conformité aux WCAG

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web satisfait à l’exigence de conformité aux WCAG 2.1 [5] « 1: Niveau de conformité » au niveau AA.

2. Vérifier que la page Web satisfait à l’exigence de conformité aux WCAG 2.1 [5] « 2: Pages complètes ».

3. Vérifier que la page Web satisfait à l’exigence de conformité aux WCAG 2.1 [5] « 3: Processus complets ».

4. Vérifier que la page Web satisfait à l’exigence de conformité aux WCAG 2.1 [5] « 4: L’usage des technologies selon des méthodes exclusivement compatibles avec l’accessibilité ».

5. Vérifier que la page Web satisfait à l’exigence de conformité aux WCAG 2.1 [5] « 5: Non-interférence ».

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: N’importe quel énoncé testable est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10 Contenu non Web

Clause de la norme EN 301 549Détermination de la conformité

10.0 Généralités (information)

Les exigences énoncées à la clause 10 s’appliquent aux documents:

  • qui ne sont pas des pages Web;
  • qui ne sont pas intégrés dans des pages Web;
  • qui sont intégrés dans des pages Web, qui ne sont pas utilisés dans le rendu et qui ne sont pas destinés à être rendus avec la page Web dans laquelle ils sont intégrés.

L’article 9 prévoit les exigences de conformité des documents qui se trouvent dans des pages Web ou qui sont intégrés dans des pages Web, et qui sont utilisés dans le rendu ou qui sont destinés à être rendus avec la page Web dans laquelle ils sont intégrés.

REMARQUE 1: Voici quelques exemples de documents: lettres, feuilles de calcul, messages électroniques, livres, images, présentations et films qui sont associés à un agent utilisateur comme un lecteur de documents, un éditeur ou un lecteur multimédia.

REMARQUE 2: Un document peut être composé de plusieurs fichiers, comme du contenu vidéo, des sous-titres, etc. La plupart du temps, cela n’est pas apparent pour l’utilisateur final qui parcourt le document/contenu.

REMARQUE 3: Les documents nécessitent un agent utilisateur pour que le contenu soit présenté à l’utilisateur. Les exigences relatives aux agents utilisateurs se trouvent à La clause 11.

REMARQUE 4: Les exigences relatives au contenu qui fait partie du logiciel se trouvent à la clause 11.

REMARQUE 5: Les critères de succès énoncés à la clause 10 visent à s’harmoniser avec la Note du groupe de travail [i.26] produite par le WCAG2ICT Task Force du W3C.

REMARQUE 6 : Des clauses « nul » ont été insérées afin de maintenir l’harmonisation avec la numérotation des clauses 9, 10 et 11.

REMARQUE 7 : Les exigences de la clause 10 s’appliquent également aux documents qui sont protégés par des mécanismes tels que les signatures numériques, le chiffrement, la protection par mot de passe et les filigranes lorsqu’ils sont présentés à l’utilisateur.

REMARQUE 8 : La pratique exemplaire consiste à utiliser WebSchemas/Accessibility 2.0 [i.38] pour fournir des métadonnées sur l’accessibilité du document au sein ou séparément du document.

C.10.0 Généralités (information)

La clause 10.0 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

10.1 Perceptible
10.1.1 Équivalents textuels
Clause de la norme EN 301 549Détermination de la conformité

10.1.1.1 Contenu non textuel

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.1.1 Contenu non textuel.

REMARQUE: Les CAPTCHAS n’apparaissent pas actuellement hors du Web. Cependant, s’ils apparaissent, ce conseil est pertinent.

C.10.1.1.1 Contenu non textuel

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

10.1.2 Médias temporels
Clause de la norme EN 301 549Détermination de la conformité

10.1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés)

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés).

REMARQUE: Le média de remplacement peut être fourni directement dans le document – ou fourni dans une version de remplacement qui satisfait au critère de succès.

C.10.1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés) des WCAG 2.1.

10.1.2.2 Sous-titres (pré-enregistrés)

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.2.2 Sous-titres (pré-enregistrés).

REMARQUE: La définition de « sous-titres » donnée par les WCAG 2.1 précise que « dans certains pays, les sous-titres sont appelés captions et subtitles ». On les appelle aussi parfois « sous-titres pour malentendants ». Selon la définition des WCAG 2.1, pour satisfaire à ce critère de succès, qu’il s’agisse de captions ou de subtitles, les sous-titres doivent fournir un « visuel synchronisé ou équivalent textuel pour l’information audio avec ou sans paroles nécessaires à la compréhension du contenu d’un média », lorsque l’information sans paroles comprend des « effets sonores, de la musique, des rires, l’identification et le positionnement des interlocuteurs ».

C.10.1.2.2 Sous-titres (pré-enregistrés)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non-Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

10.1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré)

Lorsque la technologie n’est pas un document Web, celle­ci doit satisfaire au critère de succès 1.2.3 audio-description ou version de remplacement pour un média temporel (pré-enregistré).

REMARQUE 1: La définition des WCAG 2.1 précise qu « audio-description » est également nommée « vidéo-description » et « narration descriptive ».

REMARQUE 2: Des pistes audio secondaires ou de remplacement sont couramment utilisées à cette fin.

C.10.1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.3 audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

10.1.2.4 Sous-titres (en direct)

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.2.4 Sous-titres (en direct).

REMARQUE: La définition de « sous-titres » donnée par les WCAG 2.1 précise que « dans certains pays, les sous-titres sont appelés captions et subtitles ». On les appelle aussi parfois « sous-titres pour malentendants ». Selon la définition des WCAG 2.1, pour satisfaire à ce critère de succès, qu’il s’agisse de captions ou de subtitles, les sous-titres doivent fournir un « visuel synchronisé ou équivalent textuel pour l’information audio avec ou sans paroles nécessaires à la compréhension du contenu d’un média », lorsque l’information sans paroles comprend des « effets sonores, de la musique, des rires, l’identification et le positionnement des interlocuteurs ».

C.10.1.2.4 Sous-titres (en direct)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1).

10.1.2.5 Audio-description (pré-enregistrée)

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.2.5 audio-description (pré-enregistrée).

REMARQUE 1: La définition des WCAG 2.1 précise qu’une «audio-description» est également nommée « vidéo-description » et « narration descriptive ».

REMARQUE 2: Des pistes audio secondaires ou de remplacement sont couramment utilisées à cette fin.

C.10.1.2.5 Audio-description (pré-enregistrée)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.5 audio-description (pré-enregistrée)des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.5 Audio-description (pré-enregistrée) des WCAG 2.1.

10.1.3 Adaptable
Clause de la norme EN 301 549Détermination de la conformité

10.1.3.1 Information et relations

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.3.1 Information et relations.

REMARQUE : Lorsque les documents contiennent des types de structure non standard (rôles), la pratique exemplaire consiste à les faire correspondre à un type de structure standard comme solution de secours pour le lecteur.

C.10.1.3.1 Information et relations

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.3.1 Information et relations des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.1 Information et relations des WCAG 2.1.

10.1.3.2 Ordre séquentiel logique

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

C.10.1.3.2 Ordre séquentiel logique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

10.1.3.3 Caractéristiques sensorielles

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

C.10.1.3.3 Caractéristiques sensorielles

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

10.1.3.4 Orientation

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

C.10.1.3.4 Orientation

Type d’évaluation

Inspection

Conditions préalables:

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.3.4 Orientation des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.4 Orientation des WCAG 2.1.

10.1.3.5 Identifier la finalité de la saisie

Dans le cas où la TIC est un document hors ligne, elle remplit le Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

C.10.1.3.5 Identifier la finalité de la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

10.1.4 Distinguable
Clause de la norme EN 301 549Détermination de la conformité

10.1.4.1 Utilisation de la couleur

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

C.10.1.4.1 Utilisation de la couleur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

10.1.4.2 Contrôle du son

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.1.

Tableau 10.1: Critère de succès du document: Contrôle du son

Si la lecture d’un fichier audio tiré d’un document dure plus de 3 secondes, un mécanisme est disponible pour le mettre en pause, l’arrêter ou pour en contrôler le volume de façon indépendante du niveau de volume du système général.

REMARQUE 1: Puisque toute partie d’un document ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le document entier, tout le contenu présent dans le document (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) doit satisfaire à ce critère de succès.

REMARQUE 2: Ce critère de succès est identique au critère de succès 1.4.2 Contrôle du son des WCAG 2.1, après remplacement de « sur une page Web » par « sur un document », de « tout contenu » par « toute partie d’un document », de « page entière » par « document entier », de « sur la page Web » par « sur le document », après suppression de « Voir l’exigence de conformité 5: Non-interférence » et après l’ajout de la note 1.

C.10.1.4.2 Contrôle du son

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.1.4.3 Contraste (minimum)

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.4.3 Contraste des WCAG 2.1.

C.10.1.4.3 Contraste (minimum)

Type d’évaluation: Inspection

Conditions préalables

· 1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

10.1.4.4 Redimensionnement du texte

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

REMARQUE 1: Les contenus pour lesquels il existe des lecteurs de logiciels, des visualiseurs ou des éditeurs dotés d’une fonction de zoom de 200% répondraient automatiquement à ce critère de succès lorsqu’ils sont utilisés avec ces lecteurs, à moins que le contenu ne fonctionne pas avec le zoom.

REMARQUE 2: Ce critère de succès concerne la capacité de permettre aux utilisateurs d’agrandir le texte à l’écran au moins jusqu’à 200% sans avoir besoin d’avoir recours à des technologies d’assistance. Cela signifie que l’application fournit un moyen d’agrandir le texte à 200% (zoom ou autre) sans perte de contenu ou de fonctionnalité ou que l’application fonctionne avec les fonctions de la plateforme qui répondent à cette exigence.

REMARQUE 3: La pratique exemplaire consiste à n’utiliser que des polices qui permettent une mise à l’échelle sans perte de qualité (p. ex. une présentation pixellisée). Cela s'applique en particulier aux polices intégrées.

C.10.1.4.4 Redimensionnement du texte

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

10.1.4.5 Texte sous forme d’image

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

C.10.1.4.5 Texte sous forme d’image

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès1.4.5 Texte sous forme d’image des WCAG 2.1.

10.1.4.10 Redistribution

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.2.

Tableau 10.2: Critère de succès du document: Redistribution

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessiter de défilement en deux dimensions en ce qui a trait aux éléments suivants:

  • Contenu à défilement vertical d’une largeur équivalente à 320 pixels CSS;
  • Contenu à défilement horizontal d’une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1: 320 pixels CSS équivalent à une largeur de fenêtre de départ de 1 280 pixels CSS avec un zoom de 400%. Pour les documents qui sont conçus pour défiler horizontalement (par exemple avec du texte vertical), les 256 pixels CSS équivalent à une hauteur de fenêtre de départ de 1 024 pixels avec un zoom de 400%.

REMARQUE 2: Les exemples de contenu qui nécessitent une mise en page bidimensionnelle sont les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données et les interfaces où il est nécessaire de garder les barres d’outils en vue pendant la manipulation du contenu.

REMARQUE 3: Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

C.10.1.4.10 Redistribution

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.2.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

C.10.1.4.11 Contraste du contenu non textuel

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un document hors ligne qui n’a pas de zone de présentation de contenu de taille fixe qui est essentielle à l’information véhiculée.

Procédure

1. Vérifier que le document n’échoue pas au Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

10.1.4.12 Espacement du texte

Dans le cas où la TIC est un document hors ligne qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

C.10.1.4.12 Espacement du texte

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

10.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un document hors ligne, elle remplit le Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

C.10.1.4.13 Contenu au survol ou au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.13 Contenu en mode survol ou focus des WCAG 2.1.

10.2 Utilisable
10.2.1 Accessibilité au clavier
Clause de la norme EN 301 549Détermination de la conformité

10.2.1.1 Clavier

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 2.1.1 Clavier des WCAG 2.1.

C.10.2.1.1 Clavier

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 2.1.1 Clavier des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.1 Clavier des WCAG 2.1.

10.2.1.2 Pas de piège au clavier

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.3.

Tableau 10.3: Critère de succès du document: Pas de piège au clavier

Si la Au focus du clavier peut être positionnée sur un élément de la page à l’aide d’une interface clavier, réciproquement, il peut être déplacé hors de ce même composant simplement à l’aide d’une interface clavier et, si ce déplacement exige plus que l’utilisation d’une simple touche flèche ou tabulation ou toute autre méthode standard de sortie, l’utilisateur est informé de la méthode permettant de déplacer la Au focus hors de ce composant.

REMARQUE 1: Puisque toute partie d’un document ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le document entier, il est nécessaire que tout le contenu présent dans le document (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) satisfasse à ce critère de succès.

REMARQUE 2: La méthode standard de sortie pourrait varier d’une plateforme à l’autre. Par exemple, la touche Échap est une méthode standard de sortie sur de nombreuses plateformes de bureau.

C.10.2.1.2 Pas de piège au clavier

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.3.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier des caractères des WCAG 2.1 .

C.10.2.1.4 Raccourcis clavier utilisant des caractères

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure:

1. Vérifier que la page Web n’échoue pas au critère de succès 2.1.4 Raccourcis clavier des caractères des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

10.2.2 Délai suffisant
Clause de la norme EN 301 549Détermination de la conformité

10.2.2.1 Réglage du délai

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.4.

Tableau 10.4: Critère de succès du document: Réglage du délai

Pour chaque limite de temps fixée par le document, au moins l’un des points suivants est vrai:

  • Suppression: L’utilisateur a la possibilité de désactiver la limite de temps avant de l’atteindre; ou
  • Ajustement: L’utilisateur a la possibilité d’ajuster la limite de temps avant de la rencontrer dans un intervalle d’au moins dix fois la durée paramétrée par défaut; ou
  • Extension: L’utilisateur est averti avant que la limite de temps expire et il lui est accordé au moins 20 secondes pour étendre cette limite par une action simple (par exemple, « appuyer sur la barre d’espace ») et l’utilisateur a la possibilité d’étendre la limite de temps au moins dix fois; ou
  • L’exception du temps réel: La limite de temps est une partie constitutive d’un événement en temps réel (par exemple, une enchère) et aucune solution de rechange n’est possible; ou
  • L’exception de la limite essentielle: La limite de temps est essentielleet l’étendre invaliderait alors l’activité; ou
  • L’exception des 20 heures: La limite de temps est supérieure à 20 heures.

REMARQUE 1: Ce critère de succès permet de s’assurer que les utilisateurs peuvent accomplir les tâches sans changements inattendus dans le contenu ou le contexte résultant d’une limite de temps. Ce critère de succès doit être considéré conjointement avec le critère de succès 3.2.1 des WCAG 2.1, qui impose des limites aux changements de contenu ou de contexte résultant de l’action des utilisateurs.

REMARQUE 2: Ce critère de succès est identique au critère de succès 2.2.1 Réglage du délai des WCAG 2.1, après le remplacement de « le contenu » par « documents » et l’ajout des mots « des WCAG 2.1 » après les mots « critère de succès » à la note 1 ci-dessus.

C.10.2.2.1 Réglage du délai

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.4.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.2.2 Mettre en pause, arrêter, masquer

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.5.

Tableau 10.5: Critère de succès du document: Mettre en pause, arrêter, masquer

Pour déplacer, faire clignoter, faire défiler ou mettre à jour automatiquement des informations, tous les éléments suivants sont vrais:

  • Déplacement, clignotement, défilement: Pour toute information en mouvement, clignotante ou défilante qui (1) démarre automatiquement, (2) dure plus de cinq secondes et (3) est présentée en parallèle avec d’autres contenus, il existe un mécanisme permettant à l’utilisateur de mettre en pause, d’arrêter ou de masquer l’information à moins que le déplacement, le clignement ou le défilement fasse partie d’une activité où cela est essentiel; et
  • Mise à jour automatique: Pour toute mise à jour qui (1) démarre automatiquement et (2) est présentée en parallèle avec d’autres contenus, il existe un mécanisme permettant à l’utilisateur de la mettre en pause, de l’arrêter, de la masquer ou de contrôler sa fréquence, sauf si la mise à jour automatique fait partie d’une activité où elle est essentielle.

REMARQUE 1: Pour les exigences relatives au contenu clignotant ou avec flash, se référer à la règle 2.3 des WCAG 2.1.

REMARQUE 2: Puisque toute partie d’un document ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le document entier, il est nécessaire que tout le contenu présent dans le document (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) satisfasse à ce critère de succès.

REMARQUE 3: Le contenu qui est mis à jour périodiquement par un logiciel ou qui est transmis en continu à l’agent utilisateur n’est pas tenu de préserver ou de présenter l’information générée ou reçue entre le début de la pause et la reprise de la présentation, car cela pourrait ne pas être techniquement possible et, dans de nombreuses situations, être trompeur.

REMARQUE 4: Une animation qui se produit dans le cadre d’une phase de préchargement ou d’une situation similaire peut être considérée comme essentielle si l’interaction ne peut pas se produire pendant cette phase pour tous les utilisateurs et si le fait de ne pas indiquer les progrès pouvait dérouter les utilisateurs ou leur faire croire que le contenu était gelé ou séparé.

REMARQUE 5: Ce critère de succès est identique au critère de succès 2.2.2 Mettre en pause, arrêter, masquer des WCAG 2.1, après remplacement de « page » et de « page Web » par « document », suppression de « Voir l’exigence de conformité 5: Non-ingérence » dans la note 2 du critère de succès, l’ajout des mots « des WCAG 2.1 » à la suite de « règle 2.3 » à la note 1 et la reformulation de la note 2 de façon à éviter le verbe « devoir ».

C.10.2.2.2 Mettre en pause, arrêter, masquer

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.5.

Résultat

Réussite: L’énoncé testable no 1 est vrai. Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.2.2 Mettre en pause, arrêter, masquer des WCAG 2.1.

10.2.3 Crises et réactions physiques
Clause de la norme EN 301 549Détermination de la conformité

10.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.6.

Tableau 10.6: Critère de succès du document: Pas plus de trois flashs ou sous le seuil critique

Un document doit être exempt de tout élément qui flashe plus de trois fois dans n’importe quel intervalle d’une seconde ou ce flash doit se situer sous le seuil de flash générique et le seuil de flash rouge.

REMARQUE 1: Puisque toute partie d’un document ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le document entier, il est nécessaire que tout le contenu présent dans le document (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) satisfasse à ce critère de succès.

REMARQUE 2: Ce critère de succès est identique au critère de succès 2.3.1 Pas plus de trois flashs ou sous le seuil critique des WCAG 2.1 après remplacement de « pages Web » par « documents », de « la page entière » par « le document entier », « la page Web » par « le document », après suppression de « Voir l’exigence de conformité 5: Non-ingérence » et après la reformulation de la note 1 ci-dessus pour éviter le verbe « devoir ».

C.10.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.6.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.4 Navigable
Clause de la norme EN 301 549Détermination de la conformité

10.2.4.2 Titre de document

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.7.

Tableau 10.7: Critère de succès du document: Titre de document

Les documents présentent un titre qui décrit leur sujet ou leur but.

REMARQUE 1: Le nom d’un document (p. ex. document, fichier multimédia) peut servir de titre s’il décrit le sujet ou le but.

REMARQUE 2: Ce critère de succès est identique au critère de succès 2.4.2 Titre de page des WCAG 2.1 après remplacement de « pages Web » par « documents » et après ajout de la note 1 ci-dessus.

C.10.2.4.2 Titre de document

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.7.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.4.3 Parcours du focus

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.8.

Tableau 10.8: Critère de succès du document: Parcours du focus

Si un document peut être parcourue de façon séquentielle et que les séquences de navigation affectent la signification ou l’action, les éléments reçoivent la Au focus dans un ordre qui préserve la signification et l’opérabilité.

REMARQUE: Ce critère de succès est identique au critère de succès 2.4.3 Parcours de la cible de saisie des WCAG 2.1 après remplacement de « page Web » par « document ».

C.10.2.4.3 Parcours du focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.8.

Résultat

Réussite: L’énoncé testable no 1 est vrai. Échec: L’énoncé testable no 1 est faux.

10.2.4.4 Fonction du lien (selon le contexte)

Dans le cas où la technologie est un document, celle-ci doit satisfaire au critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

C.10.2.4.4 Fonction du lien (selon le contexte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez que le document n’échoue pas au critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

10.2.4.6 En-têtes et étiquettes

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

C.10.2.4.6 En-têtes et étiquettes

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

10.2.4.7 Visibilité du focus

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 2.4.7 Visibilité de la cible de saisie des WCAG 2.1.

C.10.2.4.7 Visibilité du focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 2.4.7 Visibilité de la cible de saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.7 Visibilité du focus des WCAG 2.1.

10.2.5 Modalités d’entrée
Clause de la norme EN 301 549Détermination de la conformité

10.2.5.1 Gestes pour le contrôle du pointeur

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.9.

Tableau 10.9: Critère de succès du document: Gestes pour le contrôle du pointeur

Toutes les fonctions qui utilisent des mouvements multipoints ou basés sur un tracé pour exécuter une commande peuvent être utilisées avec un seul pointeur sans mouvement basé sur un tracé, à moins qu’un mouvement multipoint ou basé sur un tracé soit essentiel.

REMARQUE 1: cette exigence s’applique aux documents qui interprètent les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 2: ce critère de succès est identique au critère de succès 2.5.1 Mouvements du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

C.10.2.5.1 Gestes pour le contrôle du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.9.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.5.2 Annulation de l’action du pointeur

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.10.

Tableau 10.10: Critère de succès du document: Annulation de l’action du pointeur

Dans le cas des fonctions qui peuvent fonctionner à l’aide d’un seul pointeur, au moins l’un des éléments suivants est vrai:

  • Aucun événement descendant: l’événement descendant n’est pas utilisé pour exécuter une partie de la fonction;
  • Abandonner ou Annuler: la fonction se termine avec l’événement ascendant et un mécanisme est disponible pour abandonner la fonction avant la fin ou pour annuler la fonction une fois l’exécution de la fonction terminée;
  • Inversion de l’événement: l’événement montant inverse tout résultat de l’événement descendant précédent;
  • Essentiel: terminer la fonction sur inversion de l’événement est essentiel.

REMARQUE 1: les fonctions qui émulent un appui clavier ou un pavé numérique sont considérées comme essentielles.

REMARQUE 2: cette exigence s’applique au contenu Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 3: Ce critère de succès est identique au critère de succès 2.5.2 Annulation du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

C.10.2.5.2 Annulation de l’action du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.10.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.5.3 Étiquette dans le nom

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

C.10.2.5.3 Étiquette dans le nom

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

10.2.5.4 Activation par le mouvement

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

C.10.2.5.4 Activation par le mouvement

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

10.3 Compréhensible
10.3.1 Lisible
Clause de la norme EN 301 549Détermination de la conformité

10.3.1.1 Langue du document

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.11.

Tableau 10.11: Critère de succès du document: Langue du document

La langue par défaut de chaque document peut être déterminée par un programme informatique.

REMARQUE: Ce critère de succès est identique au critère de succès 3.1.1 Langue de la page des WCAG 2.1 après remplacement de « page Web » par « document ».

C.10.3.1.1 Langue du document

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.11.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.3.1.2 Langue d’un passage

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.12.

Tableau 10.12: Critère de succès du document: Langue d’un passage

La langue de chaque passage ou expression du document peut être déterminée par un programme informatique sauf pour un nom propre, pour un terme technique, pour un mot dont la langue est indéterminée ou pour un mot ou une expression faisant partie du langage courant de la langue utilisée dans le contexte immédiat.

REMARQUE 1: Pour certaines technologies de documentation, il n’existe pas de méthode de technologie d’assistance pouvant indiquer la langue des différents passages ou expressions du document, et il ne serait pas possible de satisfaire au critère de succès en utilisant ces technologies.

REMARQUE 2: L’héritage est une méthode courante. Par exemple, un document fournit la langue qu’il utilise et on peut supposer que tous les éléments de texte ou d’un élément d’interface utilisateur de ce document utiliseront la même langue, sauf indication contraire.

REMARQUE 3: Ce critère de succès est identique au critère de succès 3.1.2 Langue d’un passage des WCAG 2.1 après remplacement de « contenu » par « document » et après ajout des notes 1 et 2 ci-dessus.

C.10.3.1.2 Langue d’un passage

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.12.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.3.2 Prévisible
Clause de la norme EN 301 549Détermination de la conformité

10.3.2.1 Au focus

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 3.2.1 Au focus des WCAG 2.1.

REMARQUE: Certains documents composés et leurs agents utilisateurs sont conçus pour offrir des fonctions d’affichage et de modification très différentes selon la partie du document composé où les interactions ont lieu (par exemple, une présentation qui contient une feuille de calcul intégrée, dans laquelle les menus et les barres d’outils de l’agent utilisateur changent selon que l’utilisateur interagit avec le contenu de la présentation ou celui de la feuille de calcul intégrée). Si l’utilisateur utilise un mécanisme autre que celui de mettre la Au focus sur la partie du document composite avec laquelle il veut interagir (p. ex. par un choix de menu ou un mouvement spécial de clavier), tout changement de contexte qui en résulterait ne serait pas soumis à ce critère de succès parce qu’il n’a pas été causé par un déplacement de la Au focus.

C.10.3.2.1 Au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez si le document n’échoue pas au critère de succès 3.2.1 Au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.1 Au focus des WCAG 2.1.

10.3.2.2 À la saisie

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 3.2.2 À la saisie des WCAG 2.1.

C.10.3.2.2 À la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez que le document n’échoue pas au critère de succès 3.2.2 À la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.2 À la saisie des WCAG 2.1.

10.3.3 Assistance à la saisie
Clause de la norme EN 301 549Détermination de la conformité

10.3.3.1 Identification des erreurs

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

C.10.3.3.1 Identification des erreurs

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez que le document n’échoue pas au critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

10.3.3.2 Étiquettes ou instructions

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

C.10.3.3.2 Étiquettes ou instructions

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez que le document n’échoue pas au critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

10.3.3.3 Suggestion après une erreur

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

C.10.3.3.3 Suggestion après une erreur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez que le document n’échoue pas au critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

Résultat:

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

10.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.13.

Tableau 10.13: Critère de succès du document: Prévention des erreurs (juridiques, financières, de données)

Lorsqu’un document donne lieu à des engagements juridiques ou à des transactions financières de la part de l’utilisateur qui soit modifient ou effacent des données contrôlables par l’utilisateur dans des systèmes de stockages de données, soit enregistrent les réponses de l’utilisateur à un test ou un examen, au moins l’une des conditions suivantes est vraie:

1. Réversible: les actions d’envoi sont réversibles

2. Vérifiée: les données saisies par l’utilisateur sont vérifiées au niveau des erreurs de saisie et la possibilité est donnée à l’utilisateur de les corriger.

3. Confirmée: un mécanisme est disponible pour revoir, confirmer et corriger les informations avant leur soumission finale.

REMARQUE: Ce critère de succès est identique au critère de succès 3.3.4 Prévention des erreurs (juridique, financier, de données) des WCAG 2.1après remplacement de « pages Web » par « documents ».

C.10.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.13.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.4 Robuste
10.4.1 Compatible
Clause de la norme EN 301 549Détermination de la conformité

10.4.1.1 Analyse syntaxique

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.14.

Tableau 10.14: Critère de succès du document: Analyse syntaxique

Lorsqu’un document utilise un langage de balisage de telle sorte que le balisage est visible et mis à la disposition des technologies d’assistance et des fonctions d’accessibilité du logiciel ou à un agent utilisateur sélectionnable par l’utilisateur, les éléments ont des balises de début et de fin complètes, les éléments sont imbriqués selon leurs spécifications, les éléments ne contiennent pas d’attributs en double et tout identifiant est unique, sauf lorsque les spécifications permettent ces fonctions.

REMARQUE 1: Les balises de début et de fin auxquelles il manque un caractère critique, comme une parenthèse fermante ou un guillemet de valeur d’attribut mal appropriée, sont considérées incomplètes.

REMARQUE 2: Le balisage n’est pas toujours mis à la disposition des technologies d’assistance ou des agents utilisateurs sélectionnables par l’utilisateur tels que les navigateurs. Dans de tels cas, la conformité à cette disposition n’aurait aucune incidence sur l’accessibilité, comme c’est le cas pour le contenu Web lorsqu’il est exposé.

REMARQUE 3: Les exemples de balisage qui sont exposés séparément et disponibles pour les technologies d’assistance et les agents utilisateurs comprennent, sans s’y limiter: les documents encodés en HTML, ODF et OOXML. Dans ces exemples, le balisage peut être entièrement analysé de deux façons: a) par des technologies d’assistance qui peuvent ouvrir directement le document, b) par des technologies d’assistance utilisant des API DOM d’agents utilisateurs pour ces formats de document.

REMARQUE 4: Ce critère de succès est identique au critère de succès 4.1.1 Analyse syntaxique des WCAG 2.1 après remplacement de « Dans le contenu mis en œuvre en utilisant des langages de balisage » par « Lorsqu’un document utilise un langage de balisage de telle sorte que le balisage est visible et mis à la disposition des technologies d’assistance et des fonctions d’accessibilité du logiciel ou à un agent utilisateur sélectionnable par l’utilisateur » et après l’ajout des notes 2 et 3 ci-dessus.

C.10.4.1.1 Analyse syntaxique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.14.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.4.1.2 Nom, rôle et valeur

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.15.

Tableau 10.15: Critère de succès du document: Nom, rôle et valeur

Pour tout composant d’interface utilisateur (comprenant, mais n’étant pas limité aux éléments de formulaire, liens et composants générés par des scriptes), le nom et le rôle peuvent être déterminés par un programme informatique ; les états, les propriétés et les valeurs qui peuvent être paramétrés par l’utilisateur peuvent être définis par un programme informatique ; et la notification des changements de ces éléments est disponible aux agents utilisateurs, incluant les technologies d’assistance.

REMARQUE 1: Ce critère de succès s’adresse principalement aux développeurs de logiciels qui développent ou utilisent des composants d’interface utilisateur personnalisés. Les composants d’interface utilisateur standard de la plupart des plateformes qui prennent en charge l’accessibilité répondent déjà à ce critère de succès lorsqu’ils sont utilisés conformément aux spécifications.

REMARQUE 2: Pour les formats de documents qui prennent en charge l’interopérabilité avec la technologie d’assistance, les composants d’interface utilisateur standard satisfont souvent à ce critère de succès lorsque leur usage est conforme aux indications générales en matière de conception et d’accessibilité pour le format du document.

REMARQUE 3: Ce critère de succès est identique au critère de succès 4.1.2 Nom, rôle et valeur des WCAG 2.1 après remplacement de la note originale des WCAG 2.1 par note 1 et après ajout de la note 2 ci-dessus.

C.10.4.1.2 Nom, rôle et valeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.15.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.4.1.3 Messages d’état

Tableau 10.15: Critère de succès du document: Nom, rôle et valeur

Lorsque la TIC est un document non Web, elle doit satisfaire critère de succès 4.1.3 Messages d’état des WCAG 2.1.

C.10.4.1.3 Messages d’état

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un document non Web

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 4.1.3 Messages d’état des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 4.1.3 Messages d’état des WCAG 2.1.

10.5 Positionnement des sous-titres

Lorsque la TIC est un document hors ligne qui contient des médias synchronisés avec des sous-titres, ces sous-titres ne doivent pas masquer l’information pertinente contenue dans les médias synchronisés.

C.10.5 Positionnement des sous-titres

La clause 10.5 est un avis seulement et ne contient aucune exigence testable.

10.6 Synchronisation de la audio description

Lorsque la TIC est un document hors ligne qui contient un média synchronisé avec description sonore, cette description sonore ne doit pas interférer avec les informations audio pertinentes du média synchronisé.

C.10.6 Synchronisation de la audio description

La clause 10.6 est un avis seulement et ne contient aucune exigence testable.

11 Logiciels

Clause de la norme EN 301 549Détermination de la conformité

11.0 Généralités (information)

Cette clause précise les exigences qui s’appliquent:

  • aux logiciels de plateformes;
  • aux logiciels qui ont une interface utilisateur, y compris le contenu du logiciel;
  • aux outil-auteurs;
  • aux logiciels qui servent de technologie d’assistance.

REMARQUE 1: L’agent utilisateur est un exemple de logiciel qui possède une interface utilisateur.

REMARQUE 2: Les exigences relatives au contenu Web, notamment aux logiciels qui sont du contenu Web, se trouvent à La clause 9.

REMARQUE 3: Les exigences relatives aux documents, qui peuvent être présentés par les agents utilisateurs, se trouvent à La clause 10.

REMARQUE 4: Bien que l’accessibilité des interfaces de ligne de commande ne soit pas abordée dans le présent document, l’accessibilité peut être réalisée au moyen d’exigences contextuelles, dont certaines se trouvent dans les clauses 5 et 11.

Les exigences des clauses 11.1 à 11.5 s’appliquent aux logiciels:

  • qui ne sont pas des pages Web;
  • qui ne sont pas intégrés dans une page Web ni utilisés dans le rendu ou le fonctionnement de la page.

La clause 9 énonce les exigences de conformité des logiciels qui se trouvent dans des pages Web ou qui sont intégrés dans des pages Web, et qui sont utilisés dans le rendu ou qui sont destinés à être rendus avec la page Web dans laquelle ils sont intégrés.

Certaines exigences des clauses 11.1 à 11.5 ont des versions différentes selon que la fonctionnalité est non restreinte ou restreinte. Dans ces cas, La clause correspondante est divisée en deux sous-dispositions.

Les critères de succès énoncés dans les clauses 11.1 à 11.5 visent à s’harmoniser avec la Note du groupe de travail [i.26] produite par le WCAG2ICT Task Force du W3C.

REMARQUE 5: Le logiciel qui fournit une interface utilisateur comprend son propre contenu. Voici quelques exemples de contenu présent dans un logiciel: les composants d’interface et le texte d’une barre de menu issus d’une application d’interface utilisateur graphique, les icônes d’une barre d’outils, les invites prononcées dans une interface utilisateur audio, les autres commandes d’interaction utilisateur et les textes, graphiques ou documents qui sont chargés à l'extérieur du logiciel.

C.11.0 Généralités (information)

La clause 11.0 n’a qu’une valeur informative et ne contient aucune exigence relative aux tests de conformité.

11.1 Perceptible
11.1.1 Équivalents textuels
11.1.1.1 Contenu non textuel
Clause de la norme EN 301 549Détermination de la conformité

11.1.1.1.1 Contenu non textuel (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

REMARQUE: Les CAPTCHAS n’apparaissent pas actuellement hors du Web. Cependant, s’ils apparaissent, la présente directive est pertinente.

C.11.1.1.1.1 Contenu non textuel (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.1.1.1.2 Contenu non textuel (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, cette technologie satisfait à l’exigence 5.1.3.6 (sortie vocale pour contenu non textuel).

C.11.1.1.1.2 Contenu non textuel (fonction restreinte)

Type d’évaluation

Examen

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. Le contenu non textuel est présenté aux utilisateurs via la sortie vocale.

Procédure

1. Vérifier que la sortie vocale est fournie comme solution de rechange au contenu non textuel.

2. Vérifier que le contenu non textuel n’est pas seulement présent à titre décoratif.

3. Vérifier que le contenu non textuel n’est pas utilisé uniquement pour le formatage visuel.

4. Vérifier que la sortie vocale est conforme aux indications relatives à l’ équivalent textuel » décrit dans les critères de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite: Les énoncés testables nos 1, 2, 3 et 4 sont vrais; ou le no 1 et le no 2 sont faux; ou le no 1 et le no 3 sont faux.

Échec: L’énoncé testable no 1 est vrai et le no 2 est faux; ou le no 1 est vrai et le no 3 est faux; ou les nos 1, 2 et 3 sont vrais et le no 4 est faux.

Non applicable : La condition préliminaire 1, 2 ou 3 n’est pas remplie.

11.1.2 Médias temporels
11.1.2.1 Contenu seulement audio et seulement vidéo (préenregistré)
Clause de la norme EN 301 549Détermination de la conformité

11.1.2.1.1 Contenu seulement audio et seulement vidéo (pré-enregistré – fonction non restreinte)

Dans le cas où la TIC est un logiciel non-Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran et où un contenu audio préenregistré n’est pas nécessaire pour permettre l’utilisation des fonctions restreintes des TIC, la technologie remplit le Critère de succès 1.2.1 Contenu seulement audio et seulement vidéo (pré-enregistré) des WCAG 2.1.

REMARQUE: Le média de remplacement peut être fourni directement dans le logiciel – ou fourni dans une version de remplacement qui satisfait au critère de succès.

C.11.1.2.1.1 Contenu seulement audio ou vidéo (pré-enregistré – fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. Un contenu audio pré-enregistré n’est pas nécessaire pour permettre l’utilisation des fonctions restreintes de la TIC.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.1 Contenu seulement audio ou vidéo (pré-enregistré) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.2.1.2 Contenu seulement audio et seulement vidéo (pré-enregistré – fonction restreinte)
Clause de la norme EN 301 549Détermination de la conformité

11.1.2.1.2.1 Contenu pré-enregistré seulement audio (fonction restreinte)

Lorsque la TIC est un logiciel non-Web qui fournit une interface utilisateur qui ne prend pas en charge les technologies d’assistance pour la lecture d’écran et où des informations auditives pré-enregistrées sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, la fonctionnalité des logiciels qui fournissent une interface utilisateur doit satisfaire à l’exigence 5.1.5 (sortie visuelle pour informations auditives).

C.11.1.2.1.2.1 Contenu pré-enregistré seulement audio (fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. Un contenu audio pré-enregistré est nécessaire pour permettre l’utilisation des fonctions restreintes de la TIC.

Procédure

1. Vérifier que l’information visuelle est équivalente à la sortie auditive pré-enregistrée.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.2.1.2.2 Contenu pré-enregistré seulement vidéo (fonction restreinte)

Dans le cas où la technologie d’information et de communications (TIC) est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit l’exigence 5.1.3.7 (sortie vocale pour information vidéo).

C.11.1.2.1.2.2 Contenu pré-enregistré seulement vidéo (fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. Un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation des fonctions restreintes de la TIC.

4. La sortie vocale est fournie comme mode alternatif à une utilisation sans vision du contenu non textuel affiché sur une fonction restreinte.

Procédure

1. Vérifier que la sortie vocale présente des informations équivalentes pour le contenu vidéo pré-enregistré.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2, 3 ou 4 n’est pas remplie.

11.1.2.2 Sous-titres (pré-enregistrés)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

REMARQUE: La définition de « sous-titres » donnée par les WCAG 2.1 précise que « dans certains pays, les sous-titres sont appelés captions et subtitles ». On les appelle aussi parfois « sous-titres pour malentendants ». Selon la définition des WCAG 2.1, pour satisfaire à ce critère de succès, qu’il s’agisse de captions ou de subtitles, les sous-titres doivent fournir un « visuel synchronisé ou équivalent textuel pour l’information audio avec ou sans paroles nécessaires à la compréhension du contenu d’un média », lorsque l’information sans paroles comprend des « effets sonores, de la musique, des rires, l’identification et le positionnement des interlocuteurs ».

Critères de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1

Comprendre les sous-titres (pré-enregistrés) (en anglais seulement)

Comment satisfaire au critère Sous-titres (pré-enregistrés) (en anglais seulement)

(Niveau A)

Fournir des sous-titres pour tout contenu audio préenregistré dans un média synchronisé, excepté lorsque le média est un média de remplacement pour un texte et qu’il est clairement identifié comme tel.

C.11.1.2.2 Sous-titres (pré-enregistrés)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

11.1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré)
Clause de la norme EN 301 549Détermination de la conformité

11.1.2.3.1 Audio-description ou version de remplacement pour un média temporel (pré-enregistré et fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 1.2.3 audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

REMARQUE 1: La définition des WCAG 2.1 précise qu’ « audio-description » est également nommée « vidéo-description » et « narration descriptive ».

REMARQUE 2: Des pistes audio secondaires ou de remplacement sont couramment utilisées à cette fin.

C.11.1.2.3.1 Audio-description ou version de remplacement pour un média temporel (pré-enregistré et fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.2.3 audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

11.1.2.3.2 Audio-description ou version de remplacement pour un média temporel (pré-enregistré et fonction restreinte)

Dans le cas où la technologie d’information et de communications (TIC) est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit l’exigence 5.1.3.7 (sortie vocale pour information vidéo).

C.11.1.2.3.2 Audio-description ou version de remplacement pour un média temporel (pré-enregistré et fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. La sortie vocale est fournie comme mode alternatif à une utilisation sans vision du contenu non textuel affiché sur une fonction restreinte.

Procédure

1. Vérifier que la sortie vocale présente des informations équivalentes pour le contenu vidéo pré-enregistré.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.2.4 Sous-titres (en direct)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

REMARQUE: La définition de « sous-titres » donnée par les WCAG 2.1 précise que « dans certains pays, les sous-titres sont appelés captions et subtitles ». On les appelle aussi parfois « sous-titres pour malentendants ». Selon la définition des WCAG 2.1, pour satisfaire à ce critère de succès, qu’il s’agisse de captions ou de subtitles, les sous-titres doivent fournir un « visuel synchronisé ou équivalent textuel pour l’information audio avec ou sans paroles nécessaires à la compréhension du contenu d’un média », lorsque l’information sans paroles comprend des « effets sonores, de la musique, des rires, l’identification et le positionnement des interlocuteurs ».

C.11.1.2.4 Sous-titres (en direct)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

11.1.2.5 Audio-description (pré-enregistrée)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.2.5 audio-description (pré-enregistrée) des WCAG 2.1.

REMARQUE 1: La définition des WCAG 2.1 précise « audio-description » est également nommée « vidéo-description » et « narration descriptive ».

REMARQUE 2: Des pistes audio secondaires ou de remplacement sont couramment utilisées à cette fin.

C.11.1.2.5 Audio-description (pré-enregistrée)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.2.5 audio-description(pré-enregistrée) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.5 Audio-description (pré-enregistrée) des WCAG 2.1).

11.1.3 Adaptable
11.1.3.1 Information et relations
Clause de la norme EN 301 549Détermination de la conformité

11.1.3.1.1 Information et relations (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE: Dans le domaine des logiciels, la meilleure façon de déterminer par un programme informatique est d’utiliser les services d’accessibilité fournis par les logiciels de plateforme visant à permettre l’interopérabilité entre les logiciels et les technologies d’assistance et les fonctions d’accessibilité des logiciels. (voir La clause 11.5 Interopérabilité avec la technologie d’assistance).

C.11.1.3.1.1 Information et relations (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 1.3.1 Information et relations des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.1.3.1.2 Information et relations (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran et où l’information affichée à l’écran, la TIC devrait fournir des informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio et l’information affichée à l’écran.

REMARQUE 1: De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que la du focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2: Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées par la présentation.

C.11.1.3.1.2 Information et relations (fonction restreinte)

Clause 11.1.3.1.2 est un avis seulement et ne contient aucune exigence testable.

11.1.3.2 Ordre séquentiel logique
Clause de la norme EN 301 549Détermination de la conformité

11.1.3.2.1 Ordre séquentiel logique (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

C.11.1.3.2.1 Ordre séquentiel logique (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.1.3.2.2 Ordre séquentiel logique (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran et où l’information affichée à l’écran, la TIC devrait fournir des informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio et l’information affichée à l’écran.

REMARQUE 1: De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que la du focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2: Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées par la présentation.

C.11.1.3.2.2 Ordre séquentiel logique (fonction restreinte)

Clause 11.1.3.2.2 est un avis seulement et ne contient aucune exigence testable.

11.1.3.3 Caractéristiques sensorielles

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

C.11.1.3.3 Caractéristiques sensorielles

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

11.1.3.4 Orientation

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

C.11.1.3.4 Orientation

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.3.4 Orientation des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès critère de succès 1.3.4 Orientation des WCAG 2.1.

11.1.3.5 Identifier la finalité de la saisie
Clause de la norme EN 301 549Détermination de la conformité

11.1.3.5.1 Identifier la finalité de la saisie (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit remplir le Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

C.11.1.3.5.1 Identifier la finalité de la saisie (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1

11.1.3.5.2 Identifier la finalité de la saisie (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui est restreint aux technologies d’assistance, elle doit prévoir au moins un mode de fonctionnement selon lequel l’utilisateur est présenté, sous forme audio, la finalité de chaque champ de saisie recueillant des renseignements sur l’utilisateur, lorsque ce champ sert une finalité définie à la section Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

C.11.1.3.5.2 Identifier la finalité de la saisie (fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

Procédure

1. Vérifier que la sortie sonore est fournie par le biais d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci.

2. Vérifier que la sortie sonore est fournie au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

3. Vérifier que la sortie sonore comprend la finalité de la section Finalité de saisie des composants d’interface utilisateur

Résultat

Réussite : L’énoncé testable (no 1 ou no 2) est vrai et l’énoncé testable no 3 est vrai.

Échec : Les énoncés testables (nos 1 et 2) sont faux ou l’énoncé testable no 3 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.4 Distinguable
Clause de la norme EN 301 549Détermination de la conformité

11.1.4.1 Utilisation de la couleur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

C.11.1.4.1 Utilisation de la couleur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

11.1.4.2 Contrôle du son

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès indiqué dans le tableau 11.1.

Tableau 11.1: Critère de succès du logiciel: Contrôle du son

Si la lecture d’un fichier audio tiré d’un document dure plus de 3 secondes, un mécanisme est disponible pour le mettre en pause, l’arrêter ou pour en contrôler le volume de façon indépendante du niveau de volume du système général.

REMARQUE 1: Puisque toute partie d’un document ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le document entier, tout le contenu présent dans le document (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) doit satisfaire à ce critère de succès.

REMARQUE 2: Ce critère de succès est identique au critère de succès 1.4.2 Contrôle du son des WCAG 2.1, après remplacement de « sur une page Web » par « sur un document », de « tout contenu » par « toute partie d’un document », de « page entière » par « document entier », de « sur la page Web » par « sur le document », après suppression de « Voir l’exigence de conformité 5: Non-interférence » et après l’ajout de la note 1.

C.11.1.4.2 Contrôle du son

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.1.4.3 Contraste (minimum)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

C.11.1.4.3 Contraste (minimum)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

11.1.4.4 Redimensionnement du texte
Clause de la norme EN 301 549Détermination de la conformité

11.1.4.4.1 Redimensionnement du texte (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux fonctions d’élargissement de la plateforme ou de la technologie d’assistance, elle remplit le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

REMARQUE 1: Les contenus pour lesquels il existe des lecteurs de logiciels, des visualiseurs ou des éditeurs dotés d’une fonction de zoom de 200% répondraient automatiquement à ce critère de succès lorsqu’ils sont utilisés avec ces lecteurs, à moins que le contenu ne fonctionne pas avec le zoom.

REMARQUE 2: Ce critère de succès concerne la capacité de permettre aux utilisateurs d’agrandir le texte à l’écran au moins jusqu’à 200% sans avoir besoin d’avoir recours à des technologies d’assistance. Cela signifie que l’application fournit un moyen d’agrandir le texte à 200% (zoom ou autre) sans perte de contenu ou de fonctionnalité ou que l’application fonctionne avec les fonctions de la plateforme qui répondent à cette exigence.

C.11.1.4.4.1 Redimensionnement du texte (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge les fonctions d’élargissement de la plateforme ou de la technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

11.1.4.4.2 Redimensionnement du texte (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne pas prend en charge l’accès aux fonctions d’agrandissement de la plateforme ou à la technologie d’assistance, elle remplit l’exigence 5.1.4 (fonction restreinte à l’agrandissement du texte).

REMARQUE: Comme la prise en charge du texte dans un environnement restreinte peut être plus limitée que celle des agents utilisateurs pour le Web, satisfaire au critère 11.1.4.4.2 dans un environnement restreint peut imposer un fardeau beaucoup plus lourd à l’auteur du contenu.

C.11.1.4.4.2 Redimensionnement du texte (fonction restreinte)

Type d’évaluation

Inspection et établissement de mesures

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur est restreinte aux fonctions d’agrandissement de la plateforme ou de la technologie d’assistance.

3. Une distance de visualisation est définie par le fournisseur.

Procédure

1. Mesurer la hauteur de la lettre H en majuscule.

2. Vérifier qu’il sous-entend un angle d’au moins 0,7 degré à la distance de visualisation définie.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.4.5 Texte sous forme d’image
Clause de la norme EN 301 549Détermination de la conformité

11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

Critère 1.4.5 Texte sous forme d’image

Comprendre le texte sous forme d’image (en anglais seulement)

Comment satisfaire au critère Texte sous forme d’image (en anglais seulement)

(Niveau AA)

Si les technologies utilisées peuvent réaliser la présentation visuelle, le texteest utilisé pour véhiculer de l’information plutôt que du texte sous forme d’image, sauf dans les cas suivants:

· Personnalisable: Le texte sous forme d’image peut être personnalisé visuellement selon les exigences de l’utilisateur;

· Essentielle: Une présentation spécifique du texte est essentielle à l’information véhiculée.

Remarque: Les logotypes sont considérés comme essentiels (le texte qui fait partie d’un logo ou d’un nom de marque).

C.11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

11.1.4.5.2 Texte sous forme d’image (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge les technologies d’assistance pour la lecture d’écran, il n’est pas nécessaire qu’elle remplisse le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1, car il n’y a pas lieu d’imposer une exigence à toutes les fonctions restreintes que le texte affiché à l’écran soit effectivement représenté en interne sous forme de texte (au sens des WCAG 2.1) puisqu’il n’y a pas d’interopérabilité avec les technologies d’assistance.

Critère 1.4.5 Texte sous forme d’image

Comprendre le texte sous forme d’image (en anglais seulement)

Comment satisfaire au critère Texte sous forme d’image (en anglais seulement)

(Niveau AA)

Si les technologies utilisées peuvent réaliser la présentation visuelle, le texteest utilisé pour véhiculer de l’information plutôt que du texte sous forme d’image, sauf dans les cas suivants:

  • Personnalisable: Le texte sous forme d’image peut être personnalisé visuellement selon les exigences de l’utilisateur;
  • Essentielle: Une présentation spécifique du texte est essentielle à l’information véhiculée.

Remarque: Les logotypes sont considérés comme essentiels (le texte qui fait partie d’un logo ou d’un nom de marque).

C.11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. Le contenu non textuel est présenté aux utilisateurs via la sortie vocale.

Procédure

1. Vérifier que la sortie vocale est fournie comme solution de rechange au contenu non textuel.

2. Vérifier que le contenu non textuel n’est pas seulement présent à titre décoratif.

3. Vérifier que le contenu non textuel n’est pas utilisé uniquement pour le formatage visuel.

4. Vérifier que la sortie vocale est conforme aux indications relatives à l’« équivalent textuel » décrit dans le critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite : Les énoncés testables (nos 1, 2, 3 et 4) sont vrais ou le (no 1 et le no 2) sont faux ou le (no 1 et le no 3) sont faux.

Échec : L’énoncé testable (no 1 est vrai et le no 2 est faux); ou (le no 1 est vrai et le no 3 est faux); ou les (nos 1, 2 et 3 sont vrais et le no 4 est faux).

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.4.10 Redistribution

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès indiqué dans le tableau 11.2.

Tableau 11.2: Documenter le critère de succès: Redistribution

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • Contenu à défilement vertical d’une largeur équivalente à 320 pixels CSS;
  • Contenu à défilement horizontal d’une hauteur équivalente à 256 pixels CSS;

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1: 320 pixels CSS équivalent à une largeur de fenêtre de départ de 1 280 pixels CSS avec un zoom de 400%. Pour les logiciels non Web qui sont conçus pour défiler horizontalement (par exemple avec du texte vertical), les 256 pixels CSS équivalent à une hauteur de fenêtre de départ de 1 024 pixels avec un zoom de 400%.

REMARQUE 2: Les exemples de contenu qui nécessitent une mise en page bidimensionnelle sont les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données et les interfaces où il est nécessaire de garder les barres d’outils en vue pendant la manipulation du contenu.

REMARQUE 3: Ce critère de succès est identique au critère de succès 1.4.10 Redisposition des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

C.11.1.4.10 Redistribution

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.2.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.1.4.11 Contraste du contenu non textuel

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

C.11.1.4.11 Contraste du contenu non textuel

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas le Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.11 Contraste des éléments non textuels des WCAG 2.1.

11.1.4.12 Espacement du texte

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

C.11.1.4.12 Espacement du texte

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

11.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

C.11.1.4.13 Contenu au survol ou au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

11.2 Utilisable
11.2.1 Accessibilité au clavier
11.2.1.1 Clavier
Clause de la norme EN 301 549Détermination de la conformité

11.2.1.1.1 Clavier (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès à des claviers ou à une interface clavier, elle doit satisfaire au critère de succès 2.1.1 Clavier des WCAG 2.1.

REMARQUE: cela ne signifie pas qu’un logiciel est nécessaire pour prendre directement en charge un clavier ou une « interface clavier ». Cela n’implique pas non plus qu’un logiciel soit requis pour fournir un clavier programmable. Le logiciel de plateforme sous-jacent peut fournir des services de saisie indépendants de dispositifs à des applications qui assurent l’exploitation à l’aide d’un clavier. Le logiciel qui prend en charge l’exploitation par l’intermédiaire de ces services indépendants pourrait être utilisé par un clavier et serait conforme.

C.11.2.1.1.1 Clavier (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge les claviers ou une interface clavier.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 2.1.1 Clavier des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.1 Clavier des WCAG 2.1.

11.2.1.1.2 Clavier (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier: fonction restreinte).

C.11.2.1.1.2 Clavier (fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur est restreinte aux claviers ou aux interfaces clavier.

Procédure

1. Vérifier que toutes les fonctions de l’interface utilisateur sont utilisables sans vision.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.2.1.2 Pas de piège au clavier

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès indiqué dans le tableau 11.3.

Tableau 11.3: Critère de succès du logiciel: Pas de piège au clavier

Si la du focus du clavier peut être positionnée sur un élément du logiciel à l’aide d’une interface clavier, réciproquement, il peut être déplacé hors de ce même composant simplement à l’aide d’une interface clavier et, si ce déplacement exige plus que l’utilisation d’une simple touche flèche ou tabulation ou toute autre méthode standard de sortie, l’utilisateur est informé de la méthode permettant de déplacer la du focus hors de ce composant.

REMARQUE 1: puisque toute partie d’un logiciel ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le logiciel entier, il est nécessaire que tout le contenu présent dans le logiciel (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) satisfasse à ce critère de succès.

REMARQUE 2: La méthode standard de sortie pourrait varier d’une plateforme à l’autre. Par exemple, la touche Échap est une méthode standard de sortie sur de nombreuses plateformes de bureau.

REMARQUE 3: ce critère de succès est identique au critère de succès 2.1.2 Pas de piège au clavier des WCAG 2.1 à clavier après remplacement de « contenu », « page » et « page Web » par « logiciel », après suppression de « Voir l’exigence de conformité 5: Non-interférence », après l’ajout de la note 2 ci-dessus et la reformulation de la note 1 ci-dessus de manière à éviter le verbe « devoir ».

C.11.2.1.2 Pas de piège au clavier

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.3.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.2.1.4 Raccourcis clavier des caractères
Clause de la norme EN 301 549Détermination de la conformité

11.2.1.4.1 Raccourcis clavier utilisant des caractères (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au Critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

C.11.2.1.4.1 Raccourcis clavier utilisant des caractères (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas au Critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

11.2.1.4.2 Raccourcis clavier utilisant des caractères (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier: fonction restreinte).

C.11.2.1.4.2 Raccourcis clavier utilisant des caractères (fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La fonctionnalité des TIC est f restreintes aux claviers ou aux interfaces clavier.

2. La fonctionnalité des TIC est restreintes aux claviers ou aux interfaces clavier.

Procédure

1. Vérifier que toutes les fonctions sont utilisables sans vision.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.2.2 Délai Suffisant
Clause de la norme EN 301 549Détermination de la conformité

11.2.2.1 Réglage du délai

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès indiqué dans le tableau 11.4.

Tableau 11.4: Critère de succès du logiciel: réglage du délai

Pour chaque limite de temps fixée par le logiciel, au moins l’un des points suivants est vrai:

  • Suppression : l’utilisateur a la possibilité de supprimer la limite de temps avant de la rencontrer ; ou
  • Ajustement : l’utilisateur a la possibilité d’ajuster la limite de temps avant de la rencontrer dans un intervalle d’au moins dix fois la durée paramétrée par défaut ; ou
  • Extension: l’utilisateur est averti avant que la limite de temps expire et il lui est accordé au moins 20 secondes pour étendre cette limite par une action simple (par exemple, « appuyer sur la barre d’espace ») et l’utilisateur a la possibilité d’étendre la limite de temps au moins dix fois.
  • Extension : l’utilisateur est averti avant que la limite de temps n’expire et il lui est accordé au moins 20 secondes pour étendre cette limite par une action simple (par exemple, « appuyer sur la barre d’espace ») et l’utilisateur a la possibilité d’étendre la limite de temps au moins dix fois ; ou
  • L’exception du temps réel : la limite de temps est une partie constitutive d’un événement en temps réel (par exemple, une enchère) et aucune alternative n’est possible ; ou
  • L’exception de la limite essentielle : la limite de temps est essentielleessentielle et l’étendre invaliderait alors l’activité ; ou
  • L’exception des 20 heures : la limite de temps est supérieure à 20 heures.

REMARQUE 1: Ce critère de succès permet de s’assurer que les utilisateurs peuvent accomplir les tâches sans changements inattendus dans le contenu ou le contexte résultant d’une limite de temps. Ce critère de succès doit être considéré conjointement avec le critère de succès 3.2.1 des WCAG 2.1, qui impose des limites aux changements de contenu ou de contexte résultant de l’action des utilisateurs.

REMARQUE 2: ce critère de succès est identique au critère de succès 2.2.1 Réglage du délai des WCAG 2.1, après remplacement de « le contenu » par « logiciel » et l’ajout des mots « des WCAG 2.1 » après les mots « critère de succès » à la note 1 ci-dessus.

C.11.2.2.1 Réglage du délai

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.4.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Échec: L’énoncé testablNon applicable : La condition préalable 1 n’est pas remplie.

11.2.2.2 Mettre en pause, arrêter, masquer

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès indiqué dans le tableau 11.5.

Tableau 11.5: Critère de succès du logiciel: mettre en pause, arrêter, masquer

Pour déplacer, faire clignoter, faire défiler ou mettre à jour automatiquement des informations, tous les éléments suivants sont vrais:

  • Déplacement, clignotement, défilement: pour toute information en mouvement, clignotante ou défilante qui (1) démarre automatiquement, (2) dure plus de cinq secondes et (3) est présentée en parallèle avec d’autres contenus, il existe un mécanisme permettant à l’utilisateur de mettre en pause, d’arrêter ou de masquer l’information à moins que le déplacement, le clignement ou le défilement fasse partie d’une activité où cela est essentiel.
  • Mise à jour automatique: pour toute mise à jour qui (1) démarre automatiquement et (2) est présentée en parallèle avec d’autres contenus, il existe un mécanisme permettant à l’utilisateur de la mettre en pause, de l’arrêter, de la masquer ou de contrôler sa fréquence, sauf si la mise à jour automatique fait partie d’une activité où elle est essentielle.

REMARQUE 1: Pour les exigences relatives au contenu clignotant ou avec flash, se référer à la règle 2.3 des WCAG 2.1.

REMARQUE 2: ce critère de succès s’applique à tout le contenu du logiciel (qu’il existe ou non un autre mode de fonctionnement accessible du logiciel), car toute partie d’un logiciel qui ne satisfait pas à ce critère de succès peut nuire à la capacité de l’utilisateur d’utiliser le logiciel en entier (y compris un élément d’interface utilisateur qui lui permet d’activer le deuxième mode accessible).

REMARQUE 3: Il n’est pas exigé que le contenu mis à jour périodiquement par logiciel ou diffusé en flux à l’agent utilisateur conserve ou présente l’information générée ou reçue entre la mise en pause et la reprise de la présentation, puisque cela peut ne pas être techniquement possible et s’avérer trompeur dans beaucoup de situations.

REMARQUE 4: Une animation survenant dans une phase de pré-chargement ou dans une situation similaire peut être considérée comme essentielle si aucune interaction n’est permise à tous les utilisateurs durant cette phase et si l’absence d’indication de progression est susceptible de perturber les utilisateurs ou de leur faire croire que le contenu est figé ou défectueux.

REMARQUE 5: cela s’applique à tous les contenus. Tout contenu, informatif ou décoratif, qui est mis à jour automatiquement, clignote ou bouge peut créer un obstacle à l’accessibilité.

REMARQUE 6: ce critère de succès est identique au critère de succès 2.2.2 Mettre en pause, arrêter, masquer des WCAG 2.1, après remplacement de « page » et de « page Web » par « logiciel », suppression de « Voir l’exigence de conformité 5: non-ingérence » dans la note 2 du critère de succès, l’ajout des mots « des WCAG 2.1 » à la suite de « règle » à la note 1, la reformulation de la note 2 de façon à éviter le verbe « devoir » et l’ajout de la note 5 ci-dessus.

C.11.2.2.2 Mettre en pause, arrêter, masquer

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.5.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.2.3 Crises et réactions physiques
Clause de la norme EN 301 549Détermination de la conformité

11.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès indiqué dans le tableau 11.6.

Tableau 11.6: Critère de succès du logiciel: Pas plus de trois flashs ou sous le seuil critique

Un logiciel doit être exempt de tout élément qui flashe plus de trois fois dans n’importe quel intervalle d’une seconde ou ce flash doit se situer sous le seuil de flash générique et le seuil de flash rouge.

REMARQUE 1: ce critère de succès s’applique à tout le contenu du logiciel (qu’il existe ou non un autre mode de fonctionnement accessible du logiciel), car toute partie d’un logiciel qui ne satisfait pas à ce critère de succès peut nuire à la capacité de l’utilisateur d’utiliser le logiciel en entier (y compris un élément d’interface utilisateur qui lui permet d’activer le deuxième mode accessible).

REMARQUE 2: ce critère de succès est identique au critère de succès 2.3.1 Pas plus de trois flashs des WCAG 2.1 après remplacement de « pages Web » par « logiciel », de « la page entière » par « le logiciel entier », « la page Web » par « le logiciel », après suppression de « Voir l’exigence de conformité 5: Non-ingérence » et après la reformulation de la note 1 ci-dessus pour éviter le verbe « devoir ».

C.11.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.6.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.2.4 Navigable
Clause de la norme EN 301 549Détermination de la conformité

11.2.4.3 Parcours du focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès indiqué dans le tableau 11.7.

Tableau 11.7: Critère de succès du logiciel: Parcours du focus

Si un logiciel peut être parcourue de façon séquentielle et que les séquences de navigation affectent la signification ou l’action, les éléments reçoivent la du focus dans un ordre qui préserve la signification et l’opérabilité.

REMARQUE: ce critère de succès est identique au critère de succès 2.4.3 Parcours de la cible de saisie des WCAG 2.1 après le remplacement de « page Web » par « logiciel ».

C.11.2.4.3 Parcours du focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.7.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.2.4.4 Fonction du lien (selon le contexte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

C.11.2.4.4 Fonction du lien (selon le contexte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez que le logiciel n’échoue pas au critère de succès 2.4.4 Objectif du lien (selon le contexte) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

11.2.4.6 En-têtes et étiquettes

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

REMARQUE: dans un logiciel, les en-têtes et les étiquettes sont utilisés pour décrire les sections du contenu et les contrôles respectivement. Dans certains cas, il peut être difficile de savoir si un élément de texte statique est un en-tête ou une étiquette. Mais qu’il s’agisse d’une étiquette ou d’un en-tête, l’exigence est la même: s’ils sont présents, ils doivent décrire le sujet ou le but des éléments auxquels ils sont associés.

C.11.2.4.6 En-têtes et étiquettes

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

11.2.4.7 Visibilité du focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.4.7 Visibilité du focus des WCAG 2.1.

C.11.2.4.7 Visibilité du focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 2.4.7 Visibilité de la cible de saisie des WCAG 2.1 des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès critère de succès 2.4.7 Visibilité du focus des WCAG 2.1.

11.2.5 Modalités d’entrée
Clause de la norme EN 301 549Détermination de la conformité

11.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès indiqué dans le tableau 11.8.

Tableau 11.8: Critère de succès du logiciel: Gestes pour le contrôle du pointeur

Toutes les fonctions qui utilisent des mouvements multipoints ou basés sur un tracé pour exécuter une commande peuvent être utilisées avec un seul pointeur sans mouvement basé sur un tracé, à moins qu’un mouvement multipoint ou basé sur un tracé soit essentiel.

REMARQUE 1: cette exigence s’applique au logiciel non Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 2: ce critère de succès est identique au critère de succès 2.5.1 Mouvements du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

C.11.2.5.1 Gestes pour le contrôle du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.8.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.2.5.2 Annulation de l’action du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès indiqué dans le tableau 11.9.

Tableau 11.9: Critère de succès du logiciel: Annulation de l’action du pointeur

Dans le cas des fonctions qui peuvent fonctionner à l’aide d’un seul pointeur, au moins l’un des éléments suivants est vrai:

  • Aucun événement descendant: l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction
  • Abandonner ou Annuler: l’achèvement de la fonction se fait sur l’événement ascendant (up-event) et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion de l’événement: l’événement montant inverse tout résultat de l’événement descendant précédent.
  • Essentiel: terminer la fonction sur inversion de l’événement est essentiel.

REMARQUE 1: les fonctions qui émulent un appui clavier ou un pavé numérique sont considérées comme essentielles.

REMARQUE 2: cette exigence s’applique au logiciel non Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 3: Ce critère de succès est identique au critère de succès 2.5.2 Annulation du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

C.11.2.5.2 Annulation de l’action du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.9.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.2.5.3 Étiquette dans le nom
Clause de la norme EN 301 549Détermination de la conformité

11.2.5.3.1 Étiquette dans le nom (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

C.11.2.5.3.1 Étiquette dans le nom (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

11.2.5.3.2 Étiquette dans le nom (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.3 (Corrélation de sortie sonore).

C.11.2.5.3.2 Étiquette dans le nom (fonction restreinte)

La clause 11.2.5.3.2 a pour seul but d’informer et ne contient aucune exigence en matière de test.

11.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

C.11.2.5.4 Activation par le mouvement

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

11.3 Compréhensible
11.3.1 Lisible
11.3.1.1 Langue du logiciel
Clause de la norme EN 301 549Détermination de la conformité

11.3.1.1.1 Langue du logiciel (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès indiqué dans le tableau 11.10.

Tableau 11.10: Critère de succès du logiciel: langue du logiciel

La langue par défaut du logiciel peut être déterminée par un programme informatique.

REMARQUE 1: lorsque les plateformes logicielles fournissent un paramètre « endroit/langue », les applications qui utilisent ce paramètre et rendent leur interface propre à cet « endroit » ou cette « langue » seraient conformes à ce critère de succès. Les applications qui n’utilisent pas le paramètre « endroit/langue » de la plateforme, mais qui utilisent une méthode d’exposition de la langue humaine du logiciel basée sur l’accessibilité seraient également conformes à ce critère de succès. Les applications mises en œuvre dans des technologies où les technologies d’assistance ne peuvent pas déterminer la langue humaine et ne prennent pas en charge le paramètre « endroit/langue » de la plateforme peuvent ne pas être en mesure de satisfaire à ce critère de succès pour cet endroit ou cette langue.

REMARQUE 2: ce critère de succès est identique au critère de succès 3.1.1 Langue de la page des WCAG 2.1 après remplacement de « pages Web » par « logiciel » et après l’ajout de la note 1 ci-dessus.

C.11.3.1.1.1 Langue du logiciel (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.10.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.3.1.1.2 Langue du logiciel (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit l’exigence 5.1.3.14 (Langues parlées).

C.11.3.1.1.2 Langue du logiciel (fonction restreinte)

Type d’évaluation

Examen

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

4. La sortie vocale n’est pas utilisée pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement.

5.Le contenu n’est pas généré à l’extérieur et est sous le contrôle du fournisseur de TIC.

6. Les langues affichées peuvent être sélectionnées à l’aide d’un accès non visuel.

7. L’utilisateur n’a pas sélectionné une langue vocale différente de la langue du contenu affiché.

Procédure

1. Vérifier que la sortie vocale est dans la même langue humaine que le contenu affiché.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2, 3, 4, 5, 6 ou 7 n’est pas remplie.

11.3.2 Prévisible
Clause de la norme EN 301 549Détermination de la conformité

11.3.2.1 Au focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au Critère de succès 3.2.1 Au focus des WCAG 2.1.

REMARQUE: Certains documents composés et leurs agents utilisateurs sont conçus pour offrir des fonctions d’affichage et de modification très différentes selon la partie du document composé où les interactions ont lieu (par exemple, une présentation qui contient une feuille de calcul intégrée, dans laquelle les menus et les barres d’outils de l’agent utilisateur changent selon que l’utilisateur interagit avec le contenu de la présentation ou celui de la feuille de calcul intégrée). Si l’utilisateur utilise un mécanisme autre que celui de mettre la du focus sur la partie du document composite avec laquelle il veut interagir (p. ex. par un choix de menu ou un mouvement spécial de clavier), tout changement de contexte qui en résulterait ne serait pas soumis à ce critère de succès parce qu’il n’a pas été causé par un déplacement du focus.

C.11.3.2.1 Au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez si le logiciel n’échoue pas au Critère de succès 3.2.1 Au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.1 Au focus des WCAG 2.1.

11.3.2.2 À la saisie

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 3.2.2 À la saisie des WCAG 2.1.

C.11.3.2.2 À la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez que le logiciel n’échoue pas au critère de succès 3.2.2 À la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.2 À la saisie des WCAG 2.1.

11.3.3 Assistance à la saisie
11.3.3.1 Identification des erreurs
Clause de la norme EN 301 549Détermination de la conformité

11.3.3.1.1 Identification d’erreur (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

C.11.3.3.1.1 Identification d’erreur (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifiez que la page Web n’échoue pas au critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

11.3.3.1.2 Identification d’erreur (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit l’exigence 5.1.3.15 (Identification non visuelle des erreurs).

C.11.3.3.1.2 Identification d’erreur (fonction restreinte)

Type d’évaluation

Examen

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

4. Une erreur de saisie est automatiquement détectée.

Procédure

1. Vérifiez que la sortie vocale identifie l’élément qui est en erreur.

2. Vérifiez que la sortie vocale décrit l’élément qui est en erreur.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1, 2, 3 ou 4 n’est pas remplie.

11.3.3.2 Étiquettes ou instructions

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

C.11.3.3.2 Étiquettes ou instructions

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez que le logiciel n’échoue pas au critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

11.3.3.3 Suggestion après une erreur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

C.11.3.3.3 Suggestion après une erreur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez que le logiciel n’échoue pas au critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

11.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès indiqué dans le tableau 11.11.

Tableau 11.11: Critère de succès du logiciel: Prévention des erreurs (juridiques, financières, de données)

Pour les logiciels qui donnent lieu à des engagements juridiques ou à des transactions financières de la part de l’utilisateur qui soit modifient ou effacent des données contrôlables par l’utilisateur dans des systèmes de stockages de données, soit enregistrent les réponses de l’utilisateur à un test ou un examen, au moins l’une des conditions suivantes est vraie:

1. Réversible: les actions d’envoi sont réversibles

2. Vérifiée: les données saisies par l’utilisateur sont vérifiées au niveau des erreurs de saisie et la possibilité est donnée à l’utilisateur de les corriger.

3. Confirmée: un mécanisme est disponible pour revoir, confirmer et corriger les informations avant leur soumission finale.

REMARQUE: Ce critère de succès est identique au critère de succès 3.3.4 Prévention des erreurs (juridique, financier, de données) des WCAG 2.1remplaçant « pages Web » par « logiciel ».

C.11.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.4 Robuste
11.4.1 Compatible
11.4.1.1 Analyse syntaxique
Clause de la norme EN 301 549Détermination de la conformité

11.4.1.1.1 Analyse syntaxique (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance, elle remplit le critère de succès indiqué dans le tableau 11.12.

Tableau 11.12: Critère de succès du logiciel: Analyse syntaxique

Pour les logiciels qui utilisent des langages de balisage, de manière à ce que le balisage soit exposé et disponible séparément aux technologies d’assistance et aux fonctions d’accessibilité du logiciel ou à un agent utilisateur sélectionnable par l’utilisateur, les éléments ont des balises de début et de fin complètes, les éléments sont imbriqués selon leurs spécifications, les éléments ne contiennent pas d’attributs en double et tout identifiant est unique, sauf lorsque les spécifications permettent ces fonctions.

REMARQUE 1: Les balises de début et de fin auxquelles il manque un caractère critique, comme une parenthèse fermante ou un guillemet de valeur d’attribut mal appropriée, sont considérées incomplètes.

REMARQUE 2: Le balisage n’est pas toujours mis à la disposition des technologies d’assistance ou des agents utilisateurs sélectionnables par l’utilisateur tels que les navigateurs. Dans de tels cas, la conformité à cette disposition n’aurait aucune incidence sur l’accessibilité, comme c’est le cas pour le contenu Web lorsqu’il est exposé.

REMARQUE 3: Les exemples de balisage qui sont exposés séparément et disponibles pour les technologies d’assistance et les agents utilisateurs comprennent, sans s’y limiter: les documents encodés en HTML, ODF et OOXML. Dans ces exemples, le balisage peut être entièrement analysé de deux façons: (a) par des technologies d’assistance qui peuvent ouvrir directement le document, (b) par des technologies d’assistance utilisant des API DOM d’agents utilisateurs pour ces formats de document.

REMARQUE 4: Les exemples de balisage utilisé à l’interne pour la persistance de l’interface utilisateur du logiciel qui ne sont jamais exposés à la technologie d’assistance comprennent, sans s’y limiter: XUL, GladeXML et FXML. Dans ces exemples, la technologie d’assistance n’interagit qu’avec l’interface utilisateur du logiciel généré.

REMARQUE 5: Ce critère de succès est identique au critère de succès 4.1.1 Analyse syntaxique des WCAG 2.1 en remplaçant « Dans le contenu mis en œuvre en utilisant des langages de balisage » par « Pour les logiciels qui utilisent des langages de balisage, de manière à ce que le balisage soit exposé et disponible séparément aux technologies d’assistance et aux fonctions d’accessibilité du logiciel ou à un agent utilisateur sélectionnable par l’utilisateur » avec l’ajout des notes 2, 3 et 4 ci-dessus.

C.11.4.1.1.1 Analyse syntaxique (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifiez que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.12.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.4.1.1.2 Analyse syntaxique (fonction restreinte)

Sans objet.

REMARQUE : Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui ne prend pas en charge l’accès aux technologies d’assistance, elle ne remplit pas le critère de succès Analyse syntaxique indiqué dans le tableau 11.10, parce que le but de ce critère de succès est d’assurer la cohérence afin que différents agents utilisateurs ou technologies d’assistance donnent le même résultat.

C.11.4.1.1.2 Analyse syntaxique (fonction restreinte)

La clause 11.4.1.1.2 ne contient aucune exigence en matière de test.

11.4.1.2 Nom, rôle et valeur
Clause de la norme EN 301 549Détermination de la conformité

11.4.1.2.1 Nom, rôle et valeur (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance, elle remplit le critère de succès indiqué dans le tableau 11.13.

Tableau 11.13: Critère de succès du logiciel: Nom, rôle, valeur

Pour tout composant d’interface utilisateur (comprenant, mais n’étant pas limité aux éléments de formulaire, liens et composants générés par des scriptes), le nom et le rôle peuvent être déterminés par un programme informatique ; les états, les propriétés et les valeurs qui peuvent être paramétrés par l’utilisateur peuvent être définis par un programme informatique ; et la notification des changements de ces éléments est disponible aux agents utilisateurs, incluant les technologies d’assistance.

REMARQUE 1: Ce critère de succès s’adresse principalement aux développeurs de logiciels qui développent ou utilisent des composants d’interface utilisateur personnalisés. Les composants d’interface utilisateur standard de la plupart des plateformes qui prennent en charge l’accessibilité répondent déjà à ce critère de succès lorsqu’ils sont utilisés conformément aux spécifications.

REMARQUE 2: Pour se conformer à ce critère de succès, il est généralement préférable que les interfaces utilisateur des logiciels utilisent les services d’accessibilité fournis par les logiciels de plateforme. Ces services d’accessibilité permettent l’interopérabilité entre les interfaces utilisateur des logiciels et les technologies d’assistance et les caractéristiques d’accessibilité des logiciels de manière normalisée. La plupart des services d’accessibilité de plateforme vont au-delà de l’exposition programmatique du nom et du rôle, et de l’établissement programmatique des états, des propriétés et des valeurs (et de leur notification), et spécifient des informations supplémentaires qui pourraient ou doivent être exposées et/ou établies (p. ex. une liste des actions disponibles pour un composant d’interface utilisateur donné, et un moyen pour exécuter par un programme informatique une des actions indiquées).

REMARQUE 3: Ce critère de succès est identique au critère de succès 4.1.2 Nom, rôle et valeur des WCAG 2.1 remplaçant la note initiale des WCAG 2.1 par la suivante: « Ce critère de succès s’adresse principalement aux développeurs de logiciels qui développent ou utilisent des composants d’interface utilisateur personnalisés. Les composants d’interface utilisateur standard de la plupart des plateformes qui prennent en charge l’accessibilité répondent déjà à ce critère de succès lorsqu’ils sont utilisés conformément aux spécifications » et l’ajout de la note 2 ci-dessus.

C.11.4.1.2.1 Nom, rôle et valeur (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifiez que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.13.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.4.1.2.2 Nom, rôle et valeur (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui ne prend pas en charge l’accès aux technologies d’assistance, elle ne remplit pas le critère de succès « Nom, rôle, valeur » du tableau 11.11, parce que ce critère de succès exige des informations sous une forme pouvant être déterminée par le programme.

C.11.4.1.2.2 Nom, rôle et valeur (fonction restreinte)

La clause 11.4.1.2.2 ne contient aucune exigence en matière de test.

La clause 11.4.1.3.2 ne contient pas d’exigences testables.

11.4.1.3 Messages d’état
Clause de la norme EN 301 549Détermination de la conformité

11.4.1.3.1 Messages d’état (fonction non restreinte)

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 4.1.3 Messages d’état des WCAG 2.1.

C.11.4.1.3.1 Messages d’état (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 4.1.3 Messages d’état des WCAG 2.1.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 4.1.3 Messages d’état des WCAG 2.1.

11.4.1.3.2 Messages d’état (fonction restreinte)

Sans objet.

C.11.4.1.3.2 Messages d’état (fonction restreinte)
11.5 Interopérabilité avec la technologie d’assistance
Clause de la norme EN 301 549Détermination de la conformité

11.5.1 Fonction restreinte

Lorsque la fonction restreinte du logiciel est conforme à La clause 5.1 (Fonction restreinte), il n’est pas nécessaire de se conformer aux clauses 11.5.2 à 11.5.2.17.

C.11.5.1 Fonction restreinte

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel a une fonction restreinte.

Procédure

1. Vérifiez que la fonction restreinte est conforme à La clause 5.1.

Résultat

Si l’énoncé testable no 1 est vrai, le logiciel n’est pas tenu de se conformer aux clauses 11.5.2 à 11.5.17.

Si l’énoncé testable no 1 est faux, le logiciel est tenu de se conformer aux clauses 11.5.2 à 11.5.17.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2 Services d’accessibilité
Clause de la norme EN 301 549Détermination de la conformité

11.5.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur.

Les logiciels de plateforme fournissent un ensemble de services de plateforme documentés qui permettent aux logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme d’interagir avec la technologie d’assistance.

Le logiciel de la plateforme doit prendre en charge les exigences 11.5.2.5 à 11.5.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.5.2.14 (Modification des attributs de du focus et de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1: Elles définissent la fonctionnalité minimale des logiciels fournissant des interfaces utilisateur lors de l’utilisation des services de la plateforme.

REMARQUE 2: Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 3: Les services d’interface utilisateur qui fournissent par défaut un soutien à l’accessibilité sont considérés comme faisant partie des services fournis pour se conformer à cette clause (par exemple, le service de création d’un nouvel élément d’interface utilisateur fournit un rôle, un état, une limite, un nom et une description).

REMARQUE 4: Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

REMARQUE 5: Dans des environnements de un programme informatique particuliers, les attributs techniques associés aux propriétés de l’interface utilisateur décrites dans les clauses 11.5.2.5 à 11.5.2.17 peuvent avoir des noms différents de ceux utilisés dans ces clauses.

C.11.5.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur.

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel de plateforme.

Procédure

1. Vérifiez que la documentation du logiciel de plateforme comprend des informations sur les services de la plateforme qui peuvent être utilisés par un logiciel qui fournit une interface utilisateur pour interagir avec la technologie d’assistance.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Le logiciel de la plateforme doit fournir un ensemble de services d’accessibilité documentés qui permettent à la technologie d’assistance d’interagir avec les logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme.

Le logiciel de plateforme doit prendre en charge les exigences 11.5.2.5 à 11.5.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.5.2.14 (Modification des attributs de du focus et de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1: Celles-ci définissent les fonctions minimales disponibles pour les technologies d’assistance lors de l’utilisation des services de plateforme.

REMARQUE 2: La définition de plateforme dans la clause 3.1 s’applique aux logiciels qui fournissent des services à d’autres logiciels, y compris, mais sans s’y limiter, les systèmes d’exploitation, les navigateurs Web et les machines virtuelles.

REMARQUE 3: Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 4: Généralement, ces services appartiennent au même ensemble de services qui sont décrits dans La clause 11.5.2.1.

REMARQUE 5: Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

C.11.5.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel de plateforme.

Procédure

1. Vérifiez que la documentation du logiciel de plateforme comprend des informations sur les services d’accessibilité de la plateforme qui permettent à la technologie d’assistance d’interagir avec le logiciel qui fournit une interface utilisateur fonctionnant sur le logiciel de plateforme.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.3 Utilisation des services d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, il utilise les services d’accessibilité de plateforme documentés applicables. Si les services d’accessibilité de la plateforme documentés ne permettent pas au logiciel de satisfaire aux exigences applicables des clauses 11.5.2.5 à 11.5.2.17, le logiciel qui fournit une interface utilisateur doit utiliser d’autres services documentés pour interagir avec la technologie d’assistance.

REMARQUE: L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.5.2.1 et 11.5.2.2.

Il est préférable de développer des logiciels à l’aide de boîtes à outils qui mettent en œuvre automatiquement les services d’accessibilité de la plateforme sous-jacente.

C.11.5.2.3 Utilisation des services d’accessibilité

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

Procédure

1. Vérifiez que le logiciel utilise les services d’accessibilité de plateforme documentés applicables.

2. Vérifiez que le logiciel peut répondre aux exigences applicables de 11.5.2.5 à 11.5.2.17 tout en utilisant les services d’accessibilité documentés de la plateforme.

3. Vérifiez que le logiciel peut répondre aux exigences de 11.5.2.5 à 11.5.2.17 tout en utilisant les services d’accessibilité documentés de la plateforme et autres services documentés.

Résultat

Réussite: L’énoncé testable no 1 est vrai et l’énoncé testable no 2 ou 3 est vrai.

Échec: Les énoncés testables no 1 ou 3 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.4 Technologie d’assistance

Lorsque la TIC est une technologie d’assistance, elle doit utiliser les services d’accessibilité de la plateforme documentés.

REMARQUE: L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.5.2.1 et 11.5.2.2.

REMARQUE 2: Les technologies d’assistance peuvent également utiliser d’autres services d’accessibilité documentés.

C.11.5.2.4 Technologie d’assistance

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une technologie d’assistance.

Procédure

1. Vérifiez que la technologie d’assistance utilise les services d’accessibilité documentés de la plateforme.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.5 Renseignements sur les objets

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre au rôle, aux états, à la limite, au nom et à la description des éléments d’interface utilisateur d’être déterminés par un programme informatique au moyen de technologies d’assistance.

C.11.5.2.5 Renseignements sur les objets

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

Procédure

1. Vérifiez que le rôle de l’élément d’interface utilisateur peut être déterminé par un programme informatique à l’aide de technologies d’assistance.

2. Vérifiez que l’état ou les états l’élément d’interface utilisateur peuvent être déterminés par un programme informatique à l’aide de technologies d’assistance.

3. Vérifiez que la limite de l’élément d’interface utilisateur peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

4. Vérifiez que le nom de l’élément d’interface utilisateur peut être déterminé par un programme informatique à l’aide de technologies d’assistance.

5. Vérifiez que la description de l’élément d’interface utilisateur peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 1, 2, 3, 4 et 5 sont vrais.

Échec: Les énoncés testables nos 1, 2, 3, 4 ou 5 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.6 Ligne, colonne et en-têtes

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la ligne et la colonne de chaque cellule d’un tableau de données, y compris les en-têtes de la ligne et de la colonne, le cas échéant, déterminables par un programme informatique au moyen de technologies d’assistance.

C.11.5.2.6 Ligne, colonne et en-têtes

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il y a des tableaux de données dans l’interface utilisateur.

Procédure

1. Sélectionnez une table de données dans laquelle les tests doivent être effectués.

2. Vérifiez que la rangée de chaque cellule peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

3. Vérifiez que la colonne de chaque cellule peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

4. Vérifiez que l’en-tête de ligne de chaque cellule, si elle existe, peut être déterminé par un programme informatique à l’aide de technologies d’assistance.

5. Vérifiez que l’en-tête de la colonne de chaque cellule, si elle existe, peut être déterminé par un programme informatique à l’aide de technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 2, 3, 4 et 5 sont vrais.

Échec: Les énoncés testables nos 2, 3, 4 ou 5 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.7 Valeurs

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la valeur actuelle d’un élément d’interface utilisateur et toute valeur minimale ou maximale de la plage, si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, pouvant être déterminées par un programme informatique par des technologies d’assistance.

C.11.5.2.7 Valeurs

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Certains éléments d’interface utilisateur peuvent avoir des valeurs.

Procédure

1. Sélectionnez un élément d’interface utilisateur qui peut avoir une valeur.

2. Vérifiez que la valeur actuelle peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

3. Si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, vérifiez que la valeur minimale peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

4. Si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, vérifiez que la valeur maximale peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 2, 3 et 4 sont vrais.

Échec: Les énoncés testables nos 2, 3, ou 4 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.8 Liens entre les étiquettes

Lorsque le logiciel fournit une interface utilisateur, il expose le lien qu’entretient un élément d’interface utilisateur en tant qu’étiquette pour un autre élément ou en tant qu’élément étiqueté par un autre élément, en utilisant les services décrits dans la clause 11.5.2.3, de sorte que ces informations puissent être déterminées par un programme informatique par des technologies d’assistance.

C.11.5.2.8 Liens entre les étiquettes

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il existe des éléments d’interface utilisateur qui sont des étiquettes d’autres éléments d’interface utilisateur.

Procédure

1. Obtenir les informations de chaque élément d’interface utilisateur.

2. Vérifiez que les informations de l’élément d’interface utilisateur incluent la relation avec l’élément d’interface utilisateur qui est son étiquette, si l’élément d’interface utilisateur actuel a une étiquette, et que cette relation peut être déterminée par un programme informatique par des technologies d’assistance.

3. Vérifiez que les informations de l’élément d’interface utilisateur incluent la relation avec l’élément d’interface utilisateur qu’il étiquette, si l’élément d’interface utilisateur actuel est une étiquette, et que cette relation peut être déterminée par un programme informatique par des technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 2 ou 3 sont vrais

Échec: Les énoncés testables nos 2 et 3 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.9 Relations parents-enfants

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, la relation entre un élément d’interface utilisateur et tout élément parent ou enfant.

C.11.5.2.9 Relations parents-enfants

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il existe des éléments d’interface utilisateur qui sont les parents d’autres éléments d’interface utilisateur dans une structure hiérarchique.

Procédure

1. Pour les éléments d’interface utilisateur qui ont un parent, vérifiez que les informations de l’élément d’interface utilisateur incluent la relation avec l’élément d’interface utilisateur qui est son parent.

2. Vérifiez que les informations des éléments d’interface utilisateur qui sont les parents de l’élément d’interface utilisateur sélectionné dans l’énoncé testable no 1 incluent la relation avec les éléments d’interface utilisateur qui sont ses enfants, et que cette relation peut être déterminée par un programme informatique par des technologies d’assistance.

3. Pour les éléments d’interface utilisateur qui sont le parent d’autres éléments d’interface utilisateur, vérifiez que les informations de l’élément d’interface utilisateur incluent la relation avec les éléments d’interface utilisateur qui sont ses enfants, et que cette relation peut être déterminée par un programme informatique par des technologies d’assistance.

4. Vérifiez que les informations des éléments d’interface utilisateur qui sont les enfants de l’élément d’interface utilisateur sélectionné dans l’énoncé testable no 3 incluent la relation avec les éléments d’interface utilisateur qui sont ses parents, et que cette relation peut être déterminée par un programme informatique par des technologies d’assistance.

Résultat

Réussite: L’énoncé testable no 1 ou 2 est vrai et l’énoncé testable no 3 ou 4 est vrai.

Échec: Les énoncés testables nos 1 et 2 sont faux ou les énoncés testables nos 3 et 4 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

REMARQUE: Pour cette exigence, il suffit que l’une des deux directions d’une relation parent-enfant puisse être déterminée par le programme. C’est la raison pour laquelle les vérifications de l’exigence sont effectuées par paires et l’exigence est satisfaite si un membre de chaque paire est vrai.

11.5.2.10 Texte

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, le contenu textuel, les attributs textuels et la limite du texte rendu à l’écran.

C.11.5.2.10 Texte

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il y a du texte rendu à l’écran.

Procédure

1. Pour les exemples de texte rendu à l’écran, vérifiez que l’information du texte inclut son contenu textuel et que cette information peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

2. Pour les exemples de texte rendu à l’écran, vérifiez que l’information du texte inclut ses attributs et que cette information peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

3. Pour les exemples de texte rendu à l’écran, vérifiez que l’information du texte inclut sa limite et que cette information peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 1, 2 et 3 sont vrais

Échec: Les énoncés testables no 1, 2 ou 3 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.11 Liste des actions disponibles

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, une liste des actions disponibles qui peuvent être exécutées sur un élément d’interface utilisateur.

C.11.5.2.11 Liste des actions disponibles

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Certains éléments d’interface utilisateur ont des actions qui peuvent être exécutées par l’utilisateur.

Procédure

1. Vérifiez que les informations de l’élément d’interface utilisateur contiennent la liste des actions qui peuvent être exécutées.

2. Vérifiez que cette liste peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.12 Exécution des actions disponibles

Lorsque les exigences de sécurité le permettent, le logiciel qui fournit une interface utilisateur doit, en utilisant les services décrits à la clause 11.5.2.3, permettre l’exécution programmatique des actions exposées, au moyen des technologies d’assistance, conformément à la clause 11.5.2.11.

REMARQUE 1: Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2: Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

C.11.5.2.12 Exécution des actions disponibles

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Certains éléments d’interface utilisateur offrent des actions qui peuvent être exécutées par l’utilisateur.

3. Les exigences en matière de sécurité permettent à la technologie d’assistance d’exécuter par un programme informatique les actions de l’utilisateur.

Procédure

1. Vérifiez que les informations de l’élément d’interface utilisateur incluent la liste des actions qui peuvent être exécutées par les technologies d’assistance selon la clause 11.5.2.11.

2. Vérifiez que toutes les actions de la liste peuvent être exécutées avec succès par des technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.5.2.13 Suivi des attributs de du focus et de sélection

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre l’information et les mécanismes nécessaires au suivi de la cible de saisie, du point d’insertion du texte et des attributs de sélection des éléments d’interface utilisateur, déterminables par un programme informatiques par les technologies d’assistance.

C.11.5.2.13 Suivi des attributs de du focus et de sélection

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Certains éléments d’interface utilisateur permettent la modification de textes.

Procédure

1. Vérifiez que les informations de l’élément d’interface utilisateur comprennent des mécanismes de suivi de la du focus, du point d’insertion du texte et des attributs de sélection.

2. Vérifiez que cette information peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

3. Activez ces mécanismes de suivi.

4. En tant qu’utilisateur, utilisez la fonctionnalité d’édition de texte dans le produit logiciel évalué.

5. Vérifiez que le suivi de la du focus, du point d’insertion de texte et des attributs de sélection fonctionne.

Résultat

Réussite: Les énoncés testables nos 2 et 5 sont vrais.

Échec: Les énoncés testables no 1 ou 5 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.14 Modification des attributs de du focus et de sélection

Lorsque les exigences de sécurité le permettent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique le foyer, le point d’insertion de texte et les attributs de sélection des éléments d’interface utilisateur où l’utilisateur peut modifier ces éléments.

REMARQUE 1: Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2: Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

C.11.5.2.14 Modification des attributs de du focus et de sélection

Type d’évaluation

Examen

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Certains éléments d’interface utilisateur peuvent recevoir une du focus ou permettre l’édition de texte.

3. Les exigences de sécurité permettent au logiciel de plateforme de modifier par un programme informatique la du focus, le point d’insertion du texte et les attributs de sélection des éléments d’interface utilisateur.

Procédure

1. Pour les éléments d’interface utilisateur qui peuvent recevoir la du focus et où la cible de saisie peut être modifiée par un utilisateur sans l’utilisation d’une technologie d’assistance, vérifier que la du focus peut être modifiée par un programme informatique par des technologies d’assistance.

2. Pour les éléments d’interface utilisateur qui permettent à un utilisateur de modifier du texte sans l’aide d’une technologie d’assistance, vérifier que la position du point d’insertion du texte peut être modifiée par un programme informatique à l’aide de technologies d’assistance.

3. Pour les éléments d’interface utilisateur qui permettent l’édition de texte, vérifiez que les attributs de sélection peuvent être modifiés par un programme informatique par des technologies d’assistance, dans les cas où ils peuvent être modifiés par l’utilisateur sans l’aide de technologies d’assistance.

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: N’importe quel énoncé testable est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.5.2.15 Avis de modification

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, aviser les technologies d’assistance des changements apportés aux attributs des éléments d’interface utilisateur pouvant être déterminés par un programme informatique qui sont mentionnés dans les exigences 11.5.2.5 à 11.5.2.11 et 11.5.2.13.

C.11.5.2.15 Avis de modification

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

Procédure

1. Activer les avis de modification dans les éléments d’interface utilisateur.

2. Vérifier que les avis de modification des renseignements sur les objets (rôle, état, limite, nom et description) sont envoyés aux technologies d’assistance, si ces renseignements changent dans l’interface utilisateur du logiciel.

3. Vérifier que les avis de modification des lignes, colonnes et en-têtes des tableaux de données sont envoyés aux technologies d’assistance, si ces renseignements changent dans le logiciel.

4. Vérifier que des avis de modification de valeurs (valeur actuelle, valeur minimale et valeur maximale) sont envoyés, si ces renseignements changent dans le logiciel.

5. Vérifier que des avis de modification des liens entre les étiquettes sont envoyés aux technologies d’assistance, si ces renseignements changent dans le logiciel.

6. Vérifier que des avis de modification des relations parent-enfant sont envoyés aux technologies d’assistance, si ces informations changent dans le logiciel.

7. Vérifier que des avis de modification du texte (contenu ou attributs du texte et limite du texte rendu à l’écran) sont envoyés aux technologies d’assistance, si ces renseignements changent dans le logiciel.

8. Vérifier que des avis de modifications apportées à liste des actions disponibles sont envoyés aux technologies d’assistance, si ces renseignements changent dans le logiciel.

9. Vérifier que des avis de modification de la du focus, du point d’insertion du texte et des attributs de sélection sont envoyés aux technologies d’assistance, si ces renseignements changent dans le logiciel.

Résultat

Réussite: les énoncés testables no 2, 3, 4, 5, 6, 7, 8 et 9 sont vrais

Échec: les énoncés testables no 2, 3, 4, 5, 6, 7, 8 ou 9 sont faux

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.16 Modifications d’états ou de propriétés

Lorsque les exigences de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique les états et propriétés des éléments d’interface utilisateur grâce auxquels l’utilisateur peut modifier ces articles.

REMARQUE 1: Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2: Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

C.11.5.2.16 Modifications d’états ou de propriétés

Type d’évaluation

Examen

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il existe des éléments d’interface utilisateur dont l’état ou les propriétés peuvent être modifiés par un utilisateur sans l’aide d’une technologie d’assistance.

3. Les exigences de sécurité permettent à la technologie d’assistance de modifier par un programme informatique les états et les propriétés des éléments d’interface utilisateur.

Procédure

1. Vérifier que l’état des éléments d’interface utilisateur, dont l’état peut être changé par un utilisateur sans l’aide d’une technologie d’assistance, est susceptible d’être modifié par un programme informatique par des technologies d’assistance.

2. Vérifier que les propriétés des éléments d’interface utilisateur, dont les propriétés peuvent être modifiées par un utilisateur sans l’utilisation de technologies d’assistance, sont susceptibles d’être changées par un programme informatique par des technologies d’assistance.

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: N’importe quel énoncé testable est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.5.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à La clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recours aux technologies d’assistance.

REMARQUE 1: Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2: Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

C.11.5.2.17 Modifications des valeurs et du texte

Type d’évaluation

Examen

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il existe des éléments d’interface utilisateur dont les valeurs ou le texte peuvent être modifiés par un utilisateur sans l’aide d’une technologie d’assistance.

3. Les exigences de sécurité permettent à la technologie d’assistance de modifier par un programme informatique les valeurs et le texte des éléments d’interface utilisateur.

Procédure

1. Vérifier que les valeurs des éléments d’interface utilisateur, dont les valeurs peuvent être modifiées par un utilisateur sans l’aide d’une technologie d’assistance, peuvent être changées par des technologies d’assistance utilisant les méthodes de saisie de la plateforme.

2. Vérifier que le texte des éléments d’interface utilisateur, dont le texte peut être modifié par un utilisateur sans l’aide d’une technologie d’assistance, peut être changé par des technologies d’assistance utilisant les méthodes de saisie de la plateforme.

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: N’importe quel énoncé testable est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.6 Utilisation documentée de l’accessibilité
Clause de la norme EN 301 549Détermination de la conformité

11.6.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Lorsque le logiciel est une plateforme, il doit offrir des modes de fonctionnement suffisants permettant à l’utilisateur de contrôler les caractéristiques d’accessibilité de la plateforme documentées comme étant destinées aux utilisateurs.

C.11.6.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Type d’évaluation

Examen

Conditions préalables

1. Certaines fonctions de la plateforme sont définies dans la documentation de celle-ci comme étant des caractéristiques d’accessibilité destinées aux utilisateurs.

Procédure

1. Vérifier qu’il existe suffisamment de modes de fonctionnement pour permettre à l’utilisateur de contrôler les fonctions de la plateforme, qui sont définies dans la documentation de celle-ci comme étant des caractéristiques d’accessibilité destinées aux utilisateurs.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.6.2 Aucune perturbation des caractéristiques d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, elle ne doit pas perturber les caractéristiques d’accessibilité documentées qui sont définies dans la documentation de la plateforme, sauf si l’utilisateur en fait la demande pendant le fonctionnement du logiciel.

C.11.6.2 Aucune perturbation des caractéristiques d’accessibilité

Type d’évaluation

Examen

Conditions préalables

1. Certaines fonctions de la plateforme sont définies dans la documentation de celle-ci comme étant des caractéristiques d’accessibilité.

Procédure

1. Vérifier si un logiciel qui fournit une interface utilisateur perturbe le fonctionnement normal des caractéristiques d’accessibilité de la plateforme.

2. Vérifier si la perturbation a été spécifiquement demandée ou confirmée par l’utilisateur.

Résultat

Réussite: L’énoncé testable no 1 est faux ou les deux énoncés sont vrais.

Échec: L’énoncé testable no 1 est vrai et l’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.7 Préférences de l’utilisateur

Lorsque le logiciel n’est pas conçu pour être isolé de sa plateforme et qu’il fournit une interface utilisateur, cette interface utilisateur doit respecter les valeurs des préférences de l’utilisateur pour les réglages de la plateforme en ce qui concerne les unités de mesure, la couleur, le contraste, le type et la taille de police et le curseur du focus, sauf s’ils sont surclassés par l’utilisateur.

REMARQUE 1: Les logiciels isolés de leur plateforme sous-jacente n’ont pas accès aux paramètres de l’utilisateur de la plateforme et ne peuvent donc pas respecter cette clause.

REMARQUE 2 : Pour le contenu Web, la plateforme sous-jacente est l’agent utilisateur.

REMARQUE 3 : Cela n’empêche pas le logiciel d’avoir des valeurs supplémentaires pour un paramètre, tant qu’il existe un mode dans lequel l’application suivra les paramètres du système, même s’ils sont plus restreints.

C.11.7 Préférences de l’utilisateur

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel est un logiciel qui fournit une interface utilisateur.

Procédure

1. Vérifier si le logiciel offre suffisamment de modes de fonctionnement se servant des préférences de l’utilisateur pour les paramètres de la plateforme en ce qui concerne la couleur, le contraste, le type et la taille de police ainsi que le curseur de du focus.

2. Vérifier que la documentation du logiciel indique que le logiciel est conçu pour être isolé de sa plateforme sous-jacente.

Résultat

Réussite: L’énoncé testable no 1 est vrai ou l’énoncé testable no 1 est faux et l’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 1 est faux et l’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.8 Outils-auteurs
Clause de la norme EN 301 549Détermination de la conformité

11.8.1 Technologie du contenu

Les outils-auteurs doivent être conformes aux clauses 11.8.2 à 11.8.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

C.11.8.1 Technologie du contenu

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel est un outil-auteur.

2. Le format de l’extrant de l’outil-auteur prend en charge les renseignements nécessaires à l’accessibilité.

Procédure

1. Vérifier si l’outil-auteur est conforme aux clauses 11.8.2 à 11.8.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

REMARQUE: Lorsque le format des extrants de l’outil-auteur ne prend pas en charge certains types de renseignements requis pour l’accessibilité, il n’est pas nécessaire de respecter les exigences relatives à ce type de renseignements.

11.8.2 Création de contenu accessible

Les outils-auteurs doivent permettre et orienter la production de contenu conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

REMARQUE: Les outils-auteurs peuvent s’appuyer sur des outils supplémentaires lorsqu’il n’est pas possible de respecter des exigences spécifiques avec un seul outil. Par exemple, un outil de montage vidéo peut permettre la création de fichiers vidéo aux fins de diffusion via la télévision et le Web, mais la création de fichiers de sous-titres pour des formats multiples peut être assurée par un outil différent.

C.11.8.2 Création de contenu accessible

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel est un outil-auteur.

Procédure

1. Vérifier si l’outil-auteur possède des caractéristiques qui permettent et orientent la production conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web).

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.8.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Lorsque l’outil-auteur fournit des transformations de restructuration ou de recodage, les renseignements sur l’accessibilité doivent alors être préservés dans l’extrant s’il existe des mécanismes équivalents dans la technologie du contenu de l’extrant.

REMARQUE 1: Les transformations de restructuration sont des transformations dans le cadre desquelles la technologie du contenu reste identique, mais les caractéristiques structurelles du contenu sont modifiées (par exemple, linéarisation des tableaux, division d’un document en pages).

REMARQUE 2: Les transformations de recodage sont des transformations dans le cadre desquelles la technologie utilisée pour coder le contenu est modifiée.

C.11.8.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel est un outil-auteur.

2. L’outil-auteur fournit des transformations de restructuration ou de recodage.

Procédure

1. Pour une transformation de restructuration, vérifier si les renseignements d’accessibilité sont préservés dans l’extrant.

2. Pour une transformation de restructuration, vérifier si la technologie du contenu prend en charge les renseignements d’accessibilité dans la forme restructurée de l’information.

3. Pour une transformation de recodage, vérifier si les renseignements d’accessibilité sont préservés dans l’extrant.

4. Pour une transformation de recodage, vérifier si les renseignements d’accessibilité sont pris en charge par la technologie de l’extrant recodé.

Résultat

Réussite: L’énoncé testable no 1 est vrai ou les énoncés testables no 1 et 2 sont faux ou l’énoncé testable no 3 est vrai ou les énoncés testables no 3 et 4 sont faux.

Échec: L’énoncé testable no 1 est faux et l’énoncé testable no 2 est vrai.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.8.4 Aide à la réparation

Si la fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, alors l’outil-auteur doit formuler des suggestions en matière de réparation.

REMARQUE: Cela n’exclut pas les réparations automatisées ou semi-automatisées qui sont possibles (et recommandées) pour de nombreux types de problèmes d’accessibilité du contenu.

C.11.8.4 Aide à la réparation

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel est un outil-auteur.

2. La fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

Procédure

1. L’outil-auteur formule des suggestions en matière de réparation lorsque le contenu fournit des suggestions de réparation lorsque le contenu n’est pas conforme à l’une des exigences des clauses 9 ou 10 (selon le cas).

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.8.5 Modèles

Lorsque l’outil-auteur fournit des modèles, au moins l’un des modèles qui prend en charge la création de contenu conforme aux exigences des clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, doit être disponible et identifié en tant que tel.

C.11.8.5 Modèles

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel est un outil-auteur.

2. L’outil-auteur fournit des modèles

Procédure

1. Vérifier que l’outil-auteur fournit au moins un modèle qui prend en charge la création de contenu conforme aux exigences 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

2. Vérifier qu’au moins un modèle indiqué à l’étape 1 est disponible et qu’il est identifié comme étant conforme aux clauses 9 ou 10 (selon le cas).

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

REMARQUE: L’indication que le modèle est conforme aux exigences des clauses 9 ou 10 (selon le cas) mentionnée dans l’énoncé testable 2 peut être, par exemple, formulée dans les termes suivants: « Conforme à la directive WCAG 2.1 ». Lorsque l’indication n’indique pas explicitement que toutes les exigences énoncées aux clauses 9 ou 10 (selon le cas) sont respectées, il peut être nécessaire d’utiliser le modèle pour créer un site Web ou un document, puis de mettre à l’essai ce site Web ou ce document conformément aux exigences des clauses 9 ou 10 afin d’avoir la certitude que le modèle se comporte tel que requis.

12 Documentation et soutien technique

12.1 Documentation du produit
Clause de la norme EN 301 549Détermination de la conformité

12.1.1 Caractéristiques d’accessibilité et de compatibilité

La documentation du produit fournie avec les TIC, qu’elle soit fournie séparément ou intégrée aux TIC doit énumérer et expliquer les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

REMARQUE 1: Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

REMARQUE 2 : La pratique exemplaire consiste à utiliser WebSchemas/Accessibility 2.0 [i.38] pour fournir des métadonnées sur l’accessibilité des TIC.

REMARQUE 3 : L’énoncé sur l'accessibilité et les pages d’aide sont deux exemples de diffusion de renseignements sur les produits.

C.12.1.1 Caractéristiques d’accessibilité et de compatibilité

Type d’évaluation

Inspection

Conditions préalables

1. La documentation du produit est fournie avec les TIC.

Procédure

1. Vérifier que la documentation du produit fournie avec les TIC énumère et explique les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants:

1. un format Web conforme aux exigences de la clause 9;

2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1: Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2: Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3: Lorsque la documentation fait partie intégrante des TIC, elle est fournie par l’intermédiaire de l’interface utilisateur qui est accessible.

REMARQUE 4: Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

C.12.1.2 Documentation accessible

Type d’évaluation

Inspection

Conditions préalables

1. La documentation du produit en format électronique est fournie avec les TIC.

Procédure

1. Vérifier que la documentation du produit en format électronique fournie avec les TIC est conforme aux exigences des clauses 9 ou 10, selon le cas.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

12.2 Services de soutien
Clause de la norme EN 301 549Détermination de la conformité

12.2.1 Généralités (information)

Les services d’appui en matière de TIC comprennent, sans s’y limiter, les centres d’assistance, les centres d’appel, le soutien technique, les services de relais et les services de formation.

C.12.2.1 Généralités (information)

La clause 12.2.1 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent fournir des renseignements sur les caractéristiques d’accessibilité et de compatibilité inclus dans la documentation du produit.

REMARQUE: Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

C.12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Type d’évaluation

Inspection

Conditions préalables

1. Des services de soutien en matière de TIC sont fournis.

Procédure

1. Vérifier que les services de soutien en matière de TIC fournissent des renseignements sur les caractéristiques d’accessibilité et de compatibilité figurant dans la documentation du produit.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

12.2.3 Communication efficace

Les services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

C.12.2.3 Communication efficace

Type d’évaluation

Inspection

Conditions préalables

1. Des services de soutien en matière de TIC sont fournis.

Procédure

1. Vérifier que les services de soutien en matière TIC répondent aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

REMARQUE: La prestation de tout niveau de soutien visant à répondre aux besoins en communication des personnes handicapées constitue une réussite pour cette exigence. Les fournisseurs voudront peut-être fournir davantage de renseignements sur le niveau de soutien fourni pour permettre de juger de la pertinence et de la qualité du soutien.

12.2.4 Documentation accessible

La documentation fournie par les services de soutien doit être disponible dans au moins un des formats électroniques suivants:

1. un format Web conforme aux exigences de la clause 9;

2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1: Cela n’exclut pas la possibilité de fournir également la documentation dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2: Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3: Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

C.12.2.4 Documentation accessible

Type d’évaluation

Inspection

Conditions préalables

1. La documentation est fournie par les services de soutien en matière de TIC.

Procédure

1. Vérifier que la documentation en format électronique fournie par les services de soutien en matière de TIC est conforme aux exigences des clauses 9 ou 10, selon le cas.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13 TIC assurant l’accès aux services de relais ou d’urgence

13.1 Exigences en matière de services de relais
Clause de la norme EN 301 549Détermination de la conformité

13.1.1 Généralités (information)

Les services de relais permettent aux utilisateurs de différents modes de communication (texte, signes, parole, etc.) d’interagir à distance, grâce aux TIC et à la communication bidirectionnelle, en assurant une conversion entre les modes de communication, normalement effectuée par un opérateur humain.

Une pratique exemplaire consiste à respecter les exigences de la norme en vigueur ETSI ES 202 975 [i.5] en matière de services de relais.

C.13.1.1 Généralités (information)

La clause 13.1.1 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

13.1.2 Services de relais de textes

Lorsque les TIC visent à fournir un service de relais de textes, celui-ci doit permettre aux utilisateurs de textes et aux utilisateurs de la parole d’interagir en assurant la conversion entre les deux modes de communication.

C.13.1.2 Services de relais de textes

Type d’évaluation

Inspection

Conditions préalables

1. Le service est un service de relais de textes.

Procédure

1. Vérifier que le service permet aux utilisateurs de textes et aux utilisateurs de la parole d’interagir en assurant la conversion entre les deux modes de communication.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13.1.3 Services de relais de signes

Lorsque les TIC visent à fournir un service de relais de signes, celui-ci doit permettre aux utilisateurs des langues des signes et aux utilisateurs de la parole d’interagir en assurant la conversion entre les deux modes de communication.

REMARQUE: Les services de relais de signes sont aussi parfois appelés services de relais des langues des signes ou services de relais vidéo.

C.13.1.3 Services de relais de signes

Type d’évaluation

Inspection

Conditions préalables

1. Le service est un service de relais de signes.

Procédure

1. Vérifier que le service permet aux utilisateurs des langues des signes et aux utilisateurs de la parole d’interagir en assurant la conversion entre les deux modes de communication.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13.1.4 Services de relais de lecture labiale

Lorsque les TIC visent à fournir un service de relais de lecture labiale, le service de lecture labiale doit permettre aux personnes qui lisent sur les lèvres et aux utilisateurs de téléphonie vocale d’interagir en assurant la conversion entre les deux modes de communication.

C.13.1.4 Services de relais de lecture labiale

Type d’évaluation

Inspection

Conditions préalables

1. Il s’agit d’un service de relais de lecture labiale.

Procédure

1. Vérifier que le service permet aux personnes qui lisent sur les lèvres et aux utilisateurs de téléphonie vocale d’interagir en assurant la conversion entre les deux modes de communication.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13.1.5 Services de téléphonie sous-titrée

Lorsque les TIC visent à fournir un service de téléphonie sous-titrée, celui-ci doit aider un utilisateur sourd ou malentendant qui participe à un dialogue oral en lui fournissant des sous-titres traduisant l’appel entrant.

C.13.1.5 Services de téléphonie sous-titrée

Type d’évaluation

Inspection

Conditions préalables

1. Le service est un service de téléphonie sous-titré.

Procédure

1. Vérifier que le service aide un utilisateur sourd ou malentendant qui participe à un dialogue oral en lui fournissant des sous-titres traduisant l’appel entrant.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13.1.6 Services de relais de la parole à la parole

Lorsque les TIC visent à fournir un service de relais de la parole à la parole, celui-ci doit permettre aux utilisateurs de téléphones souffrant de troubles de l’élocution ou de troubles cognitifs et à tout autre utilisateur de communiquer en leur fournissant une assistance mutuelle.

C.13.1.6 Services de relais de la parole à la parole

Type d’évaluation

Inspection

Conditions préalables

1. Le service est un service de relais de la parole à la parole.

Procédure

1. Vérifier que le service permet aux utilisateurs de téléphone souffrant de troubles de l’élocution ou de troubles cognitifs et à tout autre utilisateur de communiquer en leur fournissant une assistance mutuelle.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13.2 Accès aux services de relais

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services de relais, l’accès à ces services de relais ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par un service de relais et le système des TIC.

REMARQUE 1: La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services de relais, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

C.13.2 Accès aux services de relais

Type d’évaluation

Inspection

Conditions préalables

1. Le système des TIC prend en charge la communication bidirectionnelle.

2. Un ensemble de services de relais pour la communication bidirectionnelle est spécifié.

Procédure

1. Vérifier que le système n’empêche pas l’accès à ces services de relais pour les appels entrants et sortants.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

13.3 Accès aux services d’urgence

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services d’urgence, l’accès à ces services d’urgence ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par le service d’urgence et le système des TIC.

REMARQUE 1: La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services d’urgence, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

C.13.3 Accès aux services d’urgence

Type d’évaluation

Inspection

Conditions préalables

1. Le système des TIC prend en charge la communication bidirectionnelle.

2. Un ensemble de services d’urgence pour la communication bidirectionnelle est spécifié.

Procédure

1. Vérifier que le système n’empêche pas l’accès à ces services d’urgence pour les appels entrants et sortants.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Annexe - Tableaux et figures (de la norme EN 301 549)

Les tableaux et figures ci-dessous proviennent des clauses de la norme EN 301 549 (2021) et n’ont pas été modifiés. Pour chaque tableau ou figure, un lien hypertexte a été créé pour référencer la clause associée, ce qui n'existe pas dans le PDF officiel EN 301 549 (2021) car le PDF officiel inclut ces tableaux et figures en ligne avec la clause.

Tableau 5.1: Relation entre la distance de visualisation du dessin maximale et la hauteur minimale des caractères à un angle sous-tendu minimal de 0,7 degré

Distance de visualisation du dessin maximaleHauteur minimale des caractères

100 mm

1,2 mm

200 mm

2,4 mm

250 mm

3,1 mm

300 mm

3,7 mm

350 mm

4,3 mm

400 mm

4,9 mm

450 mm

5,5 mm

500 mm

6,1 mm

550 mm

6,7 mm

600 mm

7,3 mm

Figure 1 : Relation entre la hauteur minimale des caractères et la distance de visualisation du dessin maximale
Diagramme illustrant le contenu linéaire du texte 5.1.4 Fonctionnalité fermée à l'agrandissement du texte

Contenu connexe:

Figure 2 : Portée avant libre
Un diagramme illustrant le contenu du texte 8.3.2.2 Hauteur minimum de la portée avant libre. Personne en fauteuil roulant tendue vers l'avant.

Contenu connexe:

Figure 3 : Portée avant obstruée
Un diagramme illustrant le contenu du texte 8.3.2.3.3. Portée avant (<635 mm) obstruée. Personne en fauteuil roulant qui s'étend au-dessus d'un bureau et qui démontre qu'il n'y a pas d'obstacles et qu'il y a une obstruction à avant portée.

Contenu connexe:

Figure 4 : Espace libre pour les pieds
Un diagramme illustrant le contenu du texte 8.3.2.5 Espace libre pour les pieds.

Contenu connexe:

Figure 5 : Espace libre pour les genoux
Un diagramme illustrant le contenu du texte 8.3.2.6 Espace libre pour les genoux.

Contenu connexe:

Figure 6 : Portée latérale libre
Un diagramme illustrant le contenu du texte 8.3.3.2 Hauteur minimale de la portée latérale libre. Personne en fauteuil roulant qui se penche sur le côté.

Contenu connexe:

Figure 7 : Portée latérale haute obstruée
Un diagramme illustrant le contenu du texte 8.3.3.3.2 Portée latérale haute obstruée (≤ 610 mm). Personne en fauteuil roulant tendre à le côté et qui démontre qu'il n'y a pas d'obstacles et qu'il y a un obstruction à haute latérale portée.

Contenu connexe:

Figure 8 : Changement de niveau vertical
Un diagramme illustrant le contenu du texte 8.3.4.1. Changement de niveau.

Contenu connexe:

Figure 9 : Changement de niveau en biseau
Un diagramme illustrant le contenu du texte 8.3.4.1. Changement de niveau.

Contenu connexe:

Figure 10 : Surface au sol dégagée
Diagramme illustrant le contenu du texte 8.3.4.2 Surface de plancher ou de sol dégagée. Personne en fauteuil roulant démontrant un espace libre minimal.

Contenu connexe:

Figure 11 : Espace libre de manœuvre dans une alcôve, approche avant
Un diagramme illustrant le contenu du texte 8.3.4.3.2 Approche avant. Personne dans un fauteuil roulant dans un alcôve.

Contenu connexe:

Figure 12 : Espace libre de manœuvre dans une alcôve approche parallèle
Un diagramme illustrant le contenu du texte 8.3.4.3.3 Approche parallèle. Personne dans un fauteuil roulant dans un alcôve.

Contenu connexe:

Tableau 9.1 : Critères de succès de niveau AAA des WCAG 2.1
No.RègleNuméro du critère de succèsNom du critère de succès
1Média temporel1.2.6Langue des signes (pré-enregistrée)
2Média temporel1.2.7Audio-description étendue (pré-enregistrée)
3Média temporel1.2.8Version de remplacement pour un média temporel (pré-enregistrée)
4Média temporel1.2.9Seulement audio (en direct)
5Adaptable1.3.6Identifier la fonction
6Distinguable1.4.6Contraste (amélioré)
7Distinguable1.4.7Arrière-plan sonore de faible volume ou absent
8Distinguable1.4.8Présentation visuelle
9Distinguable1.4.9Texte sous forme d’image (sans exception)
10Accessibilité au clavier2.1.3Clavier (pas d’exception)
11Délai suffisant2.2.3Pas de délai d’exécution
12Délai suffisant2.2.4Interruptions
13Délai suffisant2.2.5Nouvelle authentification
14Délai suffisant2.2.6Délais d’expiration
15Crises et réactions physiques2.3.2Trois flashs
16Crises et réactions physiques2.3.3Animation résultant d’interactions
17Navigable2.4.8Localisation
18Navigable2.4.9Fonction du lien (lien uniquement)
19Navigable2.4.10En-têtes de section
20Modalités d’entrée2.5.5Taille de la cible
21Modalités d’entrée2.5.6Modalités d’entrées concurrentes
22Lisible3.1.3Mots rares
23Lisible3.1.4Abréviations
24Lisible3.1.5Niveau de lecture
25Lisible3.1.6Prononciation
26Prévisible3.2.5Changement à la demande
27Assistance à la saisie3.3.5Aide
28Assistance à la saisie3.3.6Prévention des erreurs (toutes)

Annexe – Chapitre 14 - Conformité

La conformité au présent document est obtenue en respectant toutes les exigences applicables, c’est-à-dire les clauses contenant le mot « doit ». Les clauses contenant le mot « devrait » sont des recommandations et ne sont pas requises pour la conformité.

Toutes les clauses, à l’exception de la clause 12, comprennent une autoévaluation de la portée. Cela signifie qu’elles sont introduites par la locution « Lorsque les TIC'.Une exigence est respectée lorsque la condition préalable est vraie et que le test correspondant (en annexe C) est réussi. Lorsque l’une des conditions préalables est fausse, l’exigence est non applicable. Par conséquent, le résultat des tests de l’annexe C peut être : non applicable, réussite, échec ou (dans des circonstances exceptionnelles) non testable.

Les TIC sont souvent constituées d’un assemblage de deux ou plusieurs éléments de TIC. Dans certains cas, au moins deux éléments interopérables de TIC peuvent, ensemble, répondre à davantage d’exigences de la norme lorsqu’un élément complète la fonctionnalité de l’autre et que l’ensemble répond à davantage d’exigences d’accessibilité. Toutefois, la combinaison de deux éléments de TIC, qui ne réussissent pas à satisfaire à une exigence particulière, n’aboutira pas à un système de TIC combiné qui répond à cette exigence.

Le présent document n’établit pas l’ordre de priorité des exigences.

REMARQUE 1 : Une mise en œuvre ou une maintenance ultérieure pourrait avoir une incidence sur la conformité aux exigences d’accessibilité.

REMARQUE 2 : Un échantillonnage est souvent nécessaire pour les TIC complexes lorsqu’il y a trop d’instances de l’objet à tester. Le présent document ne peut pas recommander de techniques d’échantillonnage précises pour l’évaluation des TIC car celles-ci sont propres au contexte.

La nature inhérente de certaines situations fait qu’il est impossible de faire des déclarations fiables et définitives sur le respect des exigences d’accessibilité. Par conséquent, dans ces situations, les exigences du présent document sont sans objet :

REMARQUE 3 : Même dans les situations ci-dessus, la pratique exemplaire consiste à appliquer les exigences du présent document chaque fois qu’il est possible de le faire en toute sécurité.

Annexe - Références (de la norme EN 301 549 – en anglais seulement)

2.1 Références normatives

Les références sont spécifiques, identifiées par leur date de publication et/ou leur numéro d'édition ou leur numéro de version. Seule la version citée est applicable.

Les documents cités en référence qui ne sont pas disponibles publiquement à l'emplacement prévu peuvent se trouver à ETSI References in docbox (en anglais seulement).

Les documents de référence suivants sont nécessaires à l’application du présent document.

[1] ETSI ETS 300 381 (Edition 1) (December 1994): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids".

[2] ETSI ES 200 381-1 (V1.2.1) (October 2012): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids Part 1: Fixed-line speech terminals".

[3] ETSI ES 200 381-2 (V1.1.1) (October 2012): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids; Part 2: Cellular speech terminals".

[4] W3C Recommendation (December 2008) /ISO/IEC 40500:2012: "Web Content Accessibility Guidelines (WCAG) 2.0".

[5] W3C Proposed Recommendation (June 2018): "Web Content Accessibility Guidelines (WCAG) 2.1".

2.2 Références informatives

Les références sont soit spécifiques (identifiées par la date de publication et/ou le numéro d'édition ou le numéro de version), soit non spécifiques. Pour des références spécifiques, seule la version citée est applicable. En ce qui concerne les références non spécifiques, la dernière version du document cité en référence (y compris les modifications éventuelles) est applicable.

Les documents de référence suivants ne sont pas nécessaires pour l’application du présent document, mais ils aident l’utilisateur dans un domaine particulier.

[i.1] ANSI/IEEE C63.19 (2011): "American National Standard Method of Measurement of Compatibility between Wireless Communication Devices and Hearing Aids". 

[i.2] ANSI/TIA-4965: "Receive volume control requirements for digital and analogue wireline terminals". 

[i.3] European Commission M 376-EN: "Standardization Mandate to CEN, CENELEC and ETSI in support of European accessibility requirements for public procurement of products and services in the ICT domain". 

[i.4] ETSI EG 201 013: "Human Factors (HF); Definitions, abbreviations and symbols". 

[i.5] ETSI ES 202 975: "Human Factors (HF); Requirements for relay services". 

[i.6] ETSI ETS 300 767: "Human Factors (HF); Telephone Prepayment Cards; Tactile Identifier". 

[i.7] ETSI CEN/CENELEC/ETSI Translations 101 550: "Documents relevant to EN 301 549 "Accessibility requirements suitable for public procurement of ICT products and services in Europe"". 

[i.8] ETSI CEN/CENELEC/ETSI Translations 101 551: "Guidelines on the use of accessibility award criteria suitable for publicly procured ICT products and services in Europe". 

[i.9] ETSI Translations 102 612: "Human Factors (HF); European accessibility requirements for public procurement of products and services in the ICT domain (European Commission Mandate M 376, Phase 1)". 

[i.10] ETSI TS 126 114: "Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction (3GPP TS 26.114)". 

[i.11] ETSI TS 122 173: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 (3GPP TS 22.173)". 

[i.12] ETSI TS 134 229: "Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification (3GPP TS 34.229)". 

[i.13] IETF RFC 4103 (2005): "RTP Payload for Text Conversation".

[i.14] ISO/IEC 17007:2009: "Conformity assessment - Guidance for drafting normative documents suitable for use for conformity assessment". 

[i.15] ISO 9241-11:2018:"Ergonomics of human-system interaction - Part 11: Usability: Definitions and concepts". 

[i.16] ISO 9241-110:2006: "Ergonomics of human-system interaction -- Part 110: Dialogue principles". 

[i.17] ISO 9241-171:2008: "Ergonomics of human-system interaction-Part 171: Guidance on software accessibility". 

[i.18] void

[i.19] ISO/IEC 13066-1:2011: "Information technology - Interoperability with assistive technology (AT) - Part 1: Requirements and recommendations for interoperability". 

[i.20] Recommendation ITU-T E.161 (2001): "Arrangement of digits, letters and symbols on telephones and other devices that can be used for gaining access to a telephone network". 

[i.21] Recommendation ITU-T G.722 (1988): "7 kHz audio-coding within 64 kbit/s". 

[i.22] Recommendation ITU-T G.722.2 (2003): "Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB)". 

[i.23] Recommendation ITU-T V.18 (2000): "Operational and interworking requirements for DCEs operating in the text telephone mode". 

[i.24] TIA-1083-A (2010): "Telecommunications; Telephone Terminal equipment; Handset magnetic measurement Procédures and performance requirements". 

[i.25] Section 508 of the United States Rehabilitation Act of 1973, revised 2017. REMARQUE: Disponible à https://www.section508.gov/manage/laws-and-policies . 

[i.26] W3C Working Group Note 5 September 2013: "Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT)". 

[i.27] M 554 Commission Implementing Decision C(2017)2585 of 27.4.2017 on a standardisation request to the European standardisation organisations in support of Directive (EU) 2016/2102 of the European Parliament and of the Council on the accessibility of the websites and mobile applications of public sector bodies. 

[i.28] Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies. 

[i.29]ETSI/CEN/CENELEC EN 301 549 (V2.1.2) (August 2018): "Accessibility requirements for ICT products and services". 

[i.30] ETSI/CEN/CENELEC Translations 101 552: "Guidance for the application of conformity assessment to accessibility requirements for public procurement of ICT products and services in Europe".

[i.31] ISO/IEC TS 20071-25:2017: "Information technology - User interface component accessibility - Part 25: Guidance on the audio presentation of text in videos, including captions, subtitles and other on-screen text".

[i.32] W3C Recommendation (September 2015): "Authoring Tool Accessibility Guidelines (ATAG) 2.0". REMARQUE: Disponible à https://www.w3.org/WAI/standards-guidelines/atag/.

[i.33] W3C Recommendation (September 2015): "User Agent Accessibility Guidelines (UAAG) 2.0". REMARQUE: Disponible à https://www.w3.org/WAI/standards-guidelines/uaag/.

[i.34]ISO 21542:2011: "Building construction - Accessibility and usability of the built environment".

[i.35]ISO/IEC Guide 71:2014: "Guide for addressing accessibility in standards".

[i.36]Recommendation ITU-T T.140 (1988): "Protocol for multimedia application text conversation".

[i.37]Recommendation ITU-T F.703 (2000): "Multimedia conversational services".

[i.38] W3C WebSchemas/Accessibility 2.0. REMARQUE: Disponible à https://www.w3.org/wiki/WebSchemas/Accessibility.

[i.39]Void

[i.40]Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on public procurement and repealing Directive 2004/18/EC.

Annexe – Définition des termes, symboles et abréviations (d’après la norme EN 301 549)

3.1 Termes

Aux fins du présent document, les termes figurant dans la norme EG 201 013[i.4] de l’ETSI et les définitions suivantes s’appliquent :

accessibilité:

degré selon lequel des produits, systèmes, services, environnements et installations peuvent être utilisés par des membres d'une population présentant le plus large éventail possible de caractéristiques et de capacités en vue d'atteindre un objectif spécifié dans un contexte d'utilisation donné ISO 9241-11:2018 [i.15])

  • REMARQUE 1: Le contexte d’utilisation comprend l’utilisation directe et l’utilisation assistée par des technologies d’assistance.
  • REMARQUE 2: Le contexte dans lequel les TIC sont utilisées peut avoir une incidence sur leur accessibilité globale. Le contexte peut comprendre d’autres produits et services avec lesquels les TIC sont susceptibles d’interagir.
espace d’accès:

l’espace destiné à être occupé par la personne, y compris sa technologie d’assistance, pendant qu’elle utilise le produit

Aide de suppléance à l’audition (ASA):

appareils qui aident à séparer les sons, en particulier la parole, qu’une personne veut entendre du bruit de fond en apportant le son directement dans l'oreille.

  • REMARQUET: On les trouve souvent dans les réunions et les lieux publics tels que les théâtres, les concerts et les lieux de culte. Ils peuvent également être utilisés à la maison avec les téléviseurs et autres produits à sortie sonore
Technologie d’aide (TA):

équipement, système, matériel informatique, logiciel ou service utilisé pour augmenter, maintenir ou améliorer les capacités des individus (d’après la norme ISO/CEI Guide 71:2014 [i.35]).

  • REMARQUE 1 : Technologie d'aide est un terme général plus large que produits d'assistance.
  • REMARQUE 2 : La technologie d'aide peut inclure les services d'aide et les services professionnels nécessaires à l'évaluation, la recommandation et la mise à disposition.
  • REMARQUE 3 : Lorsque les TIC ne prennent pas en charge directement la technologie d’assistance connectée, les dispositifs qui peuvent être exploités par un système mis en réseau ou connecté par un autre système de connexion à distance, ledit système distinct (y compris la technologie d’assistance incluse) peut également être considéré comme étant une technologie d’assistance.
Audiodescription

Narration ajoutée à une piste sonore intercalée avec le dialogue, qui décrit les aspects importants du contenu visuel de médias audiovisuels qui ne pourraient être compris à partir de la piste sonore principale uniquement.

  • REMARQUE: On parle aussi de “vidéo description » ou “narration descriptive ».
Outil-auteur:

Logiciel pouvant être utilisé pour créer ou modifier du contenu.

  • REMARQUE 1: Un outil-auteur peut être utilisé par un seul utilisateur ou par plusieurs utilisateurs travaillant ensemble.
  • REMARQUE 2: Un outil-auteur peut être une application autonome unique ou être composé d’un ensemble d’applications.
  • REMARQUE 3: Un outil de création peut produire un contenu destiné à être modifié ou à être utilisé par les utilisateurs finaux.
Légende

Texte ou élément visuel synchronisé constituant une solution de remplacement pour l’information sonore, vocale ou non vocale nécessaire à la compréhension du contenu média (d’après la directive WCAG 2.1[5])

  • REMARQUE: On parle également de “sous-titres » ou de “sous-titres pour les sourds et les malentendants ».
Fonction restreinte

Fonctionnalité limitée par des caractéristiques qui empêche un utilisateur de joindre, d’installer ou d’utiliser une technologie d’assistance.

Contenu

Information et expérience sensorielle à communiquer à l’utilisateur au moyen d’un logiciel, y compris le code ou le balisage qui définit la structure, la présentation et les interactions du contenu (d’après WCAG2ICT[i.26])

  • REMARQUE: Le contenu se trouve dans trois endroits: les pages Web, les documents et les logiciels. Lorsqu’il s’agit du contenu d’une page Web ou d’un document, un agent utilisateur est nécessaire afin de pouvoir communiquer à l’utilisateur l’information et l’expérience sensorielle du contenu. Lorsqu’il s’agit du contenu d’un logiciel, un agent utilisateur n’est pas nécessaire pour pouvoir communiquer à l’utilisateur l’information et l’expérience sensorielle du contenu – le logiciel exécute lui-même cette fonction.
contexte d’utilisation

combinaison d’utilisateurs, d’objectifs et de tâches, de ressources et d’environnement (d’après la norme ISO 9241-11:2018 [i.15]).

  • REMARQUE : Dans un contexte d’utilisation, l’ « environnement » inclut les environnements technique, physique, social, culturel et organisationnel.
document:

ensemble de contenu logiquement distinct (tel qu’un fichier, un ensemble de fichiers ou un média diffusé en continu) qui fonctionne comme une entité unique plutôt que comme une collection, qui ne fait pas partie d’un logiciel et qui n’inclut pas son propre agent utilisateur (d’après WCAG2ICT [i.26]).

  • REMARQUE 1 : Un document nécessite toujours un agent utilisateur pour présenter son contenu à l'utilisateur.
  • REMARQUE 2 : Les lettres, les messages électroniques, les feuilles de calcul, les livres, les images, les présentations et les films sont des exemples de documents.
  • REMARQUE 3 : Les fichiers de configuration et de stockage des logiciels, tels que les bases de données et les définitions de virus, ainsi que les fichiers d’instructions informatiques, tels que le code source, les fichiers batch/script et les micrologiciels, sont des exemples de fichiers qui font partie du logiciel et ne sont donc pas des exemples de documents. Si et quand le logiciel récupère « l’information et l’expérience sensorielle à communiquer à l’utilisateur » à partir de tels fichiers, il s’agit simplement d’une autre partie du contenu qui se produit dans le logiciel et qui est couvert par WCAG2ICT comme toute autre partie du logiciel. Lorsque de tels fichiers contiennent un ou plusieurs documents intégrés, les documents intégrés restent des documents selon cette définition.
  • REMARQUE 4 : Une collection de fichiers zippés, stockés dans un seul fichier de disque dur virtuel ou stockés dans un seul fichier chiffré du système de fichiers ne constitue pas un document unique lorsque les fichiers sont ainsi rassemblés. Le logiciel qui archive/chiffre ces fichiers ou gère le contenu du disque dur virtuel ne fonctionne pas comme un agent utilisateur pour les fichiers individuels de cette collection, car ce logiciel ne fournit pas une présentation entièrement fonctionnelle de ce contenu.
  • REMARQUE 5 : Tout ce qui peut présenter son propre contenu sans faire appel à un agent utilisateur, comme un livre automatique, n’est pas un document mais un logiciel.
  • REMARQUE 6 : Un document unique peut être composé de plusieurs fichiers, tels que le contenu vidéo et le texte des sous-titres. Ce fait n’est généralement pas apparent pour l’utilisateur final qui consomme le document/contenu.
  • REMARQUE 7 : Un assemblage de fichiers représentant les fichiers vidéo, audio, de sous-titres et de synchronisation d’un film est un exemple de document.
  • REMARQUE 8 : Une reliure utilisée pour relier les différentes pièces à conviction d’une affaire judiciaire ne serait pas un document.
  • REMARQUE 9 : Les documents pourraient contenir des sous-documents.
intégré:

directement inclus dans le contenu qui est téléchargé vers l’agent utilisateur et son extension, et qui est destiné à être utilisé pour le rendu de la page Web.

  • REMARQUE : Un élément qui est téléchargé à l’aide d’un mécanisme sur la page Web mais qui n’est pas utilisé pour rendre la page n’est pas « intégré » dans la page.
Réseau de TIC:

technologie et ressources permettant la connexion et le fonctionnement de TIC interconnectées.

Technologies de l’information et des communications (TIC):

technologie, équipement ou système ou sous-système interconnecté d’équipements dont la fonction principale est la création, la conversion, la duplication, l’acquisition automatique, le stockage, l’analyse, l’évaluation, la manipulation, la gestion, le déplacement, le contrôle, l’affichage, la commutation, l’échange, la transmission, la réception ou la diffusion de données ou d’informations.

  • REMARQUE : Les pages Web, le contenu électronique, les produits de télécommunications, les ordinateurs et les équipements auxiliaires, les logiciels, y compris les applications mobiles, les kiosques d’information et les machines de transaction, les vidéos, les services informatiques et les machines de bureau multifonctions qui copient, numérisent et télécopient des documents sont des exemples de TIC.
pièce manœuvrablee mécanique:

pièce manoeuvrable qui possède une interface mécanique pour activer, désactiver ou ajuster la TIC.

  • REMARQUE : Les couvercles de scanners, les stations d’accueil d’ordinateurs portables et les couvercles, ainsi que les interrupteurs et les verrous physiques sont des exemples de pièces manœuvrables mécaniques.
mécanisme d’écoute privée:

sortie sonore conçue pour que seul l'utilisateur actuel puisse recevoir le son.

  • REMARQUE : Les casques d’écoute personnels, les haut-parleurs directionnels et les capots audio sont des exemples de mécanismes d’écoute privée.
contenu non textuel:

contenu qui n’est pas une séquence de caractères pouvant être déterminée par un programme informatique ou dans lequel la séquence n’exprime pas quelque chose en langage humain (d’après WCAG 2.1 [5]).

document non Web:

document qui n’est pas une page Web, qui n’est pas intégré dans une page Web et qui n’est pas utilisé pour le rendu ou le fonctionnement de la page.

logiciel non Web:

logiciel qui n’est pas une page Web, qui n’est pas intégré dans une page Web et qui n’est pas utilisé pour le rendu ou le fonctionnement de la page.

Fonction non restreinte:

fonctionnalité qui prend en charge l’accès par une technologie d’assistance

  • REMARQUE: C’est le contraire de la fonction restreinte.
Pièce manœuvrable:

Composante des TIC utilisée pour les activer, les désactiver ou les ajuster.

  • REMARQUE 1: Les pièces manœuvrables peuvent être fournies pour le matériel (voir les pièces manœuvrables mécaniques ci-dessus) et les logiciels. Un bouton à l’écran est un exemple d’une pièce manœuvrable fournie par un logiciel.
  • REMARQUE 2 : Les pièces manoeuvrables ne comprennent pas les pièces utilisées uniquement pour l’entretien ou la réparation ou d’autres interventions qui ne sont pas attendues d’un utilisateur typique si le produit fonctionne bien. Ces interventions comprennent : l’élimination des bourrages papier à l’intérieur de la machine, le remplacement des éléments ou des pièces internes de la machine qui peuvent exposer l’utilisateur final à des surfaces tranchantes ou chaudes, le remplacement ou la réparation des éléments désignés par les fabricants comme des éléments de service ou d’entretien dans la documentation utilisateur.
Logiciel de plateforme (plateforme):

ensemble de composants logiciels qui s’exécute sur une couche logicielle ou matérielle sous-jacente et qui fournit un ensemble de services logiciels à d’autres composants logiciels permettant d’isoler ces applications de la couche logicielle ou matérielle sous-jacente (d’après ISO/IEC 13066-1[i.19])

  • REMARQUE: Un composant logiciel particulier peut jouer le rôle d’une plateforme dans certaines situations et d’un client dans d’autres.
Déterminable par programmation:

capable d’être lu par un logiciel à partir de données fournies par le développeur de sorte que d’autres logiciels, y compris les technologies d’assistance, puissent extraire et présenter ces renseignements aux utilisateurs selon différentes modalités.

  • REMARQUE: La directive WCAG 2.1 utilise l’adjectif “déterminé » alors que la présente définition utilise l’expression “capable d’être lu » (pour éviter toute ambiguïté avec le mot “déterminé »).
Texte en Temps Réel (TTR):

form of a text conversation in point to point situations or in multipoint conferencing where the text being entered is sent in such a way that the communication is perceived by the user as being continuous

  • REMARQUE 1 : Les utilisateurs percevront la communication comme continue si le délai entre la création du texte par l’expéditeur et sa réception par le destinataire est inférieur à 500 ms. Toutefois, le délai réel dépendra du réseau de communication.
  • REMARQUE 2 : La création de texte différera selon que le système permet d’entrer le texte mot par mot (p. ex., la conversion de la voix en texte et la saisie du texte prédictif) ou d’entrer un caractère à la fois. La création de texte sera différente selon qu’il s’agit de systèmes où le texte est saisi mot par mot (p. ex. les systèmes de transmission automatique de la parole et de texte prédictif) ou de systèmes où chaque caractère est généré séparément (par exemple, la saisie sur un clavier physique).
Satisfait à un critère de réussite

Le critère de réussite ne se révèle pas faux lorsqu’il est appliqué au TIC (d’après la directive WCAG 2.1 [5])

Connexion utilisateur unique:

connexion constituée de son, de TTR ou de vidéo (ou d’une combinaison de deux ou trois de ces médias) établie par une seule action de l'utilisateur.

  • REMARQUE : Même si les différents médias peuvent emprunter des canaux différents et impliquent plusieurs composants matériels, l’utilisateur a l’impression qu’il s’agit d’une connexion unique, et elle est traitée par toutes les technologies intermédiaires (p. ex. le réseau, l'auto-réception) comme une connexion unique à des fins comme le transfert.
Sous-titres vocaux/sous-titres audio:

les sous-titres qui sont exprimés vocalement sur le contenu audiovisuel (d’après la norme ISO/IEC TS 20071-25 [i.31])

TIC fixes:

TIC qui reposent sur le sol, ou qui sont montées sur un mur ou une autre structure immobile, et qui ne sont pas destinées à être déplacées par leur utilisateur.

  • REMARQUE 1 : En général, les TIC fixes reposent sur le sol (comme un kiosque d’information) ou sont installées dans un mur (comme une machine qui distribue de l’argent ou effectue d’autres services bancaires).
  • REMARQUE 2 : Un fabricant ne peut pas contrôler la hauteur des TIC posées sur une table par quelqu’un d’autre, mais il est en mesure de contrôler les dimensions de la portée des TIC autonomes qui reposent sur le sol et peut spécifier les hauteurs d’installation dans les murs.
Terminal

Ensemble de matériel et de logiciel grâce auquel l’utilisateur final interagit directement et qui fournit l’interface utilisateur.

  • REMARQUE 1: Le matériel peut être composé de plusieurs appareils fonctionnant ensemble, par exemple un appareil mobile et un ordinateur.
  • REMARQUE 2: Pour certains systèmes, le logiciel qui fournit l’interface utilisateur peut se trouver sur plusieurs appareils, comme un téléphone et un serveur.
À tour de rôle:

type d’organisation dans la conversation et le discours selon lequel les participants parlent un à la fois, chacun leur tour.

Agent utilisateur:

Tout logiciel qui récupère et présente le contenu aux utilisateurs (d’après la directive WCAG 2.1[5])

  • Tout logiciel qui récupère et présente le contenu aux utilisateurs (d’après la directive WCAG 2.1[5])
  • REMARQUE 2: À titre d’exemple de logiciel qui n’est pas un agent utilisateur, on peut citer une application de calculatrice qui n’obtient pas les résultats des calculs à l’extérieur du logiciel afin de les présenter à un utilisateur. Dans ce cas, le logiciel de la calculatrice n’est pas un agent utilisateur, c’est simplement un logiciel doté d’une interface utilisateur.
  • REMARQUE 3: Les logiciels qui n’affichent qu’un aperçu du contenu tel qu’une vignette ou toute autre présentation qui n’est pas entièrement opérationnelle ne fournissent pas de fonctionnalité d’agent utilisateur.
Interface utilisateur:

Toutes les composantes d’un système interactif (logiciel ou matériel) qui fournissent des renseignements ou des commandes permettant à l’utilisateur d’accomplir des tâches spécifiques avec le système interactif (d’après la norme ISO 9241-110[i.16])

Élément d’interface utilisateur:

Entité de l’interface utilisateur qui est présentée à l’utilisateur par le logiciel (d’après la norme ISO 9241¬171[i.17])

  • REMARQUE 1: On parle aussi de “composante d’interface utilisateur ».
  • REMARQUE 2: Les éléments d’interface utilisateur peuvent être interactifs ou non.
Contenu Web:

contenu qui se trouve dans une page Web, et qui est utilisé dans la restitution ou qui est conçu pour être utilisé dans la restitution de la page Web.contenu qui se trouve dans une page Web, et qui est utilisé dans la restitution ou qui est conçu pour être utilisé dans la restitution de la page Web.

Page Web:

Une ressource autonome obtenue depuis un URI unique grâce au protocole HTTP, accompagnée de toutes les autres ressources utilisées dans la restitution ou conçues pour être restituées simultanément par un agent utilisateur (d’après la directive WCAG 2.1[5])

3.2 Symboles

Sans objet

3.3 Abréviations

Aux fins du présent document, les abréviations suivantes sont employées :

ANSI
American National Standards Institute/ Loi sur les Américains en situation de handicap
AT
Assistive Technology/ Technologie d’Assistance (TA)
ATAG
Authoring Tool Accessibility Guidelines (of W3C)/ Règles d'accessibilité pour les outils d'édition (du W3C)
CEN
Comité Européen de Normalisation
CSS
Cascading Style Sheets/ Feuilles de style en cascade
DOM
Document Object Model/ Modèle d'objets de document
EU
European Union/ Union européenne
IPS
Images par seconde
FXML
XML-based user interface markup language (pas de terme en français)
HTML
HyperText Markup Language (pas de terme en français)
HTTP
HyperText Transfer Protocol (pas de terme en français)
ICT
Information and Communication Technology/ Technologies de l’information et des communications (TIC)
IETF
Internet Engineering Task Force (pas de terme en français)
IMS
IP Multimedia System/ Sous-système multimédia IP
IP
Internet Protocol/ Protocole internet
JWG
Joint Working Group (of CEN/CENELEC/ETSI)
ODF
Open Document Format/ Format OpenDocument
OOXML
Office Open eXtensible Markup Language (pas de terme en français)
RTPC
Réseau téléphonique public commuté
RFC
Request For Comment/ Demande de commentaires
TTR
Texte en temps réel
SIP
Session Initiation Protocol (pas de terme en français)
URI
Uniform Resource Identifier/ Identifiant uniforme de ressource
USB
Universal Serial Bus/ bus série universel
VoIP
Voice over IP/ Voix sur IP
W3C
World Wide Web Consortium (pas de terme en français)
WCAG
Web Content Accessibility Guidelines (of W3C/ Règles pour l’accessibilité des contenus Webdd>
XML
eXtensible Markup Language/ Langage de balisage extensible
XUL
XML User interface Language (pas de terme en français)
ISO
International Organization for Standardization/ Organisation internationale de normalisation
ITU-T
International Telecommunication Union - Telecommunication standardization sector/ Union internationale des télécommunications - Secteur de la normalisation des télécommunications
LED
Light Emitting Device/ Diode électroluminescente
QVGA
Quarter Video Graphics Array (pas de terme en français)
UAAG
User Agent Accessibility Guidelines (of W3C)/ Directives pour l'accessibilité des agents utilisateurs (du W3C)
VGA
Video Graphics Array (pas de terme en français)
WAI
Web Accessibility Initiative/ L'Initiative d'Accès au Web
WLAN
Wireless Local Access Network (pas de terme en français)

Annexe - Conseils pratiques sur la création d’une documentation non-Web accessible

Dans les WCAG, les « critères de succès » sont tous agnostiques sur le plan technologique. Les exigences relatives aux documents non-Web sont basées sur les exigences de niveau AA de la norme WCAG 2.1, ce qui signifie que tous les critères de niveau A et AA pertinents pour les documents doivent être respectés.

Les W3C publient des techniques suffisantespour répondre aux critères de succès du WCAG, y compris des techniques pour les formats de document autres que Web, tels que PDF. L'utilisation d'une technique donnée est considérée « suffisante » pour répondre aux critères pertinents pour la technique, mais vous pouvez également répondre aux critères d'autres manières.

Services partagés Canada a créé un ensemble de guides pour la production de documents accessibles dans Microsoft Office:

Divers organismes et fournisseurs de logiciels offrent du matériel supplémentaire proposant des instructions en vue de rendre les documents accessibles:

REMARQUE : Le fait de suivre les conseils prodigués dans les liens susmentionnés ne garantit pas la conformité aux normes WCAG 2.1. Les liens sont fournis à titre indicatif seulement.

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Exigences en matière de technologies de l’information et des communications (TIC) accessibles

Cette page a pour but de partager une partie du travail effectué par Services partagés Canada (SPC) pour le pilotage des normes harmonisées d'accessibilité des technologies de l’information et des communications (TIC) EN 301 549 (2021). Il ne s'agit pas d'un copier / coller / traduction complet des normes, l'EN 301 549 (2021) ou le Web Content Accessibility Guidelines (WCAG) 2.1.

Exigences en matière de technologies de l’information et des communications (TIC) accessibles ( Word, 636 ko)

Que sont les TIC?

Les technologies de l’information et des communications (TIC) comprennent le matériel, les logiciels, les communications vocales, les capacités vidéo et le contenu numérique (y compris l’information sur le Web et ailleurs).

Qu’est-ce que l’accessibilité des TIC et pourquoi est-elle importante?

« L’accessibilité des TIC permet aux personnes handicapées et non handicapées d’accéder aux mêmes informations, d’accomplir les mêmes tâches et de recevoir les mêmes services grâce aux technologies de l’information. C’est l’équivalent numérique de l’accessibilité dans l’environnement physique – les bateaux de trottoir, les rampes d’accès, les garde-corps, etc. L’accessibilité des TIC peut offrir des avantages en termes d’ergonomie à tous ceux qui utilisent les TIC, mais elle est essentielle pour de nombreuses personnes handicapées. » - NASCIO - Accessibilité en matière d’acquisition de TI (en anglais seulement).

À propos du présent document et avis de droit d’auteur

Ce document reproduit les exigences pertinentes du EN 301 549 v3.2.1 (2021-03) norme européenne harmonisée « Exigences en accessibilité pour les produits et services en TIC », disponible en anglais seulement, (© utilisé sous la licence de l’Institut Européen de Normalisation des Télécommunications 2021. © Comité Européen de Normalisation 2021. © Comité Européen de Normalisation Électrotechnique 2021. Tous droits réservés.), ce qui inclut les Règles pour l'accessibilité des contenus Web (WCAG) 2.1 de niveau AA.

Les droits de propriété intellectuelle (DPI) essentiels ou potentiellement essentiels aux livrables normatifs peuvent avoir été déclarés à l'ETSI. Les informations relatives à ces DPI essentiels, le cas échéant, sont accessibles au public pour les membres et les non-membres de l'ETSI, dans ETSI SR 000 314 : « Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards », disponible auprès du secrétariat de l'ETSI. Les dernières mises à jour sont disponibles sur le serveur Web ETSI (https://ipr.etsi.org/) (en anglais seulement). Veuillez consulter la base de données ETSI IPR (en anglais seulement) pour la recherche de DPI.

Le présent document contient des exigences qui, à première vue, peuvent sembler sans rapport avec ce produit ou de service. Elles ont été incluses aux fins de considération puisqu’il est impossible de savoir ce qui pourrait être inclus dans le produit ou service d’un fournisseur. Par exemple, une vidéo peut être intégrée à la documentation d’un produit et les exigences en matière d’accessibilité pour la vidéo et l’audio peuvent devenir pertinentes.

Les annexes comprennent des définitions, des références et un guide pratique portant sur la création d’une documentation accessible.

Sources utilisées pour compiler le présent document

Sur cette page

Vous pouvez trouver ici des informations partielles et les présenter en deux langues à titre informatif. Les marchés publics spécifiques auront les exigences appropriées en matière de TIC dans le dossier d'appel d'offres.

Partie A - Énoncés de rendement fonctionnel

Il s’agit d’énoncés explicatifs (non testables) qui présentent les aspects essentiels que le produit ou le service offert doit fournir pour être jugé accessible.

4.2.1 Utilisation sans vision: Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas la vision.

4.2.2 Utilisation avec vision limitée: Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec des fonctions leur permettant de mieux utiliser leur vision limitée.

4.2.3 Utilisation sans perception des couleurs: Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec un mode de fonctionnement visuel qui n’exige pas la perception des couleurs par les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une perception limitée des couleurs et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.4 Utilisation sans audition: Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas l’audition. Ceci est essentiel pour les utilisateurs sans audition et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.5 Utilisation avec audition limitée: Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin des TIC avec des fonctions audio améliorées. Ceci est essentiel pour les utilisateurs ayant une audition limitée et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.6 Utilisation sans capacité vocale: Lorsque les TIC nécessitent la contribution vocale des utilisateurs, certains utilisateurs auront besoin des TIC pour fournir au moins un mode de fonctionnement qui n’exige pas d’entrée vocale. Ceci est essentiel pour les utilisateurs sans capacité vocale ou ayant une capacité vocale limitée et est bénéfique à plusieurs autres dans différentes situations.

4.2.7 Utilisation avec une capacité de manipulation ou de force limitée: Lorsque les TIC nécessitent des actions manuelles, certains utilisateurs auront besoin de TIC avec des caractéristiques qui permettent aux utilisateurs d’utiliser les TIC par d’autres actions ne nécessitant aucune manipulation ou force de la main. Ceci est essentiel pour les utilisateurs ayant une capacité de manipulation ou de force limitée et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.8 Utilisation à portée limitée: Lorsque les produits des TIC sont autonomes ou installés, les éléments opérationnels doivent être à la portée de tous les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une portée limitée et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.9 Minimiser les déclencheurs de convulsions liées à une condition photosensible: lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs ont besoin de TIC avec au moins un mode de fonctionnement qui minimise le risque de déclencher des convulsions liées à une condition photosensible. Ceci est essentiel pour les utilisateurs présentant des déclencheurs de crise photosensibles.

4.2.10 Utilisation avec des capacités cognitives, linguistiques ou d’apprentissage limitées: Les TIC fournissent des fonctions et/ou une présentation qui simplifient la compréhension, le fonctionnement et l’utilisation. Ceci est essentiel pour les utilisateurs ayant des capacités cognitives, linguistiques ou d’apprentissage limitées et aussi bénéfique à plusieurs autres dans différentes situations.

4.2.11. Confidentialité : Lorsque les TIC fournissent des fonctions d’accessibilité, elles préservent la confidentialité des utilisateurs de ces fonctions au même niveau que celle des autres utilisateurs.

Partie B - Exigences en matière d’accessibilité fonctionnelle

Explication des colonnes du tableau

Portée

Les exigences en matière d’accessibilité fonctionnelle suivantes s’appliquent aux énoncés de rendement fonctionnel de la partie A. Si une solution répond à toutes ces exigences, elle est considérée comme ayant satisfait aux énoncés de rendement fonctionnel et est donc jugée conforme à la norme EN 301 549 V3.2.1.

Clauses jugées pertinentes pour ce TIC

Clauses jugées pertinentes pour ce TIC

  • 5
  • 5.1
  • 5.1.1
  • 5.1.2
  • 5.1.2.1
  • 5.1.2.2
  • 5.1.3
  • 5.1.3.1
  • 5.1.3.2
  • 5.1.3.3
  • 5.1.3.4
  • 5.1.3.5
  • 5.1.3.6
  • 5.1.3.7
  • 5.1.3.8
  • 5.1.3.9
  • 5.1.3.10
  • 5.1.3.11
  • 5.1.3.12
  • 5.1.3.13
  • 5.1.3.14
  • 5.1.3.15
  • 5.1.3.16
  • 5.1.4
  • 5.1.5
  • 5.1.6
  • 5.1.6.1
  • 5.1.6.2
  • 5.1.7
  • 5.2
  • 5.3
  • 5.4
  • 5.5
  • 5.5.1
  • 5.5.2
  • 5.6
  • 5.6.1
  • 5.6.2
  • 5.7
  • 5.8
  • 5.9
  • 6
  • 6.1
  • 6.2
  • 6.2.1
  • 6.2.1.1
  • 6.2.1.2
  • 6.2.2
  • 6.2.2.1
  • 6.2.2.2
  • 6.2.2.3
  • 6.2.2.4
  • 6.2.3
  • 6.2.4
  • 6.5.5
  • 6.5.6
  • 6.6
  • 7
  • 7.1
  • 7.1.1
  • 7.1.2
  • 7.1.3
  • 7.1.4
  • 7.1.5
  • 7.2
  • 7.2.1
  • 7.2.2
  • 7.2.3
  • 7.3
  • 8
  • 8.1
  • 8.1.1
  • 8.1.2
  • 8.1.3
  • 8.2
  • 8.2.1
  • 8.2.1.1
  • 8.2.1.2
  • 8.2.2
  • 8.2.2.1
  • 8.2.2.2
  • 8.3
  • 8.3.0
  • 8.3.1
  • 8.3.2
  • 8.3.2.1
  • 8.3.2.2
  • 8.3.2.3
  • 8.3.2.3.1
  • 8.3.2.3.2
  • 8.3.2.3.3
  • 8.3.2.4
  • 8.3.2.5
  • 8.3.2.6
  • 8.3.3
  • 8.3.3.1
  • 8.3.3.2
  • 8.3.3.3
  • 8.3.3.3.1
  • 8.3.3.3.2
  • 8.3.4
  • 8.3.4.1
  • 8.3.4.2
  • 8.3.4.3
  • 8.3.4.3.1
  • 8.3.4.3.2
  • 8.3.4.3.3
  • 8.3.5
  • 8.3.6
  • 8.4
  • 8.4.1
  • 8.4.2
  • 8.3.4.3
  • 8.3.4.3.1
  • 8.3.4.3.2
  • 8.3.4.3.3
  • 8.3.5
  • 8.3.6
  • 8.4
  • 8.4.1
  • 8.4.2
  • 8.4.2.1
  • 8.4.2.2
  • 8.4.3
  • 8.5
  • 9
  • 9.0
  • 9.1
  • 9.1.1
  • 9.1.1.1
  • 9.1.2
  • 9.1.2.1
  • 9.1.2.2
  • 9.1.2.3
  • 9.1.2.4
  • 9.1.2.5
  • 9.1.3
  • 9.1.3.1
  • 9.1.3.2
  • 9.1.3.3
  • 9.1.3.4
  • 9.1.3.5
  • 9.1.4
  • 9.1.4.1
  • 9.1.4.2
  • 9.1.4.3
  • 9.1.4.4
  • 9.1.4.5
  • 9.1.4.10
  • 9.1.4.11
  • 9.1.4.12
  • 9.1.4.13
  • 9.2
  • 9.2.1
  • 9.2.1.1
  • 9.2.1.2
  • 9.2.1.4
  • 9.2.2
  • 9.2.2.1
  • 9.2.2.2
  • 9.2.3
  • 9.2.3.1
  • 9.2.4
  • 9.2.4.1
  • 9.2.4.2
  • 9.2.4.3
  • 9.2.4.4
  • 9.2.4.5
  • 9.2.4.6
  • 9.2.4.7
  • 9.2.5
  • 9.2.5.1
  • 9.2.5.2
  • 9.2.5.3
  • 9.2.5.4
  • 9.3
  • 9.3.1
  • 9.3.1.1
  • 9.3.1.2
  • 9.3.2
  • 9.3.2.1
  • 9.3.2.2
  • 9.3.2.3
  • 9.3.2.4
  • 9.3.3
  • 9.3.3.1
  • 9.3.3.2
  • 9.3.3.3
  • 9.3.3.4
  • 9.4
  • 9.4.1
  • 9.4.1.1
  • 9.4.1.2
  • 9.4.1.3
  • 9.5
  • 9.6
  • 10
  • 10.0
  • 10.1
  • 10.1.1
  • 10.1.1.1
  • 10.1.2
  • 10.1.2.1
  • 10.1.2.2
  • 10.1.2.3
  • 10.1.2.4
  • 10.1.2.5
  • 10.1.3
  • 10.1.3.1
  • 10.1.3.2
  • 10.1.3.3
  • 10.1.3.4
  • 10.1.3.5
  • 10.1.4
  • 10.1.4.1
  • 10.1.4.2
  • 10.1.4.3
  • 10.1.4.4
  • 10.1.4.5
  • 10.1.4.10
  • 10.1.4.11
  • 10.1.4.12
  • 10.1.4.13
  • 10.2
  • 10.2.1
  • 10.2.1.1
  • 10.2.1.2
  • 10.2.1.4
  • 10.2.2
  • 10.2.2.1
  • 10.2.2.2
  • 10.2.3
  • 10.2.3.1
  • 10.2.4
  • 10.2.4.2
  • 10.2.4.3
  • 10.2.4.4
  • 10.2.4.6
  • 10.2.4.7
  • 10.2.5
  • 10.2.5.1
  • 10.2.5.2
  • 10.2.5.3
  • 10.2.5.4
  • 10.3
  • 10.3.1
  • 10.3.1.1
  • 10.3.1.2
  • 10.3.2
  • 10.3.2.1
  • 10.3.2.2
  • 10.3.3
  • 10.3.3.1
  • 10.3.3.2
  • 10.3.3.3
  • 10.3.3.4
  • 10.4
  • 10.4.1
  • 10.4.1.1
  • 10.4.1.2
  • 10.4.1.3
  • 10.5
  • 10.6
  • 11
  • 11.0
  • 11.1
  • 11.1.1
  • 11.1.1.1
  • 11.1.1.1.1
  • 11.1.1.1.2
  • 11.1.2
  • 11.1.2.1
  • 11.1.2.1.1
  • 11.1.2.1.2
  • 11.1.2.1.2.1
  • 11.1.2.1.2.2
  • 11.1.2.2
  • 11.1.2.3
  • 11.1.2.3.1
  • 11.1.2.3.2
  • 11.1.2.4
  • 11.1.2.5
  • 11.1.3
  • 11.1.3.1
  • 11.1.3.1.1
  • 11.1.3.1.2
  • 11.1.3.2
  • 11.1.3.2.1
  • 11.1.3.2.2
  • 11.1.3.3
  • 11.1.3.4
  • 11.1.3.5
  • 11.1.3.5.1
  • 11.1.3.5.2
  • 11.1.4.1
  • 11.1.4.2
  • 11.1.4.3
  • 11.1.4.4
  • 11.1.4.4.1
  • 11.1.4.4.2
  • 11.1.4.5
  • 11.1.4.5.1
  • 11.1.4.5.2
  • 11.1.4.10
  • 11.1.4.11
  • 11.1.4.12
  • 11.1.4.13
  • 11.2
  • 11.2.1
  • 11.2.1.1
  • 11.2.1.1.1
  • 11.2.1.1.2
  • 11.2.1.2
  • 11.2.1.4
  • 11.2.1.4.1
  • 11.2.1.4.2
  • 11.2.2
  • 11.2.2.1
  • 11.2.2.2
  • 11.2.3
  • 11.2.3.1
  • 11.2.4
  • 11.2.4.3
  • 11.2.4.4
  • 11.2.4.6
  • 11.2.4.7
  • 11.2.5
  • 11.2.5.1
  • 11.2.5.2
  • 11.2.5.3
  • 11.2.5.3.1
  • 11.2.5.3.2
  • 11.2.5.4
  • 11.3
  • 11.3.1
  • 11.3.1.1
  • 11.3.1.1.1
  • 11.3.1.1.2
  • 11.3.2
  • 11.3.2.1
  • 11.3.2.2
  • 11.3.3
  • 11.3.3.1
  • 11.3.3.1.1
  • 11.3.3.1.2
  • 11.3.3.2
  • 11.3.3.3
  • 11.3.3.4
  • 11.4
  • 11.4.1
  • 11.4.1.1
  • 11.4.1.1.1
  • 11.4.1.1.2
  • 11.4.1.2
  • 11.4.1.2.1
  • 11.4.1.2.2
  • 11.4.1.3
  • 11.4.1.3.1
  • 11.4.1.3.2
  • 11.5
  • 11.5.1
  • 11.5.2
  • 11.5.2.1
  • 11.5.2.2
  • 11.5.2.3
  • 11.5.2.4
  • 11.5.2.5
  • 11.5.2.6
  • 11.5.2.7
  • 11.5.2.8
  • 11.5.2.9
  • 11.5.2.10
  • 11.5.2.11
  • 11.5.2.12
  • 11.5.2.13
  • 11.5.2.14
  • 11.5.2.15
  • 11.5.2.16
  • 11.5.2.17
  • 11.6
  • 11.6.1
  • 11.6.2
  • 11.7
  • 11.8
  • 11.8.1
  • 11.8.2
  • 11.8.3
  • 11.8.4
  • 11.8.5
  • 12
  • 12.1
  • 12.1.1
  • 12.1.2
  • 12.2
  • 12.2.1
  • 12.2.2
  • 12.2.3
  • 12.2.4
  • 13
  • 13.1
  • 13.1.1
  • 13.1.2
  • 13.1.3
  • 13.1.4
  • 13.1.5
  • 13.1.6
  • 13.2
  • 13.3

Se trouve dans cette section

5 Exigences génériques

5.1 Fonction restreinte
Clause de la norme EN 301 549Détermination de la conformité

5.1.1 Introduction (informative)

Les TIC ont des fonctions restreintes pour de nombreuses raisons, y compris en matière de conception ou de politique. Certaines fonctions des produits peuvent être restreinte parce que le produit est autonome et qu’il est interdit aux utilisateurs d’ajouter des périphériques ou des logiciels afin d’accéder à ces fonctions.

Dans la pratique, les TIC peuvent avoir une fonction restreinte même si elles n’ont pas été conçues, développées ou fournies pour être restreinte.

Les ordinateurs qui ne permettent pas aux utilisateurs finaux de régler les paramètres ou d’installer des logiciels sont fonctionnellement restreints.

C.5.1.1 Introduction (informative)

La clause 5.1.1 a une valeur informative et ne contient aucune exigence en matière de tests.

5.1.2 Généralités
Clause de la norme EN 301 549Détermination de la conformité

5.1.2.1 Fonction restreinte

Lorsque les TIC ont une fonctionnalité restreinte, elles doivent satisfaire aux exigences énoncées dans les clauses 5.2 à 13, selon le cas.

REMARQUE 1: Les TIC peuvent restreinte certaines de leurs fonctions, mais pas toutes. Seules les fonctions restreintes doivent être conformes aux exigences de la clause 5.1.

REMARQUE 2: Les dispositions de cette clause sont des exigences relatives à la fonctionnalité restreinte des TIC qui remplacent les exigences des clauses 5.2 à 13 qui stipulent spécifiquement qu’elles ne s’appliquent pas à la fonction restreinte. Cela peut être dû au fait qu’elles sont liées à la compatibilité avec la technologie d’assistance ou à la capacité de l’utilisateur d’ajuster les paramètres d’accessibilité du système dans les produits à fonction restreinte (par exemple, les produits qui empêchent l’accès au panneau de contrôle des paramètres du système).

C.5.1.2.1 Fonction restreinte

Voir les clauses C.5.2 à C.13, selon le cas.

5.1.2.2 Technologie d’assistance

Lorsque les TIC ont une fonction restreinte, cette fonction restreinte doit pouvoir fonctionner sans que l’utilisateur ait à joindre, connecter ou installer une technologie d’assistance et doit être conforme aux exigences génériques des clauses 5.1.3 à 5.1.6 selon le cas. Les casques d’écoute personnels et les boucles inductives ne doivent pas être considérés comme une technologie d’assistance aux fins de la présente clause.

C.5.1.2.2 Technologie d’assistance

Type d’évaluation

Examen

Conditions préalables

1. Les TIC ont des fonctions restreintes.

Procédure

1. Déterminer les fonctions restreintes des TIC.

2. Vérifier que les essais C.5.1.3 à C.5.1.6 peuvent être effectués sans installation d’une technologie d’assistance, à l’exception des casques personnels ou des boucles inductives.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.3 Accès non visuel
Clause de la norme EN 301 549Détermination de la conformité

5.1.3.1 Général

Lorsque des informations visuelles sont nécessaires pour permettre l’utilisation des fonctions des TIC restreintes aux technologies d’assistance pour la lecture d’écran, les TIC doivent prévoir au moins un mode de fonctionnement utilisant un accès non visuel pour permettre l’utilisation de ces fonctions.

REMARQUE 1: L’accès non visuel peut se faire sous forme audio, y compris la parole, ou sous forme tactile.

REMARQUE 2: Les informations visuelles nécessaires pour permettre l’utilisation de certaines fonctions peuvent inclure les instructions d’utilisation et l’orientation, les invites de transaction, la vérification des entrées utilisateur, les messages d’erreur et le contenu non textuel.

C.5.1.3.1 Général

Type d’évaluation

Examen

Conditions préalables

1. L’information visuelle est nécessaire pour permettre l’utilisation des fonctions des TIC restreintes à la technologie d’assistance pour la lecture d’écran.

Procédure

1. Déterminer les fonctions des TIC fermées à la lecture d’écran.

2. Vérifier qu’elles sont toutes utilisables avec un accès non visuel.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les fonctions sonores doivent être utilisées:

1. soit directement au moyen d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci;

2. soit au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

REMARQUE 1: Les mécanismes intégrés ou fournis peuvent comprendre, mais sans s’y limiter, un haut-parleur, un combiné ou casque intégré ou un autre périphérique accrédité par l’industrie.

REMARQUE 2: Par connexion accréditée par l’industrie, on entend par exemple une connexion sans fil.

REMARQUE 3: Certains utilisateurs pourraient tirer parti d’un équipement à boucle inductive.

C.5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Type d’évaluation

Inspection

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

Procédure

1. Vérifier que la sortie sonore est fournie par le biais d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci.

2. Vérifier que la sortie sonore est fournie au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

Résultat

Réussite: Les énoncés testables nos 1 ou 2 sont vrais.

Échec: Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.3.3 Corrélation de sortie sonore

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que l’information est affichée à l’écran, les TIC doivent fournir des informations auditives qui permettent à l’utilisateur de corréler l’audio avec l’information affichée à l’écran.

REMARQUE 1: De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que la Au focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2: Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées par la présentation.

C.5.1.3.3 Corrélation de sortie sonore

La clause 5.1.3.3 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit pouvoir être interrompue et répétée à la demande de l’utilisateur, lorsque les exigences de sécurité le permettent.

REMARQUE 1: Il est préférable de permettre à l’utilisateur de faire une pause plutôt que de simplement interrompre la sortie vocale.

REMARQUE 2: Il est préférable de permettre à l’utilisateur de ne répéter que la partie la plus récente plutôt que de recommencer depuis le début.

C.5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Type d’évaluation

Inspection

Conditions préalables

1. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

Procédure

1. Vérifier que la sortie vocale peut être interrompue à la demande de l’utilisateur.

2. Vérifier que la sortie vocale peut être répétée à la demande de l’utilisateur.

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: N’importe quel énoncé testable est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.3.5 Interruption automatique de la sortie vocale

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC doivent interrompre la sortie vocale actuelle lorsqu’une action de l’utilisateur se produit et lorsque la nouvelle sortie vocale débute.

REMARQUE: Lorsqu’il est essentiel que l’utilisateur entende l’intégralité du message, par exemple une instruction de sécurité ou un avertissement, les TIC peuvent devoir bloquer toute action de l’utilisateur afin que la parole ne soit pas interrompue.

C.5.1.3.5 Interruption automatique de la sortie vocale

Type d’évaluation

Inspection

Conditions préalables

1. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

Procédure

1. Déterminer les fonctions restreintes des TIC.

2. Vérifier que la sortie vocale de chaque fonction est interrompue lors d’une action de l’utilisateur.

3. Vérifier que la sortie vocale de chaque fonction est interrompue lorsqu’une nouvelle sortie vocale débute.

Résultat

Réussite: Les énoncés testables nos 1, 2 et 3 sont vrais.

Échec: Les énoncés testables nos 2 ou 3 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.3.6 Sortie vocale pour les contenus non textuels

Lorsque les TIC présentent un contenu non textuel, la solution de rechange pour le contenu non textuel doit être présentée aux utilisateurs par le biais d’une sortie vocale, sauf si le contenu non textuel est purement décoratif ou n’est utilisé que pour le formatage visuel. La sortie vocale pour les contenus non textuels doit suivre les indications relatives à « l’équivalent textuel » décrit dans les critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

C.5.1.3.6 Sortie vocale pour les contenus non textuels

Type d’évaluation

Examen

Conditions préalables

1. Le contenu non textuel est présenté aux utilisateurs via la sortie vocale.

Procédure

1. Vérifier que la sortie vocale est fournie comme solution de rechange au contenu non textuel.

2. Vérifier que le contenu non textuel n’est pas seulement présent à titre décoratif.

3. Vérifier que le contenu non textuel n’est pas utilisé uniquement pour le formatage visuel.

4. Vérifier que la sortie vocale est conforme aux indications relatives à l’” équivalent textuel » décrit dans les critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite: Les énoncés testables nos 1, 2, 3 et 4 sont vrais; ou le no 1 et le no 2 sont faux; ou le no 1 et le no 3 sont faux.

Échec: L’énoncé testable no 1 est vrai et le no 2 faux; ou le 1 est vrai et le 3 est faux; ou les nos 1, 2 et 3 sont vrais et le no 4 est faux.

Non applicable: La condition préalable 1 n’est pas remplie.

5.1.3.7 Sortie vocale pour l’information vidéo

Lorsqu’un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation de fonctions restreintes des TIC et que la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit présenter des informations équivalentes pour le contenu vidéo préenregistré.

REMARQUE: Cette sortie vocale peut prendre la forme d’une description audio ou d’une transcription auditive du contenu vidéo.

C.5.1.3.7 Sortie vocale pour l’information vidéo

Type d’évaluation

Examen

Conditions préalables

1. Un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation des fonctions restreintes des TIC.

2. La sortie vocale est fournie comme mode alternatif à une utilisation sans vision du contenu non textuel affiché sur une fonction restreinte.

Procédure

1. Vérifier que la sortie vocale présente des informations équivalentes pour le contenu vidéo préenregistré.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1: Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2: La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

C.5.1.3.8 Entrée masquée

Type d’évaluation

Examen

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. Les caractères affichés sont des caractères de masquage.

3. Toute option permettant d’autoriser une sortie sonore non privée n’a pas été activée.

Procédure

1. Vérifier que la sortie sonore n’est pas une version orale des caractères saisis.

2. Vérifier que la sortie sonore est reconnue comme étant fournie uniquement par le biais d’un mécanisme d’écoute privée.

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: Tous les énoncés testables sont faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies

5.1.3.9 Accès privé aux données personnelles

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que la sortie contient des données considérées comme étant privées conformément à la politique de confidentialité applicable, la sortie sonore correspondante ne peut être fournie que par le biais d’un mécanisme d’écoute privée qui peut être connecté sans nécessiter l’utilisation de la vision, ou par tout autre mécanisme explicitement choisi par l’utilisateur.

REMARQUE 1: Cette exigence ne s’applique pas dans les cas où les données ne sont pas définies comme étant privées conformément à la politique de confidentialité applicable ou lorsqu’il n’existe aucune politique de confidentialité applicable.

REMARQUE 2: La sortie non privée peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

C.5.1.3.9 Accès privé aux données personnelles

Type d’évaluation

Examen

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. La fonction contient des données.

3. Il existe une politique de confidentialité applicable qui considère que ces données sont privées.

Procédure

1. Vérifier que la sortie sonore est fournie uniquement par le biais d’un mécanisme d’écoute privée.

2. Vérifier que le mécanisme d’écoute privée peut être connecté sans nécessiter l’utilisation de la vision.

3. Vérifier que la sortie sonore est fournie par tout autre mécanisme qui peut être choisi par l’utilisateur.

Résultat

Réussite: Les énoncés testables nos 1, 2 et 3 sont vrais.

Échec: Les énoncés testables nos 1, 2 et 3 sont faux.

Non applicable : Les conditions préalables 1 et 3 ne sont pas remplies.

5.1.3.10 Sortie sonore non interférente

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC ne doivent pas lire automatiquement, en même temps, toute sortie audible interférente d’une durée supérieure à trois secondes.

C.5.1.3.10 Sortie sonore non interférente

Type d’évaluation

Examen

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. Les TIC lisent automatiquement la sortie audible interférente.

Procédure

1. Vérifier que la sortie audible interférente ne dure pas plus de trois secondes.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.3.11 Volume d’écoute privé

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, et ce, par le biais d’un mécanisme d’écoute privée, les TIC doivent prévoir au moins un mode de fonctionnement non visuel pour contrôler le volume.

C.5.1.3.11 Volume d’écoute privé

Type d’évaluation

Inspection

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. La sortie sonore est fournie par le biais d’un mécanisme d’écoute privée.

Procédure

1. Vérifier qu’il existe au moins un mode de fonctionnement non visuel pour régler le volume sonore.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.3.12 Volume de l’enceinte

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et qu’elle est fournie par des haut-parleurs sur les TIC, une commande de volume incrémentielle non visuelle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

REMARQUE: Pour les environnements bruyants, 65 dBA peut ne pas être suffisant.

C.5.1.3.12 Volume de l’enceinte

Type d’évaluation

Inspection et établissement de mesures

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. La sortie sonore est fournie par le biais de haut-parleurs.

Procédure

1. Vérifier qu’une commande de volume incrémentielle non visuelle est fournie.

2. Vérifier que l’amplification de sortie est disponible jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.3.13 Réinitialisation du volume

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, une fonction qui réinitialise le volume à un niveau inférieur ou égal à 65 dBA après chaque utilisation doit être fournie, sauf si les TIC sont destinées à un seul utilisateur.

REMARQUE: Une fonction permettant de désactiver la fonction de réinitialisation du volume peut être fournie afin de permettre de respecter l’exception de l’utilisateur unique.

C.5.1.3.13 Réinitialisation du volume

Type d’évaluation

Inspection et établissement de mesures

Conditions préalables

1. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

2. Les TIC ne sont pas dédiées à un seul utilisateur.

Procédure

1. Vérifier qu’une fonction qui réinitialise automatiquement le volume à un niveau de 65 dBA ou moins après chaque utilisation est fournie.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.3.14 Langues parlées

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit être dans la même langue humaine que le contenu affiché fourni, sauf:

1. pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement;

2. lorsque le contenu est généré à l’extérieur et n’est pas sous le contrôle du fournisseur de TIC, La clause présente n’est pas tenue de s’appliquer aux langues non prises en charge par le synthétiseur vocal de TIC;

3. pour les langues affichées qui ne peuvent pas être sélectionnées à l’aide d’un accès non visuel;

4. lorsque l’utilisateur choisit explicitement une langue vocale différente de la langue du contenu affiché.

C.5.1.3.14 Langues parlées

Type d’évaluation

Examen

Conditions préalables

1. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

2. La sortie vocale n’est pas utilisée pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement.

3. Le contenu n’est pas généré à l’extérieur et est sous le contrôle du fournisseur de TIC.

4. Les langues affichées peuvent être sélectionnées à l’aide d’un accès non visuel.

5. L’utilisateur n’a pas sélectionné une langue vocale différente de la langue du contenu affiché.

Procédure

1. Vérifier que la sortie vocale est dans la même langue humaine que le contenu affiché.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : Les conditions préalables 1 et 3 ne sont pas remplies.

5.1.3.15 Détermination non visuelle des erreurs

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte et qu’une erreur d’entrée est automatiquement détectée, la sortie vocale doit identifier et décrire l’élément qui est en erreur.

C.5.1.3.15 Détermination non visuelle des erreurs

Type d’évaluation

Examen

Conditions préalables

1. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

2. Une erreur de saisie est automatiquement détectée.

Procédure

1. Vérifier que la sortie vocale identifie l’élément qui est en erreur.

2. Vérifier que la sortie vocale décrit l’élément qui est en erreur.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.3.16 Reçus, billets et sorties transactionnelles

Lorsque les TIC sont restreints à l’accès visuel et qu’elles fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service, une sortie vocale doit être fournie, comprenant tous les renseignements nécessaires pour conclure ou vérifier la transaction. Dans le cas des distributeurs automatiques de billets, les copies imprimées des itinéraires et des cartes n’ont pas à être audibles.

REMARQUE: La sortie vocale peut être fournie par n’importe quel élément de l’ensemble du système de TIC.

C.5.1.3.16 Reçus, billets et sorties transactionnelles

Type d’évaluation

Examen

Conditions préalables

1. Les TIC sont restreintes à l’accès visuel.

2. Les TIC fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service.

3. Les renseignements vérifiés ne sont pas des copies imprimées des itinéraires et des cartes.

Procédure

1. Vérifier que la sortie vocale est fournie et qu’elle contient tous les renseignements nécessaires pour conclure ou vérifier la transaction.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : Les conditions préalables 1, 2 et 3 ne sont pas remplies.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante:

Ψ = (180 x H)/(π x D)

Où:

· ψ est l’angle sous-tendu en degrés;

· H est la hauteur du texte;

· D est la distance de visibilité;

· D et H sont exprimés dans les mêmes unités.

REMARQUE 1: L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

REMARQUE 2: Le tableau 5.1 et la figure 1 illustrent la relation entre la distance de vision maximale et la hauteur minimale des caractères pour l’angle sous-tendu minimal spécifié.

(Voir le tableau 5.1 et la figure 1.)

C.5.1.4 Fonction restreinte à l’agrandissement du texte

Type d’évaluation

Inspection et établissement de mesures

Conditions préalables

1. Une fonction des TIC ne prend pas en charge les fonctions d’agrandissement de la plateforme ou de la technologie d’assistance.

2. Une distance de visualisation est définie par le fournisseur.

Procédure

1. Mesurer la hauteur de la lettre H en majuscule.

2. Vérifier qu’il sous-tend un angle d’au moins 0,7 degré à la distance de visualisation définie.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : Les conditions préalables 1 et 2 ne sont pas remplies.

5.1.5 Sortie visuelle pour renseignement audio

Lorsque des renseignements audio préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, les TIC doivent fournir des renseignements visuels équivalents aux résultats sonores préenregistrés.

REMARQUE: Ce renseignement visuel peut prendre la forme de sous-titre ou de transcriptions textuelles.

C.5.1.5 Sortie visuelle pour renseignement audio

Type d’évaluation

Inspection

Conditions préalables

1. Un contenu audio préenregistré est nécessaire pour permettre l’utilisation des fonctions restreintes des TIC.

Procédure

1. Vérifier que l’information visuelle est équivalente à la sortie sonore préenregistrée.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

5.1.6 Fonctionnement sans interface clavier
Clause de la norme EN 301 549Détermination de la conformité

5.1.6.1 Fonction restreinte

Lorsque la fonction des TIC est restreinte aux claviers ou aux interfaces clavier, toutes les fonctions doivent pouvoir fonctionner sans vision, comme l’exige la clause 5.1.3.

C.5.1.6.1 Fonction restreinte

Type d’évaluation

Inspection

Conditions préalables

1. La fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier.

Procédure

1. Vérifier que toutes les fonctions sont utilisables sans vision.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.1.6.2 Focus de la saisie

Lorsque la fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier et que le point d’entrée peut être déplacé vers un élément d’interface utilisateur, il doit être possible d’éloigner le point d’entrée de cet élément en utilisant le même mécanisme, afin d’éviter de piéger le focus de la saisie.

C.5.1.6.2 Focus de la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier.

2. La Au focus d’entrée peut être déplacée vers un élément d’interface utilisateur.

Procédure

1. Vérifier qu’il est possible d’éloigner la Au focus d’entrée de cet élément en utilisant le même mécanisme.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

5.1.7 Accès sans capacité vocale

Lorsque la capacité vocale est nécessaire pour faire fonctionner des fonctions restreintes des TIC, celles-ci doivent prévoir au moins un mode de fonctionnement utilisant un autre mécanisme de saisie ne nécessitant pas la capacité vocale.

C.5.1.7 Accès sans capacité vocale

Type d’évaluation

Inspection

Conditions préalables

1. La capacité vocale est nécessaire pour permettre l’utilisation des fonctions restreintes de TIC.

Procédure

1. Vérifier que les fonctions restreintes peuvent être activées par un autre mécanisme de saisie qui ne nécessite pas la capacité vocale.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.2 Activation des caractéristiques d’accessibilité

Lorsque les TIC sont dotées de caractéristiques d’accessibilité documentées, est-il possible d’activer les caractéristiques requises pour répondre à un besoin particulier sans avoir recours à une méthode qui ne répond pas à ce besoin?

C.5.2 Activation des caractéristiques d’accessibilité

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées de caractéristiques d’accessibilité documentées pour répondre à un besoin spécifique.

Procédure

1. Vérifier qu’il est possible d’activer les caractéristiques d’accessibilité sans avoir recours à une méthode qui ne répond pas à ce besoin.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.3 Données biométriques

Lorsque les TIC utilisent des caractéristiques biologiques, elles ne s’appuient pas sur l’utilisation d’une caractéristique biologique particulière comme seul moyen d’identification de l’utilisateur ou de contrôle des TIC.

REMARQUE 1: D’autres moyens d’identification des utilisateurs ou de contrôle des TIC pourraient être non biométriques ou biométriques.

REMARQUE 2: Les méthodes biométriques fondées sur des caractéristiques biologiques dissemblables augmentent la probabilité que les personnes handicapées possèdent au moins une des caractéristiques biologiques précisées. Les empreintes digitales, les motifs rétiniens des yeux, la voix et le visage sont des exemples de caractéristiques biologiques dissemblables.

C.5.3 Données biométriques

Type d’évaluation

Examen no 1

Conditions préalables

1. Les TIC utilisent des caractéristiques biologiques pour l’identification des utilisateurs.

Procédure

1. Vérifier que plus d’un moyen peut être utilisé pour identifier l’utilisateur.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Type d’évaluation

Examen no 2

Conditions préalables

1. Les TIC utilisent des caractéristiques biologiques pour le contrôle des TIC.

Procédure

1. Vérifiez que plus d’un moyen peut être utilisé pour le contrôle des TIC.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

C.5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Type d’évaluation

Inspection

Conditions préalables

1. Les renseignements libres fournis aux fins d’accessibilité sont documentés.

2. Les TIC convertissent les renseignements ou les communications.

3. Les renseignements libres fournis aux fins d’accessibilité peuvent être contenus dans le format de destination.

4. Les renseignements libres fournis aux fins d’accessibilité peuvent être pris en charge dans le format de destination.

Procédure

1. Vérifier que les renseignements libres fournis aux fins d’accessibilité sont préservés lorsque les TIC convertissent les renseignements ou les communications.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2, 3 ou 4 n’est pas remplie.

5.5 Pièces manœuvrables
Clause de la norme EN 301 549Détermination de la conformité

5.5.1 Moyens de fonctionnement

Lorsque les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

C.5.5.1 Moyens de fonctionnement

Type d’évaluation

Examen

Conditions préalables

Les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner.

Procédure

1. Vérifier qu’il y a un autre moyen de fonctionnement qui n’exige pas de telles actions.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE: Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

C.5.5.2 Perceptibilité des pièces manœuvrables

Type d’évaluation

Examen

Conditions préalables

Les TIC sont dotées de pièces manœuvrables.

Procédure

1. Déterminer qu’il y a moyen de percevoir chaque pièce manœuvrable sans avoir besoin de la vision.

2. Vérifier que l’action associée à la pièce manœuvrable n’a pas été effectuée en utilisant les moyens de perception de chaque pièce manœuvrable de l’étape 1.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

5.6 Commandes de verrouillage ou de basculement
Clause de la norme EN 301 549Détermination de la conformité

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1: Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2: La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

C.5.6.1 État tactile ou auditif

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées d’une commande de verrouillage ou de basculement.

2. La commande de verrouillage ou de basculement se présente visuellement à l’utilisateur.

Procédure

1. Vérifier qu’au moins un mode de fonctionnement permet de déterminer au toucher l’état de toutes les commandes de verrouillage ou de basculement sans qu’il soit nécessaire d’actionner la commande.

2. Vérifier qu’au moins un mode de fonctionnement permet de déterminer au son l’état de toutes les commandes de verrouillage ou de basculement sans qu’il soit nécessaire d’actionner la commande.

Résultat

Réussite: Les énoncés testables nos 1 ou 2 sont vrais.

Échec: Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

5.6.2 État visuel

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que la commande ne se présente pas visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement permettant de déterminer visuellement l’état de la commande.

REMARQUE 1: Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2: La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. Un indicateur visuel d’état sur un clavier est un exemple de détermination de l’état d’une commande.

C.5.6.2 État visuel

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées d’une commande de verrouillage ou de basculement.

2. La commande de verrouillage ou de basculement se présente à l’utilisateur.

Procédure

1. Vérifier qu’il existe au moins un mode de fonctionnement dans lequel l’état de toutes les commandes de verrouillage ou de basculement peut être déterminé visuellement lorsque la commande se présente.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée:

1. le délai de répétition des touches doit être réglable à au moins 2 secondes;

2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.

C.5.7 Répétition des touches

Type d’évaluation

Examen

Conditions préalables

1. Les TIC sont dotées d’un clavier ou d’un pavé numérique avec une fonction de répétition des touches.

2. La fonction de répétition des touches ne peut pas être désactivée.

Procédure

1. Vérifier que le délai de répétition des touches peut être réglé à au moins 2 secondes.

2. Vérifier que la fréquence de répétition des touches peut être réglée à 2 secondes par caractère.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

5.8 Acceptation de la double frappe

Lorsque les TIC sont dotées d’un clavier ou d’un pavé numérique, le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la pression précédente, doit être réglable jusqu’à au moins 0,5 seconde.

C.5.8 Acceptation de la double frappe

Type d’évaluation

Examen

Conditions préalables

1. Les TIC sont dotées d’un clavier ou d’un pavé numérique.

Procédure

1. Vérifier qu’un mécanisme permet de régler le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la pression précédente.

2. Régler ce mécanisme à son niveau maximal.

3. Appuyer sur n’importe quelle touche.

4. Après un délai de 0,5 seconde, appuyer sur la même touche qu’à l’étape 3.

5. Vérifier si la touche de l’étape 4 a été acceptée.

Résultat

Réussite: L’énoncé testable no 1 est vrai et l’énoncé testable no 5 est faux.

Échec: L’énoncé testable no 1 est faux et l’énoncé testable no 5 est vrai.

Non applicable : La condition préalable 1 n’est pas remplie.

5.9 Actions simultanées de la part de l’utilisateur

Lorsque les TIC requièrent des actions simultanées de la part de l’utilisateur pour fonctionner, ces TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas d’actions simultanées de la part de l’utilisateur pour fonctionner.

REMARQUE: L’utilisation des deux mains pour ouvrir le couvercle d’un ordinateur portable, la pression simultanée de deux ou plusieurs touches ou le contact d’une surface avec plus d’un doigt sont des exemples d’actions simultanées de la part de l’utilisateur.

C.5.9 Actions simultanées de la part de l’utilisateur

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC ont un mode de fonctionnement exigeant des actions simultanées de la part de l’utilisateur.

Aucune

Procédure

1. Vérifier qu’il existe un mode de fonctionnement qui n’exige pas d’actions simultanées de la part de l’utilisateur.

2. Déterminer toutes les fonctions contrôlables par l’utilisateur des TIC.

3. Vérifier que chaque fonction contrôlable par l’utilisateur peut être commandée par une seule action.

Résultat

Réussite: L’énoncé testable no 3 est vrai.

Échec: L’énoncé testable no 3 est faux pour tous les modes de fonctionnement.

Non applicable : La condition préalable 1 n’est pas remplie.

6 Les TIC permettent la communication vocale bidirectionnelle.

Clause de la norme EN 301 549Détermination de la conformité

6.1 Largeur de bande sonore pour la parole

Lorsque les TIC permettent la communication vocale bidirectionnelle, pour offrir une bonne qualité sonore, elles doivent pouvoir coder et décoder la communication vocale bidirectionnelle selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

REMARQUE 1: aux fins de l’interopérabilité, la Recommandation G.722[i.21] de l’UIT-T est largement utilisée.

REMARQUE 2: lorsqu’il y a négociation de codecs, d’autres codecs normalisés tels que la Recommandation G.722.2[i.22] de l’UIT-T sont parfois utilisés afin d’éviter le transcodage.

C.6.1 Largeur de bande sonore pour la parole

Type d’évaluation

Mesure

Conditions préalables

1. Les TIC testées permettent une communication vocale bidirectionnelle.

Procédure

1. Vérifier que les TIC peuvent encoder et décoder selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

6.2 Fonctionnalité de texte en temps réel (TTR)
6.2.1 Fourniture du TTR
Clause de la norme EN 301 549Détermination de la conformité

6.2.1.1 Communication par TTR

Lorsque le mode des TIC prévoit un moyen de communication vocale bidirectionnelle, les TIC doivent fournir un moyen de communication vocale bidirectionnelle par TTR, sauf si cela nécessite des modifications de conception pour ajouter du matériel d'entrée ou de sortie aux TIC.

REMARQUE 1 : Cette exigence inclut les produits qui ne sont pas dotés de fonctionnalités d’affichage physique ou de saisie de texte mais qui ont la capacité de se connecter à des périphériques qui possèdent de telles fonctionnalités. Elle inclut également les TIC intermédiaires situés entre les points finaux de la communication.

REMARQUE 2 : Il n’est pas nécessaire d’ajouter : un écran matériel, un clavier matériel ou du matériel pour permettre de se connecter à un écran ou à un clavier, filaire ou sans fil, si ce matériel n’est normalement pas fourni.

REMARQUE 3 : Aux fins de l’interopérabilité, la Recommandation ITU-T T.140 [i.36] est largement utilisée.

C.6.2.1.1 Communication par TTR

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC testées possèdent un mode qui permet une communication vocale bidirectionnelle.

2. Les TIC sont dans le mode qui permet la communication vocale bidirectionnelle

3. Un « terminal de TTR de référence » est disponible.

Procédure

1. Vérifier que les TIC permettent une communication par TTR bidirectionnelle avec les TIC de « référence ».

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de TTR de référence » est un terminal spécialement conçu pour tester les dispositifs de TTR de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de TTR de référence » compatible.

6.2.1.2 Voix et texte simultanés

Lorsque les TIC prévoient un moyen de communication vocale bidirectionnelle et permettent aux utilisateurs de communiquer par TTR, elles doivent permettre la communication vocale et textuelle simultanément par l’intermédiaire d’une connexion utilisateur unique.

REMARQUE 1 : Dans le cas d’une communication entre plusieurs participants, comme dans un système de conférence, il est permis (mais pas obligatoire ou nécessairement recommandé) que le TTR soit traité dans un champ d’affichage unique et que « la prise de parole à tour de rôle » soit nécessaire afin d’éviter toute confusion (de la même manière que la prise de parole à tour de rôle est requise pour ceux qui présentent ou parlent avec la parole).

REMARQUE 2 : Dans le cas d’une communication entre plusieurs participants, la pratique exemplaire consiste à lever la main pour que les utilisateurs de capacité vocale et les utilisateurs du TTR soient traités de la même manière, afin que les utilisateurs de capacité vocale et de TTR soient placés dans la même file d’attente.

REMARQUE 3 : Dans le cas d’un système de conférence entre plusieurs participants dont l’une des fonctions est le clavardage – le TTR (tout comme la capacité vocale) est généralement séparé de la fonction de clavardage pour que celle-ci n’interfère pas avec le TTR (c.-à-d. les personnes peuvent envoyer des messages dans la zone de clavardage pendant qu’une personne présente ou parle avec le TTR – de la même manière que les personnes s’envoient des messages en utilisant la fonction de clavardage pendant que des personnes utilisent la parole pour parler). Les utilisateurs de TTR utiliseraient alors le TTR pour présenter et la fonction de clavardage pour envoyer des messages pendant que les autres présentent (par la parole ou le TTR).

REMARQUE 4 : La possibilité de faire fonctionner la capacité vocale et le TTR simultanément (et séparément de la fonction de clavardage) peut également permettre à la zone de TTR de prendre en charge le sous-titrage lorsque quelqu’un parle (et elle n’est donc pas utilisée pour le TTR puisque ce n’est pas au tour de l’utilisateur du TTR de prendre la parole).

REMARQUE 5 : Lorsque le logiciel côté serveur tout comme le matériel et les logiciels locaux sont nécessaires pour fournir la communication vocale, mais qu’aucune partie ne peut prendre en charge la communication vocale sans l’autre et qu’elles sont vendues comme une seule unité pour la fonction de communication vocale, les composants des logiciels locaux et du serveur sont considérés comme un seul produit.

C.6.2.1.2 Voix et texte simultanés

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC permettent la communication vocale bidirectionnelle.

2. Les TIC prévoient un moyen de communication par TTR bidirectionnelle.

Procédure

1. Vérifier que les TIC permettent la communication vocale et le TTR simultanément par l’intermédiaire d’une connexion utilisateur unique.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

6.2.2 Affichage du TTR (texte en temps réel)
Clause de la norme EN 301 549Détermination de la conformité

6.2.2.1 Affichage visuellement reconnaissable

Lorsque les TIC sont dotées de capacités d’envoi et de réception de TTR, l’affichage du texte envoyé doit être visuellement différenciable et séparé de l’affichage du texte reçu.

REMARQUE : La possibilité de choisir entre l’affichage du texte d’envoi et de réception sur une ligne ou séparément et avec des options de sélection, permet aux utilisateurs d’afficher le TTR dans le format qui leur convient le mieux. Cela permettrait aux utilisateurs de texte en braille d’utiliser un seul champ et d’intervenir à tour de rôle ainsi que de faire apparaître le texte de manière séquentielle s’ils en ont besoin ou s’ils préfèrent.

C.6.2.2.1 Affichage visuellement reconnaissable

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC testées ont des capacités d’envoi et de réception de TTR.

2. Les TIC permettent les mécanismes de TTR.

3. Un appareil de TTR de référence compatible qui utilise des mécanismes pris en charge par le système des TIC est branché à l’autre extrémité du système sous épreuve

Procédure

1. Les TIC testées sont raccordées au système des TIC auquel le terminal de référence est raccordé.

2. Les différents éléments des TIC sont fonctionnels (le raccordement est actif et les terminaux sont en mode TTR correspondant) et les deux terminaux communiquent entre eux.

3. Une séquence de textes courts est envoyée par les TIC testées.

4. Une séquence de textes courts est envoyée par le terminal de référence.

5. Vérifier, sur les TIC testées, que l’affichage du texte envoyé est visuellement différenciable et séparé de l’affichage du texte reçu.

Résultat

Réussite: L’énoncé testable no 5 est vrai.

Échec: L’énoncé testable no 5 est faux.

REMARQUE: Un terminal de référence est un terminal doté de capacités d’envoi et de réception de TTR qui utilise des mécanismes de TTR pris en charge par le système des TIC. Ce terminal de référence est la responsabilité du laboratoire d’évaluation.

6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Lorsque les TIC présentent des capacités d’envoi et de réception de TTR, la direction de l’envoi et de la réception du texte doit pouvoir être déterminée par un programme informatique, à moins que la fonction de TTR soit une fonctionnalité restreinte.

REMARQUE: Le but de cette clause est de permettre aux lecteurs d’écran de différencier le texte entrant du texte sortant lorsque la fonction de TTR est utilisée.

C.6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC testées ont des capacités d’envoi et de réception de TTR.

2. La TTR a une fonction non restreinte.

3. Un « terminal de TTR de référence » est disponible.

Procédure

1. Les TIC testées sont connectés au « terminal de TTR de référence ».

2. Les différents éléments des TIC sont fonctionnels (le raccordement est actif et les terminaux sont en mode TTR correspondant) et les deux terminaux communiquent entre eux.

3. Une séquence de textes courts est envoyée par les TIC testées.

4. Une séquence de textes courts est envoyée par le « terminal de TTR de référence ».

5. Vérifier que la direction d’envoi et réception de texte peut être déterminée par un programme informatique.

Résultat

Réussite: L’énoncé testable no 5 est vrai.

Échec: L’énoncé testable no 5 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de TTR de référence » est un terminal spécialement conçu pour tester les dispositifs de TTR de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de TTR de référence » compatible.

6.2.2.3 Identification des interlocuteurs

Lorsque les TIC sont dotées de capacités de TTR et offrent l’identification des interlocuteurs par capacité vocale, elles doivent fournir l’identification des interlocuteurs par TTR.

REMARQUE : Cela est nécessaire pour permettre aux participants utilisant la fonction de capacité vocale comme ceux utilisant la fonction de TTR de savoir qui communique à un moment donné, que ce soit par TTR ou capacité vocale.

C.6.2.2.3 Identification des interlocuteurs

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC disposent de capacités de TTR.

2. Les TIC fournissent l’identification des interlocuteurs pour la capacité vocale.

3. Un « terminal de TTR de référence » est disponible.

Procédure

1. Les TIC testées sont connectées au « terminal de TTR de référence ».

2. Le TTR est envoyé à partir du « terminal de TTR de référence ».

3. Vérifier par observation si les TIC testées permettent l’identification des interlocuteurs pour le TTR entrant.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de TTR de référence » est un terminal spécialement conçu pour tester les dispositifs de TTR de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de TTR de référence » compatible.

6.2.2.4 Indicateur visuel de l’audio avec TTR

Lorsque les TIC offrent une communication vocale bidirectionnelle dotées de capacités de TTR, elles doivent fournir un indicateur visuel en temps réel de l’activité audio à l’écran.

REMARQUE 1 : L’indicateur visuel peut être une position de caractère simple sur l’écran qui clignote pour refléter l’activité audio ou la présentation des renseignements d’une autre manière étant à la fois visible par les utilisateurs voyants et transmis aux utilisateurs sourds-aveugles qui utilisent un écran braille.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

C.6.2.2.4 Indicateur visuel de l’audio avec TTR

Inspection

Conditions préalables

1. Les TIC offrent une communication vocale bidirectionnelle.

2. Les TIC sont dotées de capacités de TTR.

Procédure

1. La TIC testée est connectée à une autre TIC fournissant une communication vocale bidirectionnelle qui est compatible avec la voix de celle-ci.

2. Une personne parle dans l’autre TIC.

3. Vérifier par observation s’il y a un indicateur visuel en temps réel de l’activité audio.

Résultat

Réussite: L’énoncé testable no 3 est vrai.

Échec: L’énoncé testable no 3 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

REMARQUE : L’indicateur devrait clignoter en temps réel d’une manière qui reflète l’activité audio.

6.2.3 Interopérabilité

Lorsque les TIC dotées d’une fonction de TTR fonctionnent avec d’autres TIC dotées d’une fonction de TTR (comme l’exige la clause 6.2.1.1), elles doivent prendre en charge au moins un des quatre mécanismes d’interopérabilité de TTR décrits ci-dessous:

1. l’interopérabilité des TIC sur le réseau téléphonique public commuté (RTPC), avec d’autres TIC qui se raccordent directement au RTPC, comme le décrit la Recommandation V.18[i.23] de l’UIT-T ou l’une de ses annexes pour les signaux de téléphonie texte à l’interface du RTPC;

2. l’interopérabilité des TIC avec d’autres TIC à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initialisation de session (PIS) et du TTR conforme à RFC 4103 [i.13] de l’IETF. Pour l’interopérabilité des TIC avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, l’ensemble des protocoles spécifiés dans TS 126 114 [i.10], TS 122 173 [i.11] et TS 134 229 [i.12] de l’ETSI décrivent la façon dont RFC 4103 [i.13] de l’IETF s’appliquerait;

3. l’interopérabilité des TIC avec d’autres TIC utilisant des technologies autres que a ou b, ci-dessus, utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible pour les environnements dans lesquels elles fonctionneront. Cette spécification commune doit comprendre une méthode permettant d’indiquer la perte ou la corruption de caractères

4. l’interopérabilité des TIC avec d’autres TIC utilisant une norme pour TTR qui a été mise en place aux fins d’utilisation dans un des environnements susmentionnés, et qui est compatible avec toutes les autres TIC actives qui prennent en charge la capacité vocale et le TTR dans l’environnement en question.

C.6.2.3 Interopérabilité

a)

Type d’évaluation

Test

Conditions préalables

1. Vérifier l’interopérabilité des TIC avec le réseau téléphonique public commuté (RTPC), le terminal de référence V.18 étant raccordé au RTPC comme il est décrit dans la Recommandation V.18 [i.23] de UIT-T ou l’une de ses annexes pour les signaux de téléphonie à l’interface RTPC.

2. Vérifier que les TIC fonctionnent avec d’autres TIC à l’aide de la technologie VoIP dotée du protocole d’initiation de session (PIS) et du texte en temps réel conforme à RFC 4103[i.13]de l’IETF;

3. Vérifier que les TIC fonctionnent avec d’autres TIC dotées de TTR conformes aux protocoles du sous-système multimédia IP (IMS) conformément aux spécifications TS 126 114[i.10], TS 122 173[i.11] et TS 134 229[i.12] de l’ETSI;

Procédure

1. Vérifier l’interopérabilité des TIC avec le réseau téléphonique public commuté (RTPC), le terminal de référence V.18 étant raccordé au RTPC comme il est décrit dans la Recommandation V.18 [i.23] de UIT-T ou l’une de ses annexes pour les signaux de téléphonie à l’interface RTPC.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de référence V.18 » est un terminal spécialement conçu pour tester les dispositifs V.18 de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de référence » compatible.

b)

Type d’évaluation

Test

Conditions préalables

1. Les TCI fournissent un moyen de communication vocale bidirectionnelle à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initialisation de session (PIS).

2. Les TIC fournissent un moyen de communication bidirectionnelle par TTR.

3. Un « terminal de TTR de référence » est disponible.

Procédure

1. Vérifier l’interopérabilité des TIC avec le « terminal de TTR de référence » à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initialisation de session (PIS) et du TTR conforme à RFC 4103 [i.13] de l’IETF.

2. Si les TIC interopèrent avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, vérifier qu’elles respectent l’ensemble des protocoles spécifiés dans TS 126 114 [i.10], TS 122 173 [i.11] et TS 134 229 [i.12] de l’ETSI décrivant la façon dont RFC 4103 [i.13] de l’IETF s’applique.

Résultat

Réussite : L’énoncé testable no 1 est vrai et si les TIC interopèrent avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, l’énoncé testable no 2 est vrai.

Échec : L’énoncé testable no 1 est faux ou, si les TIC interopèrent avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, l’énoncé testable no 2 est faux.

Non applicable: La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de TTR de référence » est un terminal spécialement conçu pour tester les dispositifs de TTR de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de TTR de référence » compatible.

c)

Type d’évaluation

Test

Conditions préalables

1. Les TCI fournissent un moyen de communication vocale bidirectionnelle à l’aide de technologies autres que le RTPC ou Voix sur IP (VoIP) dotée du protocole d’initialisation de session (PIS).

2. Les TIC fournissent un moyen de communication bidirectionnelle par TTR.

3. Un « terminal de TTR de référence » est disponible pour ce mode de communication par TTR.

Procédure

1. Vérifier l’interopérabilité des TIC avec le « terminal de TTR de référence » utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible pour les environnements dans lesquels les TIC fonctionneront.

2. Vérifier que la spécification commune dans l’énoncé testable no 1 comprend une méthode permettant d’indiquer la perte ou la corruption de caractères.

Résultat

Réussite : Les énoncés testables nos 1 et 2 sont vrais.

Échec : Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Un « terminal de TTR de référence » est un terminal spécialement conçu pour tester les dispositifs de TTR de manière à confirmer leur fonctionnalité et leur interopérabilité. Ces terminaux sont généralement créés par une entité de normalisation nationale ou internationale afin que tous les tests soient effectués avec un « terminal de TTR de référence » compatible.

d)

Type d’évaluation

Test

Conditions préalables

1. Les TIC fournissent un moyen de communication vocale bidirectionnelle.

2. Les TIC fournissent un moyen de communication par TTR bidirectionnelle.

3. Un « terminal de TTR de référence » est disponible utilisant la nouvelle norme de TTR.

Procédure

1. Vérifier que les TIC testées interopèrent avec le « terminal de TTR de référence » pour la nouvelle norme de TTR qui a été mise en place aux fins d’utilisation.

2. Vérifier que la nouvelle norme de TTR est supporté par toutes les autres TIC actives qui supportent la capacité vocale et le TTR dans le même environnement.

Résultat

Réussite : Les énoncés testables nos 1 et 2 sont vrais.

Échec : Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

6.2.4 Réactivité du TTR (texte en temps réel)

Lorsque les TIC permettent la saisie de TTR, cette saisie doit être transmise au réseau des TIC ou à la plateforme sur laquelle fonctionne les TIC dans un délai de 500 ms à compter du moment où la plus petite unité de saisie de texte fiable est accessible aux TIC jusqu’à la fin de la transmission. Les retards attribuables à la performance de la plateforme ou du réseau ne doivent pas être inclus dans la limite de 500 ms.

REMARQUE 1 : Pour la saisie de caractère par caractère, la « plus petite unité de saisie de texte fiable » serait un caractère. Pour la prédiction des mots, ce serait un mot. Pour certains systèmes de reconnaissance vocale, le texte pourrait ne pas quitter le logiciel de reconnaissance tant qu’un mot entier (ou une expression entière) n’a pas été prononcé. Dans ce cas, la plus petite unité de saisie de texte fiable accessible aux TIC serait le mot (ou la phrase).

REMARQUE 2 : La limite de 500 ms permet de conserver en mémoire tampon les caractères avant leur transmission de sorte que la transmission caractère par caractère ne soit pas nécessaire à moins qu’ils soient générés plus lentement qu’un caractère par 500 ms.

REMARQUE 3 : Un délai de 300 ms, ou moins, produit une meilleure impression de fluidité pour l'utilisateur.

C.6.2.4 Réactivité du TTR (texte en temps réel)

Type d’évaluation

Inspection des mesures ou examen

Conditions préalables

1. Les TIC testées permettent la saisie de TTR.

2. Les TIC testée sont connectées à un dispositif ou un logiciel qui peut déterminer quand les caractères sont transmis.

Procédure

1. Saisir des caractères uniques dans le terminal testé.

2. Vérifier le temps à laquelle la saisie a eu lieu (p. ex. les caractères apparaissent sur l’écran).

3. Vérifier le délai entre le moment où la saisie est exécutée dans les TIC testées et le moment où le texte est transmis au réseau ou à la plate-forme des TIC.

Résultat

Réussite : Le résultat de l’énoncé testable no 3 est inférieur ou égal à 500 ms.

Échec : Le résultat de l’énoncé testable no 3 est supérieur à 500 ms.

Non applicable : La condition préalable 1 n’est pas remplie.

Non testable : La condition préalable 3 n’est pas remplie.

REMARQUE : Comme l’indiquent les remarques à la clause 6.2.4, la détermination du moment où la saisie a été exécutée peut différer selon le système TTR testé.

6.3 Identification de l’appelant

Lorsque les TIC sont dotées de la fonction d’identification de l’appelant ou d’une fonction de télécommunications similaire, la fonction d’identification de l’appelant ou de télécommunications similaire doit être offerte en mode textuel ainsi qu’être déterminable par un programme informatique, à moins que la fonction ne soit restreinte.

C.6.3 Identification de l’appelant

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC permettent la fonction d’identification de l’appelant ou de télécommunications similaire.

Procédure

1. Vérifier que les renseignements fournis par chaque fonction sont accessibles en mode textuel.

2. Vérifier que les renseignements fournis par chaque fonction sont déterminables par la programmation.

Résultat

Réussite : L’énoncé testable no 1 est vrai et l’énoncé testable no 2 est vrai ou la fonction est restreinte.

Échec : L’énoncé testable no 1 est faux ou l’énoncé testable no 2 est faux lorsque la fonction n’est pas restreinte.

Non applicable : La condition préalable 1 n’est pas remplie.

6.4 Autres solutions de services vocaux

Lorsque les TIC permettent la communication vocale en temps réel ainsi que la messagerie vocale, la réception automatique ou la réponse vocale interactive, elles doivent permettre à l’utilisateur d’accéder aux renseignements et d’exécuter les tâches sans recourir à l’ouïe ou à la parole.

REMARQUE 1: Les tâches qui impliquent à la fois l’utilisation de l'interface et la perception des informations exigeraient que celles-ci soient accessibles sans recourir à la parole ou à l’ouïe.

REMARQUE 2: Des solutions permettant de traiter les supports sons, texte et vidéo en temps réel pourraient répondre au besoin susmentionné.

C.6.4 Autres solutions de services vocaux

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC permettent la communication vocale en temps réel.

2. Les TIC permettent la messagerie vocale, la réception automatique ou la réponse vocale interactive.

Procédure

1. Vérifier que les TIC permettent à l’utilisateur d’accéder aux renseignements sans recourir à l’ouïe ou à la parole.

2. Vérifier que l’utilisateur peut exécuter les tâches que permet le système sans avoir à recourir à l’ouïe ou à la parole.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

6.5 Communication vidéo
Clause de la norme EN 301 549Détermination de la conformité

6.5.1 Généralités (information)

La clause 6.5 (Communication vidéo) décrit les exigences fonctionnelles supportant les utilisateurs qui communiquent en utilisant le langage des signes et la lecture labiale. Pour ces utilisateurs une résolution au moins QVGA (320 x 240), une vitesse de défilement d’au moins 20 images par seconde et un écart entre le son et la vidéo de 100 ms ou moins permettent une bonne utilisabilité.

L'augmentation de la résolution et de la vitesse de défilement des images améliore encore plus le langage des signes (en particulier l'orthographe digitale) et la lecture labiale, la vitesse de défilement des images étant plus importante que la résolution.

Les écarts temporels entre l’audio et la vidéo (asynchronicité) peuvent avoir un impact important sur la lecture labiale - une vidéo en retard sur l’audio a un effet négatif plus important.

La latence de bout en bout peut être un problème dans la communication vidéo (signes). Des valeurs d’écart inférieur à 400 ms avec une augmentation allant jusqu’à 100 ms sont préférables. L’écart global dépend de plusieurs facteurs, dont le délai de transmission du réseau et le traitement vidéo. Voilà pourquoi il est impossible d’établir une exigence testable des valeurs minimales d’écart global.

REMARQUE : La Recommandation UIT-T F.703 [i.37] définit et donne les exigences relatives à la conversation totale qui a trait à l’intégration de l’audio, au TTR et à la vidéo dans une connexion utilisateur unique.

C.6.5.1 Généralités (information)

La clause 6.5.1 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

6.5.2 Résolution

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles:

1. doivent prendre en charge au moins la résolution QVGA;

2. doivent de préférence prendre en charge au moins la résolution VGA.

C.6.5.2 Résolution

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC permettent la communication vocale bidirectionnelle.

2. Les TIC permettent la fonctionnalité vidéo en temps réel.

Procédure

1. Vérifier que la résolution de la communication vidéo est de résolution QVGA ou supérieure.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

6.5.3 Vitesse de défilement des images

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles:

1. doivent prendre en charge une vitesse de défilement d’au moins 20 images par seconde (IPS);

2. doivent de préférence prendre en charge une vitesse de défilement d’au moins 30 images par seconde (IPS) avec ou sans langage gestuel dans le flux vidéo.

C.6.5.3 Vitesse de défilement des images

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC permettent la communication vocale bidirectionnelle.

2. Les TIC permettent la fonctionnalité vidéo en temps réel.

Procédure

1. Vérifier que la vitesse de défilement des images de la communication vidéo est égale ou supérieure à 12 images par seconde.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

6.5.4 Synchronisation entre le son et la vidéo

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles doivent présenter à l’utilisateur un écart temporel maximal de 100 ms entre la parole et la vidéo.

REMARQUE : Des recherches récentes montrent que si l’audio mène la vidéo, l’intelligibilité en souffre beaucoup plus que dans le cas inverse.

C.6.5.4 Synchronisation entre le son et la vidéo

Type d’évaluation

Mesure

Conditions préalables

1. Les TIC permettent la communication vocale bidirectionnelle.

2. Les TIC permettent la fonctionnalité vidéo en temps réel.

Procédure

1. Vérifier que l’écart temporel entre la parole et la vidéo présentée à l’utilisateur est égal ou inférieur à 100 ms.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

6.5.5 Indicateur visuel de l’audio avec vidéo

Lorsque les TIC offrent une communication vocale bidirectionnelle et qu’elles comprennent une fonctionnalité de vidéo en temps réel, elles doivent fournir un indicateur visuel en temps réel de l’activité audio.

REMARQUE 1 : L’indicateur visuel peut être un simple point visuel, une LED ou d’autre type d’indicateur marche-arrêt, qui clignote pour refléter l’activité audio.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

C.6.5.5 Indicateur visuel de l’audio avec vidéo

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC prévoient une communication vocale bidirectionnelle.

2. Les TIC comprennent une fonctionnalité de vidéo en temps réel.

Procédure

1. La TIC testée est connectée à une autre TIC fournissant une communication vocale bidirectionnelle compatible avec la communication vocale de la TIC testée.

2. Une personne parle dans l’autre TIC.

3. Vérifier par observation s’il y a un indicateur visuel en temps réel de l’activité audio.

Résultat

Réussite : L’énoncé testable no 3 est vrai.

Échec : L’énoncé testable no 3 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

REMARQUE : L’indicateur devrait clignoter en temps réel d’une manière qui reflète l’activité audio.

6.5.6 Identification des interlocuteurs avec communication vidéo (langue des signes)

Lorsque les TIC offrent une fonction d’identification des interlocuteurs pour les utilisateurs de la capacité vocale, elles doivent fournir un moyen d’identification des interlocuteurs pour les utilisateurs de signes en temps réel et pour le langage des signes dès que celui-ci est utilisé.

REMARQUE 1 : L’identification des interlocuteurs peut se trouver au même emplacement que celui des utilisateurs de capacité vocale dans le cas des appels avec plusieurs interlocuteurs.

REMARQUE 2 : Ce mécanisme peut être déclenché manuellement par un utilisateur ou automatiquement lorsque cela est techniquement réalisable.

C.6.5.6 Identification des interlocuteurs avec communication vidéo (langue des signes)

Type d’évaluation

Mesure

Conditions préalables

1. Les TIC prévoient une communication vocale bidirectionnelle

2. Les TIC comprennent la vidéo en temps réel.

Procédure

1. La TIC testée est connectée à une TIC compatible qui supporte la vidéo et une personne communique en langue des signes.

2. Vérifier par l'observation si les TIC testées fournissent un moyen d’identification des interlocuteurs pour les utilisateurs de la langue des signes.

Résultat

Réussite : L’énoncé testable no 2 est vrai.

Échec : L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Lorsque les TIC offrent une fonction d’identification des interlocuteurs pour les utilisateurs de la capacité vocale, elles doivent fournir un moyen d’identification des interlocuteurs pour les utilisateurs de signes en temps réel et pour le langage des signes dès que celui-ci est utilisé.

REMARQUE 1 : L’identification des interlocuteurs peut se trouver au même emplacement que celui des utilisateurs de capacité vocale dans le cas des appels avec plusieurs interlocuteurs.

REMARQUE 2 : Ce mécanisme peut être déclenché manuellement par un utilisateur ou automatiquement lorsque cela est techniquement réalisable.

6.6 Autres solutions de services vidéo

Lorsque les TIC sont dotées de la communication vidéo en temps réel ainsi que d’un répondeur, d’un standard automatique ou de moyens de réponse interactifs, elles doivent permettre aux utilisateurs d’accéder aux renseignements et d’exécuter les tâches liées à ces moyens:

1. pour des renseignements audibles, sans recourir à l’ouïe;

2. pour les commandes vocales, sans recourir à la parole;

3. pour les renseignements visuels, sans recourir à la vision.

REMARQUE: Les solutions pouvant produire des sous-titres en temps réel ou traiter du texte en temps réel pourraient répondre au besoin susmentionné.

C.6.6 Autres solutions de services vidéo

La clause 6.6 n’a qu’une valeur informative et ne contient aucune exigence relative aux tests de conformité.

7 TIC avec capacités vidéo

7.1 Technologie de traitement des sous-titres
Clause de la norme EN 301 549Détermination de la conformité

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1: Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un dispositif braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

REMARQUE 3 : La clause 7.1.1 fait référence à la capacité du lecteur d’afficher des sous-titres. Les clauses 9.1.2.2, 10.1.2.2 et 11.1.2.2 font référence à la fourniture de sous-titres pour le contenu (la vidéo).

C.7.1.1 Lecture du sous-titrage

Type d’évaluation

Examen no 1

Conditions préalables

1. Les TIC affichent ou traitent la vidéo et la synchronisation sonore.

2. Les sous-titres sont fournis dans la vidéo.

Procédure

1. Vérifier qu’il y a un mécanisme d’affichage des sous-titres.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Type d’évaluation

Examen no 2

Conditions préalables

1. Les TIC affichent ou traitent la vidéo et la synchronisation sonore.

2. Les sous-titres sont fournis dans le contenu.

Procédure

1. Vérifier qu’il y a un mécanisme d’affichage des sous-titres.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

7.1.2 Synchronisation du sous-titrage

Lorsque les TIC affichent des sous-titres, le mécanisme d’affichage doit préserver la synchronisation entre le son et les sous-titres correspondants comme suit :

  • Sous-titres dans le matériel enregistré : dans les 100 ms de l’estampille temporelle du sous-titre.
  • Sous-titres en direct : dans les 100 ms suivant la disponibilité du sous-titre pour le lecteur.

C.7.1.2 Synchronisation du sous-titrage

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées d’un mécanisme d’affichage des sous-titres.

Procédure

1. Vérifier que le mécanisme d’affichage des sous-titres préserve la synchronisation entre le son et les sous-titres correspondants dans un dixième de seconde de l’estampille temporelle du sous-titre ou suivant la disponibilité du sous-titre pour le lecteur dans le cas d’un sous-titre en direct.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

7.1.3 Préservation du sous-titrage

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

D’autres aspects d’affichage du texte (p. ex. le positionnement à l’écran, la couleur et le style du texte ainsi que la police de caractères) peuvent être significatifs selon les conventions régionales. La modification de ces aspects pourrait en changer le sens et devrait être évitée dans la mesure du possible.

C.7.1.3 Préservation du sous-titrage

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC transmettent des conversions ou des enregistrements vidéo avec synchronisation sonore.

Procédure

1. Vérifier que les TIC préservent les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

7.1.4 Caractéristiques des sous-titres

Lorsque les TIC affichent des sous-titres, elles doivent permettre à l’utilisateur d’adapter les caractéristiques affichées des sous-titres à ses besoins individuels, sauf lorsque les sous-titres sont affichés sous forme de caractères non modifiables.

REMARQUE 1 : La définition de la couleur d’arrière-plan et d’avant-plan des sous-titres, du type de police, de l’opacité de la zone d’arrière-plan des sous-titres et du contour ou de la bordure des polices peut contribuer à répondre à cette exigence.

REMARQUE 2 : Les sous-titres qui sont des images bitmap sont des exemples de caractères non modifiables.

C.7.1.4 Caractéristiques des sous-titres

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC affichent les sous-titres.

2. Les sous-titres testés sont affichés sous forme de caractères modifiables.

Procédure

1. Vérifier que les TIC permettent à l’utilisateur d’adapter les caractéristiques affichées des sous-titres à ses besoins individuels.1. Check that the ICT provides a way for the user to adapt the displayed characteristics of captions to their individual requirements.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

7.1.5 Sous-titres vocaux

Lorsque les TIC affichent des vidéos avec son synchronisé, elles doivent fournir un mode de fonctionnement qui fournit une sortie vocale pour les sous-titres disponibles, sauf lorsque le contenu des sous-titres affichés n’est pas déterminable par programmation.

REMARQUE 1 : Il est préférable pour la plupart des utilisateurs de pouvoir gérer la gamme de sortie vocale pour les sous-titres vocaux indépendamment de la capacité vocale générale des TIC. Cela est possible lorsque le fichier audio avec sous-titres vocaux est reçu dans une piste audio distincte puis mixé sur l’appareil des utilisateurs.

REMARQUE 2 : Présenter la piste audio distincte avec des sous-titres vocaux en synchronisme avec les sous-titres affichés améliore la compréhension des sous-titres.

REMARQUE 3 : Fournir les sous-titres sous forme de flux de texte distincts facilite la conversion des textes respectifs en audio.

REMARQUE 4 : Les sous-titres qui sont des images bitmap sont des exemples pour lesquels le contenu de sous-titres affichés n’est pas déterminable par programmation.

C.7.1.5 Sous-titres vocaux

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC affichent des vidéos avec son synchronisé.

2. Le contenu des sous-titres testés est déterminable par programmation.

Procédure

1. Vérifier qu’il existe un mode de fonctionnement fournissant une sortie vocale pour les sous-titres disponibles.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

7.2 Technologie de description audio
Clause de la norme EN 301 549Détermination de la conformité

7.2.1 Lecture de la description audio

Lorsque les TIC affichent la vidéo avec synchronisation sonore, elles doivent fournir un mécanisme permettant de sélectionner et de lire la description audio accessible pour le canal sonore par défaut.

Lorsque les technologies vidéo ne fournissent pas de mécanismes explicites et distincts de description audio, une TIC est réputée répondre à ce besoin si elle permet à l’utilisateur de sélectionner et de lire plusieurs pistes sonores.

REMARQUE 1: Dans ce cas, le contenu vidéo peut présenter la description audio dans l’une des pistes sonores offertes.

REMARQUE 2: Les descriptions audio dans les médias numériques incluent parfois des renseignements permettant des descriptions plus longues que les temps morts entre les répliques. La fonction de description audio prolongée dans les lecteurs multimédias numériques est utile, en particulier pour les médias numériques consultés de manière individuelle.

C.7.2.1 Lecture de la description audio

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC affichent la vidéo et la synchronisation sonore.

Procédure

1. Vérifier qu’il existe un mécanisme explicite et distinct de description audio.

2. Vérifier qu’il existe un mécanisme permettant de sélectionner et de lire la description audio sur le canal sonore par défaut.

3. Vérifier que les TIC permettent à l’utilisateur de sélectionner et de lire plusieurs pistes sonores.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais, ou l’énoncé testable no 1 est faux et l’énoncé testable no 3 est vrai.

Échec: L’énoncé testable no 1 est vrai et l’énoncé testable no 2 est faux ou l’énoncé testable no 1 est faux et l’énoncé testable no 3 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

7.2.2 Synchronisation de la description audio

Lorsque les TIC sont dotées d’un mécanisme de lecture de description sonore, elles doivent préserver la synchronisation entre le contenu sonore ou visuel et la description sonore correspondante.

C.7.2.2 Synchronisation de la description audio

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées d’un mécanisme de lecture de la description audio.

Procédure

1. Vérifier que la synchronisation entre le contenu sonore ou visuel et la description audio correspondante sont préservées.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

C.7.2.3 Préservation de la description audio

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC transmettent des conversions ou des enregistrements vidéo avec synchronisation sonore.

Procédure

1. Vérifier que les TIC préservent la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1: Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2: Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3: Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio.

C.7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC affichent principalement du contenu vidéo et du contenu sonore associé

Procédure

1. Vérifier que les commandes de l’utilisateur pour activer le sous-titrage et les descriptions audio sont fournies à l’utilisateur au même niveau d’interaction que les principales commandes médias.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8 Matériel

8.1 Généralités
Clause de la norme EN 301 549Détermination de la conformité

8.1.1 Exigences génériques

Les exigences génériques de la clause 5 s’appliquent également aux TIC qui sont du matériel.

C.8.1.1 Exigences génériques

La clause 8.1.1 ne contient aucune exigence en matière de test.

8.1.2 Raccordements standard

Lorsque les TIC fournissent des points de raccordement de dispositif d’entrée ou de sortie à l’utilisateur, elle comprend au moins un raccordement d’entrée ou de sortie conforme à un format standard de l’industrie librement accessible, directement ou au moyen d’adaptateurs offerts sur le marché.

REMARQUE 1: L’exigence de raccordements standard vise à garantir la compatibilité avec les technologies d’assistance.

REMARQUE 2: Le terme raccordement s’applique à la fois aux raccordements matériels et sans fil.

REMARQUE 3: Les raccordements USB et Bluetooth sont des exemples de formats standard de l’industrie librement accessibles.

C.8.1.2 Raccordements standard

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC fournissent des points de raccordement d’entrée ou de sortie à l’utilisateur.

Procédure

1. Vérifier qu’un type de raccordement est conforme à un format standard de l’industrie librement accessible.

2. Vérifier qu’un type de raccordement est conforme à un format standard de l’industrie librement accessible au moyen d’adaptateurs offerts sur le marché.

Résultat

Réussite: Les énoncés testables nos 1 ou 2 sont vrais.

Échec: Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

REMARQUE: Les raccordements peuvent être matériels ou sans-fil.

8.1.3 Couleur

Lorsque les TIC sont dotées d’aspects matériels utilisant la couleur, la couleur n’est pas utilisée comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

C.8.1.3 Couleur

Type d’évaluation

Inspection

Conditions préalables

1. Les aspects matériels des TIC véhiculent de l’information visuelle à l’aide d’un code de couleur comme moyen d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

Procédure

1. Vérifier qu’une autre forme de codage visuel est fournie.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.2 Produits matériels avec sortie vocale
8.2.1 Gain de volume de la parole
Clause de la norme EN 301 549Détermination de la conformité

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE: Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965[i.2] sont réputés conformes à cette exigence.

C.8.2.1.1 Gamme de volume de la parole

Type d’évaluation

Inspection reposant sur les mesures

Conditions préalables

1. Le matériel de TIC est doté d’une sortie vocale.

Procédure

1. Vérifier que les TIC sont conformes à la norme ANSI/TIA-4965[i.2].

2. Mesurer le niveau (en dB) de la sortie vocale au réglage le plus bas.

3. Mesurer le niveau (en dB) de la sortie vocale au réglage le plus élevé.

4. Vérifier que la gamme entre 1 et 2 est supérieure ou égale à 18 dB.

Résultat

Réussite: Les énoncés testables nos 1 ou 4 sont vrais.

Échec: Les énoncés testables nos 1 et 4 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

C.8.2.1.2 Réglage incrémentiel du volume

Type d’évaluation

Inspection reposant sur les mesures

Conditions préalables

1. Le matériel de TIC est doté d’une sortie vocale.

2. Le réglage du volume est incrémentiel.

Procédure

1. Mesurer le niveau (en dB) de la sortie vocale au réglage le plus bas.

2. Vérifier si une étape intermédiaire fournit un niveau de 12 dB au-dessus du niveau de volume le plus bas mesuré à l’étape 1.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.2.2 Couplage magnétique
Clause de la norme EN 301 549Détermination de la conformité

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille et qui porte le symbole « T » spécifié dans la norme ETS 300 381[1] de l’ETSI, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1[2] de l’ETSI.

REMARQUE 1: Les TIC répondant aux exigences de la norme TIA-1083-A[i.24] sont réputées conformes aux exigences de la présente clause.

REMARQUE 2 : Le couplage magnétique est également appelé couplage inductif pour bobine en T.

C.8.2.2.1 Dispositifs de téléphonie fixe

Type d’évaluation

Inspection reposant sur les données de mesure

Conditions préalables

1. Le matériel de TIC est un dispositif de communication fixe avec sortie audio qui est normalement tenu à l’oreille.

Procédure

1. Vérifier que le matériel de TIC est conforme à la norme TIA-1083[i.24].

2. Les mesures effectuées conformément à la norme ES 200 381-1[2] de l’ETSI indiquent que les exigences définies dans cette norme sont satisfaites.

3. Les TIC portent le symbole « T » spécifié dans la norme ETS 300 381[1] de l’ETSI.

Résultat

Réussite: Les énoncés testables nos 1 ou 2 sont vrais et l’énoncé testable no 3 est vrai.

Échec: Les énoncés testables nos 1 et 2 sont faux ou l’énoncé testable no 3 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2[3] de l’ETSI.

REMARQUE: Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19[i.1] sont réputées conformes aux exigences de la présente clause.

C.8.2.2.2 Dispositifs de communication sans fil

Type d’évaluation

Inspection reposant sur les les données de mesure

Conditions préalables

1. Le matériel de TIC est un dispositif de communication sans fil qui est normalement tenu à l’oreille.

Procédure

1. Vérifier que le matériel de TIC est conforme à la norme ANSI/IEEE C63.19[i.1].

2. Vérifier que les TIC fournissent un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2[3] de l’ETSI.

Résultat

Réussite: Les énoncés testables nos 1 ou 2 sont vrais.

Échec: Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.3 TIC fixes
Clause de la norme EN 301 549Détermination de la conformité

8.3.0 Généralités (information)

Le présent document définit les dimensions pour accéder aux TIC fixes qui peuvent être placées dans un environnement bâti, mais ne définit pas les normes de l’environnement bâti en général.

Le champ d’application inclut les TIC fixes, dont les planchers et les espaces de circulation font « partie intégrante » (généralement les kiosques et les cabines), et où il existe des plages de portée externe qui sont importantes pour le fonctionnement des TIC fixes.

Les clauses 8.3.2 à 8.3.4 précisent les limites obligatoires pour la hauteur maximale et minimale des pièces manœuvrables et des écrans. Selon les dimensions indiquées à la figure 53 de la norme ISO 21542:2011 [i.34], il est recommandé que la portée possible en hauteur soit ramenée :

  • aux hauteurs minimale et maximale des pièces manœuvrables : 800 mm et 1100 mm respectivement, et.
  • aux hauteurs minimale et maximale des écrans : 1200 mm et 1400 mm respectivement.

C.8.3.0 Généralités (information)

La clause 8.3.0 n’a qu’une valeur informative et ne contient aucune exigence relative aux tests de conformité.

8.3.1 Portée avant ou latérale

Les TIC fixes doivent être conformes à la clause 8.3.2 ou à la clause 8.3.3.

REMARQUE 1 : Cela n'empêche pas de se conformer aux deux clauses.

REMARQUE 2 : Les dimensions indiquées dans les clauses 407.8.3 et 407.8.2 de l’article 508 du Rehabilitation Act, telles que publiées en janvier 2017 [i.25], sont identiques à celles indiquées dans les clauses 8.3.2 et 8.3.3 du présent document.

REMARQUE 3 : L’accès physique à une TIC fixe dépend des dimensions de la TIC et de l’environnement dans lequel elle est installée et exploitée. La clause 8.3 ne s’applique pas à l’accessibilité de l’environnement physique extérieur à la TIC.

C.8.3.1 Portée avant ou latérale

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes.

Procédure

1. Vérifier si les TIC sont conformes à la clause 8.3.2.2.

2. Vérifier si les TIC sont conformes à la clause 8.3.2.3.

Résultat

Réussite : L’énoncé testable no 1 ou no 2 est vrais

Échec : Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.3.2 Portée avant
Clause de la norme EN 301 549Détermination de la conformité

8.3.2.1 Hauteur maximum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins une pièce manœuvrable de chaque type ne doit pas être située à plus de 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès. Cela est illustré à la figure 2.

8.3.2.1 Hauteur maximum de la portée avant libre

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Aucune pièce des TIC fixes n’obstrue la portée avant.

Procédure

1. Vérifier qu’au moins une pièce manœuvrable de chaque type n’est pas située à plus de 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.2 Hauteur minimum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins une pièce manœuvrable de chaque type ne doit pas être située à moins de 380 mm (15 po) au-dessus du plancher de l’espace d’accès. Cela est illustré à la figure 2.

C.8.3.2.2 Hauteur minimum de la portée avant libre

Type d’évaluation

Inspection and mesures

Conditions préalables

1. Les TIC sont fixes.

2. Aucune pièce des TIC fixes n’obstrue la portée avant.

Procédure

1. Vérifier qu’au moins une pièce manœuvrable de chaque type n’est pas située à moins de 380 mm (15 po) au-dessus du plancher de l’espace d’accès

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.3 Portée avant obstruée
Clause de la norme EN 301 549Détermination de la conformité

8.3.2.3.1 Espace libre

Lorsqu’une obstruction faisant partie intégrante des TIC fixes empêche l’accès à tout type de pièce manœuvrable, les TIC doivent prévoir un espace libre qui s’étend sous l’élément obstruant sur une distance qui n’est pas inférieure à la profondeur d’atteinte requise au-dessus de l’obstruction.

REMARQUE : Le fait de prévoir un libre « accès à tout type de partie manœuvrable » garantit qu’un utilisateur pourra accéder à au moins une pièce manœuvrable de chaque type.

C.8.3.2.3.1 Espace libre

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes.

2. Une obstruction faisant partie intégrante des TIC empêche l’accès à tout type de pièce manœuvrable.

Procédure

1. Vérifier que les TIC prévoient un espace libre qui s’étend sous l’élément obstruant sur une distance qui n’est pas inférieure à la profondeur d’atteinte requise au-dessus de l’obstruction.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.3.2 Portée avant obstruée (<510 mm)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins une pièce manœuvrable de chaque type ne doit pas être supérieure à 1220 mm (48 po) au-dessus du point de contact au sol des TIC. Cela est illustré à la figure 3 (a).

C.8.3.2.3.2 Portée avant obstruée (<510 mm)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Une partie intégrante des TIC fixes forme une obstruction de moins de 510 mm (20 pouces) de profondeur.

Procédure

1. Vérifier que la portée avant à au moins une pièce manœuvrable de chaque type n’est pas supérieure à 1220 mm (48 pouces) au-dessus du contact avec le sol des TIC.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.3.3 Portée avant obstruée (<635 mm)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins une pièce manœuvrable de chaque type ne doit pas être supérieure à 1120 mm (44 po) au-dessus du point de contact au sol des TIC. Cela est illustré à la figure 3 (b).

8.3.2.3.3 Portée avant obstruée (<635 mm)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Une partie intégrante des TIC fixes forme une obstruction de pas moins de 510 mm (20 pouces) mais de moins de 635 mm (25 pouces) de profondeur.

Procédure

1. Vérifier que la portée avant à au moins une pièce manœuvrable de chaque type n’est pas supérieure à 1120 mm (44 pouces) au-dessus du contact avec le sol des TIC.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.4 Largeur libre pour les genoux et les pieds

Lorsque l’espace sous un obstacle faisant partie intégrante des TIC fait partie de l’espace d’accès, la largeur libre doit être d’au moins 760 mm (30 po).

C.8.3.2.4 Largeur libre pour les genoux et les pieds

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. L’espace sous un obstacle faisant partie intégrante des TIC fait partie d’un espace d’accès.

Procédure

1. Vérifier que la largeur de l’espace libre pour les genoux est supérieure à 760 mm (30 po).

2. Vérifier que la largeur de l’espace libre pour les pieds est supérieure à 760 mm (30 po).

Résultat

Réussite : Les énoncés testables nos 1 et 2 sont vrais.

Échec : Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.2.5 Espace libre pour les pieds

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle d’au moins 230 mm (9 po) au-dessus du plancher est considéré comme un espace libre pour les pieds et il devrait :

1. s’étendre sur au plus 635 mm (25 po) sous tout l’obstacle;

2. procurer un espace d’au moins 430 mm (17 po) de profondeur et 230 mm (9 po) au-dessus du plancher sous l’obstacle;

3. ne pas dépasser de plus de 150 mm (6 po) toute obstruction à 230 mm (9 po) au-dessus du plancher.

Cela est illustré à la figure 4.

C.8.3.2.5 Espace libre pour les pieds

a)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. L’espace sous un obstacle faisant partie intégrante des TIC fait partie d’un espace d’accès.

Procédure

1. Vérifier que la largeur de l’espace libre pour les genoux est supérieure à 760 mm (30 po).

2. Vérifier que la largeur de l'espace libre pour les pieds est supérieure à 760 mm (30 po).

Résultat

Réussite : Les énoncés testables nos 1 et 2 sont vrais.

Échec : Les énoncés testables nos 1 et 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

b)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Sous tout obstacle faisant partie intégrante des TIC, l’espace libre pour les pieds est d’au moins 230 mm (9 po) au-dessus du plancher.

Procédure

1. Vérifier que l’espace libre pour les orteils a au moins 430 mm (17 po) de profondeur et est à 230 mm (9 po) au-dessus du plancher sous l’obstacle.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie

c)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Sous tout obstacle faisant partie intégrante des TIC, l'espace libre pour les pieds est d’au moins 230 mm (9 po) au-dessus du plancher.

Procédure

1. Vérifier que l'espace libre pour les pieds ne dépasse pas de plus de 150 mm (6 po) tout obstacle à 230 mm (9 po) au-dessus du plancher.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

8.3.2.6 Espace libre pour les genoux

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (27 po) au-dessus du plancher est considéré comme un espace libre pour les genoux et il doit :

1. ne pas s’étendre sur plus de 635 mm (25 pouces) sous l’obstacle à une hauteur de 230 mm (9 po) au-dessus du plancher;

2. s’étendre sur au moins 280 mm (11 pouces) sous l’obstacle à une hauteur de 230 mm (9 po) au-dessus du plancher;

3. s'étendre sur au moins 205 mm (8 po) sous l’obstacle à une hauteur de 685 mm (27 po) au-dessus du plancher;

4. être autorisé à être réduit en profondeur à raison de 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.

Cela est illustré à la figure 5.

C.8.3.2.6 Espace libre pour les genoux

a)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Il y a un espace libre pour les genoux sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher.

Procédure

1. Vérifier qu’il y a un espace libre pour les genoux qui s’étend sur moins de 635 mm (25 po) sous l’obstacle à une hauteur de 230 mm (9 po) au-dessus du plancher.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

b)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Il y a un espace libre pour les genoux sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher.

Procédure

1. Vérifier qu’il y a un espace libre pour les genoux qui s’étend sur au moins 280 mm (11 po) sous l’obstacle à une hauteur de 230 mm (9 po) au-dessus du plancher.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

c)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Il y a un espace libre pour les genoux sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher.

Procédure

1. Vérifier qu’il y a un espace libre pour les genoux qui s’étend sur plus de 205 mm (9 po) sous l’obstacle à une hauteur de 685 mm (25 po) au-dessus du plancher.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

d)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Un obstacle fait partie intégrante des TIC.

3. Il y a un espace libre pour les genoux sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher.

Procédure

1. Vérifier que la réduction de la profondeur de l’espace libre pour les genoux n’est pas supérieure à 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

8.3.3 Portée latérale
Clause de la norme EN 301 549Détermination de la conformité

8.3.3.1 Hauteur maximum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant fait partie intégrante des TIC fixes qui est inférieur à 255 mm (10 po), la hauteur maximum de la portée latérale d’au moins une pièce manœuvrable de chaque type doit être inférieure ou égale à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

C.8.3.3.1 Hauteur maximum de la portée latérale libre

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. La portée latérale est libre ou obstruée par un élément faisant fait partie intégrante des TIC fixes qui est inférieur à 510 mm (20 po).

Procédure

1. Vérifier que la hauteur maximum de la portée latérale à au moins une pièce manœuvrable de chaque type n’est pas supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.3.2 Hauteur minimum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes qui est inférieur à 255 mm (10 po), la hauteur minimum de la portée latérale à au moins une pièce manœuvrable de chaque type doit être supérieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès. Cela est illustré à la figure 6.

C.8.3.3.2 Hauteur minimum de la portée latérale libre

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. La portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes qui est inférieur à 510 mm (20 po).

Procédure

1. Vérifier que la hauteur minimum de la portée latérale à au moins une pièce manœuvrable de chaque type est supérieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.3.3 Portée latérale obstruée
Clause de la norme EN 301 549Détermination de la conformité

8.3.3.3.1 Portée latérale obstruée (≤ 255 mm)

Lorsque les TIC fixes présentent une obstruction qui fait partie intégrante des TIC, la hauteur de l’obstruction doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est inférieure ou égale à 255 mm (10 po), la hauteur maximum de la portée latérale à au moins une pièce manœuvrable de chaque type ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès. Cela est illustré à la figure 7 (a).

C.8.3.3.3.1 Portée latérale obstruée (≤ 255 mm)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Une obstruction dont la profondeur est inférieure ou égale à 255 mm (10 po) fait partie intégrante des TIC.

Procédure

1. Vérifier que la hauteur maximum de la portée latérale à au moins une pièce manœuvrable de chaque type n’est pas supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.3.3.2 Portée latérale obstruée (≤ 610 mm)

Lorsque les TIC fixes présentent une obstruction qui fait partie intégrante des TIC, la hauteur de l’obstruction doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est supérieure à 255 mm (10 po) et inférieure à 610 mm (24 po), la hauteur maximum de la portée latérale à au moins un de chaque type de pièce manœuvrable ne doit pas être supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès. Cela est illustré à la figure 7 (b).

C.8.3.3.3.2 Portée latérale obstruée (≤ 610 mm)

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Une obstruction dont la profondeur est supérieure à 255 mm (10 po) et inférieure à 610 mm (24 po) fait partie intégrante des TIC.

Procédure

1. Vérifier que la hauteur maximum de la portée latérale à au moins une pièce manœuvrable de chaque type n’est pas supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.4 Surface de plancher ou de sol dégagée
Clause de la norme EN 301 549Détermination de la conformité

8.3.4.1 Changement de niveau

Lorsque des TIC fixes comportent un plancher, tout changement de niveau du plancher qui y est intégré doit être aménagé d’une rampe présentant une pente d’au plus 1:48. Exceptions :

1. Si le changement de niveau du plancher est inférieur ou égal à 6,4 mm (1/4 po), le changement peut être vertical comme l’indique la figure 8.

2. Si le changement de niveau du plancher est inférieur ou égal à 13 mm (1/2 po), le changement peut présenter une pente d’au plus 1:2 comme il est illustré à la figure 9.

C.8.3.4.1 Changement de niveau

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Les TIC comportent un plancher.

3. Le plancher présente un changement de niveau..

Procédure

1. Si le changement de niveau est aménagé d’une rampe, vérifier qu’il présente une pente inférieure à 1:48.

2. Si le changement de niveau du plancher est vertical, vérifier qu’il est inférieur ou égal à 6,4 mm.

3. Si le changement de niveau du plancher est vertical ou présente une pente, vérifier que la pente n’est pas supérieure à 1:2.

Résultat

Réussite : L’énoncé testable no 1 ou no 2 ou no 3 est vrai.

Échec : Les énoncés testables nos 1, 2 et 3 sont faux.

Non applicable : La condition préalable 1 ou 2 ou 3 n’est pas remplie.

8.3.4.2 Surface de plancher ou de sol dégagée

Lorsque des TIC fixes intègrent un espace opérationnel, elles doivent prévoir une surface de plancher dégagée d’au moins 760 mm (30 po) par 1 220 mm (48 po) à partir de laquelle il est possible d’exploiter les TIC. Cela est illustré à la figure 10.

C.8.3.4.2 Surface de plancher ou de sol dégagée

Type d’évaluation

Inspection et mesures

Conditions préalables

1. Les TIC sont fixes.

2. Elles intègrent un espace opérationnel.

Procédure

1. Vérifier qu’il y a une surface de plancher dégagée avec des dimensions rectangulaires minimales de 760 mm sur un bord et de 1220 mm sur l’autre bord.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.4.3 Approche
Clause de la norme EN 301 549Détermination de la conformité

8.3.4.3.1 Généralités

Lorsque des TIC fixes comportent un espace d’accès, au moins un côté complet de l’espace doit être dégagé.

C.8.3.4.3.1 Généralités

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes.

2. Elles comportent un espace d’accès.

Procédure

1. Vérifier qu’un côté complet de l’espace est dégagé.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.4.3.2 Approche avant

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 610 mm (24 po), et lorsqu’une approche avant est nécessaire, l’espace d’accès doit être d’au moins 915 mm (36 po) de largeur. Cela est illustré à la figure 11.

C.8.3.4.3.2 Approche avant

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes et comportent une alcôve

2. L’espace opérationnel se trouve dans l’alcôve.

3. La profondeur de l’alcôve est supérieure à 610 mm.

4. Une approche avant est nécessaire.

Procédure

1. Vérifier que la largeur de l’alcôve est supérieure à 915 mm.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2, 3 ou 4 n’est pas remplie.

8.3.4.3.3 Approche parallèle

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 380 mm (15 po), et lorsqu’une approche parallèle est nécessaire, l’espace d’accès doit être d’au moins 1525 mm (60 po) de largeur. Cela est illustré à la figure 12.

C.8.3.4.3.3 Approche parallèle

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes et comportent une alcôve

2. L’espace opérationnel se trouve dans l’alcôve.

3. La profondeur de l’alcôve est supérieure à 380 mm.

4. Une approche parallèle est possible.

Procédure

1. Vérifier que la largeur de l’espace d’accès est supérieure à 1525 mm.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2, 3 ou 4 n’est pas remplie.

8.3.5 Visibilité

Lorsque les TIC fixes fournissent un ou plusieurs écrans d’affichage, au moins un écran d'affichage de chaque type doit être positionné de telle sorte que les renseignements à l'écran soient lisibles depuis un point situé à 1015 mm (40 pouces) au-dessus du centre du plancher de l’espace opérationnel.

REMARQUE : Cette exigence vise à ce que l’information à l’écran soit lisible par des utilisateurs ayant une vision normale et des compétences linguistiques appropriées, lorsqu’ils sont assis dans un fauteuil roulant.

C.8.3.5 Visibilité

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes.

2. Un ou plusieurs écrans d’affichage sont fournis.

Procédure

1. Vérifier qu’au moins un écran d'affichage de chaque type est positionné de telle sorte que les renseignements à l'écran soient lisibles depuis un point situé à 1015 mm (40 pouces) au-dessus du centre du plancher de l’espace opérationnel.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

8.3.6 Instructions d’installation

Les instructions d’installation doivent être disponibles pour toutes les TIC fixes. Ces instructions doivent indiquer comment installer les TIC en tenant compte des exigences applicables en matière d’accessibilité de l’environnement bâti dans la mesure où elles s’appliquent à l’installation des TIC. Lorsque de telles exigences n’existent pas, les instructions devraient exiger que les dimensions des TIC installées soient conformes aux clauses 8.3.2 à 8.3.5 du présent document.

C.8.3.6 Instructions d’installation

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont fixes.

Procédure

1. Vérifier que les instructions d’installation sont disponibles.

2. Vérifier que les instructions indiquent comment installer les TIC de façon à s’assurer que les dimensions des TIC installées sont conformes aux clauses 8.3.2 à 8.3.4.

3. Vérifier que les instructions indiquent que les installateurs doivent également tenir compte des exigences applicables en matière d’accessibilité de l’environnement bâti dans la mesure où elles s’appliquent à l’installation des TIC.

Résultat

Réussite : Les énoncés testables nos 1, 2 et 3 sont vrais.

Échec : Les énoncés testables nos 1, 2 et 3 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.4 Pièces mécaniquement manœuvrable
Clause de la norme EN 301 549Détermination de la conformité

8.4.1 Touches numériques

Lorsqu’elles sont fournies, les touches numériques formant un pavé rectangulaire doivent permettre de distinguer le numéro cinq de manière tactile des autres touches du pavé numérique.

REMARQUE: La Recommandation E.161[i.20] de l’UIT-T décrit la disposition du clavier du téléphone à 12 touches et fournit des détails supplémentaires sur la forme des marqueurs tactiles.

C.8.4.1 Touches numériques

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées de touches numériques physiques disposées sur un clavier téléphonique à 12 touches.

Procédure

1. Vérifier que le numéro cinq se distingue de manière tactile des autres touches du clavier.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.4.2 Fonctionnement des pièces mécaniques
Clause de la norme EN 301 549Détermination de la conformité

8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

C.8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner.

Procédure

1. Vérifier qu’il y a un autre moyen de fonctionnement qui n’exige pas de telles actions.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.4.2.2 Force de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite une force supérieure à 22,2 N pour fonctionner, un autre moyen de fonctionnement nécessitant une force inférieure à 22,2 N doit être prévu.

REMARQUE : ISO 21542:2011 [i.34] : Building Construction - Accessibility and Usability of the Built Environment recommande une valeur comprise entre 2,5 et 5 newtons.

C.8.4.2.2 Force de fonctionnement des pièces mécaniques

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont dotées d’une commande qui nécessite une force supérieure à 22,2 N pour fonctionner.

Procédure

1. Vérifier qu’un autre moyen de fonctionnement nécessitant une force inférieure ou égale à 22,2 N est prévu.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.4.3 Clés, billets et cartes tarifaires

Lorsque les TIC fournissent des touches, des billets ou des cartes tarifaires, et que leur orientation est importante pour une utilisation ultérieure, elles doivent avoir une orientation qui est perceptible au toucher.

REMARQUE: La norme ETSI ETS 300 767[i.6] définit les indications tactiles appropriées pour les cartes plastiques.

C.8.4.3 Clés, billets et cartes tarifaires

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC fournissent des clés, des billets ou des cartes tarifaires, et leur orientation est importante pour une utilisation ultérieure.

Procédure

1. Vérifier que les clés, les billets ou les cartes tarifaires ont une orientation perceptible au toucher.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

8.5 Indication tactile du mode vocal

Lorsque les TIC sont conçues pour une utilisation partagée et qu’une sortie vocale est disponible, une indication tactile des moyens permettant de lancer le mode de fonctionnement vocal doit être fournie.

REMARQUE: L’indication tactile peut inclure des instructions en braille.

C.8.5 Indication tactile du mode vocal

Type d’évaluation

Inspection

Conditions préalables

1. Les TIC sont conçues pour une utilisation partagée.

2. La sortie vocale est disponible.

Procédure

1. Vérifier qu’une indication tactile des moyens de lancement du mode vocal est fournie.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie..

9 Web

Clause de la norme EN 301 549Détermination de la conformité

9.0 Généralités (information)

Les exigences de la clause 9 s’appliquent aux pages Web (telles que définies à La clause 3.1), y compris:

  • La conformité avec le niveau AA des WCAG 2.0 équivaut à la conformité avec les clauses 9.1.1, 9.1.2, 9.1.3.1 à 9.1.3.3, 9.1.4.1 à 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.1.4, 9.2.1.1, 9.2.1.2, 9.2.2, 9.2.3, 9.2.4, 9.3, 9.4.1.1, 9.4.1.2 et avec les exigences de conformité de la clause 9.5 du présent document.
  • La conformité au niveau AA des WCAG 2.1 équivaut à la conformité à toutes les clauses 9.1 à 9.4 et aux exigences de conformité de La clause 9.5 du présent document.
  • Les exigences relatives aux autres documents et logiciels sont énoncées aux articles 10 et 11, respectivement.

REMARQUE 1: Les sites Web sont évalués en tant que pages Web individuelles. Les applications Web, les applications Web mobiles, etc., sont couvertes par la définition de page Web qui est très large et qui englobe tous les types de contenu Web.

Les exigences en matière de contenu Web énoncées aux articles 9.1 à 9.4 établissent tous les critères de succès des niveaux A et AA à partir des Règles pour l’accessibilité des contenus Web 2.0 de W3C (WCAG 2.1) [5]:

  • Les pages Web qui sont conformes aux niveaux A et AA des WCAG 2.0 sont également conformes aux clauses 9.1.1.1 à 9.1.3.3, 9.1.4.1 à 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.2.1 à 9.2.4.7, 9.3.1.1 à 9.4.1.2 ainsi qu’aux exigences de conformité de la clause 9.5.
  • Les pages Web qui sont conformes au niveau AA des WCAG 2.1 sont conformes à toutes les clauses 9.1 à 9.4 ainsi qu’aux exigences de conformité de La clause 9.5.
  • Les pages Web qui sont conformes aux clauses 9.1.1.1 à 9.1.3.3, 9.1.4.1 à 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.2.1 à 9.2.4.7, 9.3.1.1 à 9.4.1.2 ainsi qu’aux exigences de conformité de la clause 9.5, sont également conformes au niveau AA des WCAG 2.0.
  • Les pages Web qui sont conformes à toutes les clauses 9.1 à 9.4 et aux exigences de conformité de la clause 9.5, sont conformes au Niveau AA des WCAG 2.1.

REMARQUE 2: WCAG 2.0 est identique à la norme ISO/CEI 40500 (2012): « Technologies de l’information – Règles pour l’accessibilité des contenus Web 2.0 (WCAG 2.0) de World Wide Web Consortium (W3C)» [4].

Les exigences des clauses 9.1 à 9.4 sont rédigées selon le concept de la satisfaction des critères de succès (défini à la clause 3.1).

Une page Web satisfait à un critère de succès des WCAG lorsque ce critère ne se révèle pas « faux » lors de l’évaluation de la page Web. Cela implique que si le critère de succès place des conditions sur une caractéristique spécifique et que cette caractéristique spécifique n’apparaît pas dans la page Web, alors cette page satisfait au critère de succès.

REMARQUE 3: Par exemple, une page Web qui ne contient pas de contenu audio pré-enregistré dans un support synchronisé satisfera automatiquement au critère de succès 1.2.2 des WCAG (Sous-titres [pré-enregistrés]) et, par conséquent, sera également conforme à la clause 9.1.2.2.

En plus des critères de réussite du Niveau AA, les lignes directrices pour l’accessibilité aux contenus Web comprennent également des critères de succès pour le niveau AAA.

REMARQUE 4: Le corps du présent document n’inclut pas les critères de succès du niveau AAA, et ce, à la fois pour éviter toute confusion avec les exigences fondées sur le niveau A et le niveau AA et pour assurer l’harmonisation avec les autres normes d’approvisionnement.

Les auteurs de sites Web et les spécialistes de l’accessibilité en matière d’approvisionnement sont encouragés à améliorer l’accessibilité au-delà des exigences du présent document. Par conséquent, ils doivent examiner si l’un ou l’autre des critères de succès du niveau AAA des WCAG offre des suggestions qui peuvent être applicables et pertinentes à leur projet, de même que potentiellement bénéfiques pour certains utilisateurs.

REMARQUE 5: Le W3C énonce ce qui suit: « il n’est pas recommandé d’exiger la conformité au niveau AAA puisqu’il est impossible de respecter tous les critères de succès liés à ce niveau pour certains éléments du contenu ».

C.9.0 Généralités (information)

La clause 9.0 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

9.1 Perceptible
9.1.1 Équivalents textuels
Clause de la norme EN 301 549Détermination de la conformité

9.1.1.1 Contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

C.9.1.1.1 Contenu non textuel

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez que la page Web n’échoue pas au critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

9.1.2 Médias temporels
Clause de la norme EN 301 549Détermination de la conformité

9.1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés)

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 1.2.1 Contenu audio ou vidéo seulement (préenregistré) des WCAG 2.1.

C.9.1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés) des WCAG 2.1.

Résultat.

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.1 Contenu seulement audio et seulement vidéo (pré-enregistrés) des WCAG 2.1.

9.1.2.2 Sous-titres (pré-enregistrés)

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.2.2 Sous-titres (pré-enregistrés).

Critères de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1

Comprendre le critère Sous-titres (pré-enregistrés)(en anglais seulement)

Comment satisfaire au critère Sous-titres (pré-enregistrés)(en anglais seulement)

(Niveau A)

Fournir des sous-titres pour tout contenu audio pré-enregistré dans un média synchronisé, excepté lorsque le média est un média de remplacement pour un texte et qu'il est clairement identifié comme tel.

C.9.1.2.2 Sous-titres (pré-enregistrés)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez que la page Web n’échoue pas au critère de succès 1.2.2 Sous-titres (pré-enregistrées) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

9.1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré)

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1

C.9.1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

9.1.2.4 Sous-titres (en direct)

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1 .

C.9.1.2.4 Sous-titres (en direct)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez que la page Web n’échoue pas au critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

9.1.2.5 Audio-description (pré-enregistrée)

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès 1.2.5 Audio-description (pré-enregistré) des WCAG 2.1. 

C.9.1.2.5 Audio-description (pré-enregistrée)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

1. Vérifier que la page Web n’échoue pas au critère de succès 1.2.5 Audio-description (pré-enregistrée) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.5 Audio-description (pré-enregistrée) des WCAG 2.1.

9.1.3 Adaptable
Clause de la norme EN 301 549Détermination de la conformité

9.1.3.1 Information et relations

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

C.9.1.3.1 Information et relations

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.1 Information et relations des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.1 Information et relations des WCAG 2.1.

9.1.3.2 Ordre séquentiel logique

Dans le cas où la TIC est une page Web, elle satisfait au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

C.9.1.3.2 Ordre séquentiel logique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

9.1.3.3 Caractéristiques sensorielles

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.3 Caractéristiques sensorielles de WCAG 2.1.

C.9.1.3.3 Caractéristiques sensorielles

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

9.1.3.4 Orientation

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.4 Orientation des WCAG 2.1.

C.9.1.3.4 Orientation

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez si la page Web n’échoue pas au critère de succès 1.3.4 Orientation des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.4 Orientation des WCAG 2.1.

9.1.3.5 Identifier la finalité de la saisie

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 1.3.5 Finalité d’un champ de saisie des WCAG 2.1.

C.9.1.3.5 Identifier la finalité de la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

9.1.4 Distinguable
Clause de la norme EN 301 549Détermination de la conformité

9.1.4.1 Utilisation de la couleur

Dans le cas où la TIC est une page Web, elle remplit le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

C.9.1.4.1 Utilisation de la couleur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

9.1.4.2 Contrôle du son

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.2 Contrôle du son des WCAG 2.1.

C.9.1.4.2 Contrôle du son

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.2 Contrôle du son des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.2 Contrôle du son des WCAG 2.1.

9.1.4.3 Contraste (minimum)

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.3 Contraste (minimum).

C.9.1.4.3 Contraste (minimum)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

9.1.4.4 Redimensionnement du texte

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.4 Redimensionnement du texte (en direct) des WCAG 2.1.

C.9.1.4.4 Redimensionnement du texte

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

9.1.4.5 Texte sous forme d’image

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

C.9.1.4.5 Texte sous forme d’image

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

9.1.4.10 Redistribution

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.10 Redistribution des WCAG 2.1.

C.9.1.4.10 Redistribution

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez si la page Web n’échoue pas au critère de succès 1.4.10 Redistribution des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.10 Redistribution des WCAG 2.1.

9.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

C.9.1.4.11 Contraste du contenu non textuel

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.11 Contraste des éléments non textuels des WCAG 2.1.

9.1.4.12 Espacement du texte

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

C.9.1.4.12 Espacement du texte

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

9.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est une page Web, elle remplit le Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

C.9.1.4.13 Contenu au survol ou au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que le document n’échoue pas au Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

9.2 Utilisable
9.2.1 Accessibilité au clavier
Clause de la norme EN 301 549Détermination de la conformité

9.2.1.1 Clavier

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 2.1.1 Clavier de WCAG 2.1.

C.9.2.1.1 Clavier

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez si la page Web n’échoue pas au critère de succès 2.1.1 Clavier des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.1 Clavier des WCAG 2.1.

9.2.1.2 Pas de piège au clavier

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 2.1.2 Pas de piège au clavier de WCAG 2.1.

C.9.2.1.2 Pas de piège au clavier

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez que la page Web n’échoue pas le critère de succès 2.1.2 Pas de piège à clavier des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.2 Pas de piège à clavier des WCAG 2.1.

9.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier des caractères des WCAG 2.1.

C.9.2.1.4 Raccourcis clavier utilisant des caractères

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.1.4 Raccourcis clavier des caractères de WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.4 Raccourcis clavier utilisant des caractères de WCAG 2.1.

9.2.2 Délai suffisant
Clause de la norme EN 301 549Détermination de la conformité

9.2.2.1 Réglage du délai

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.2.1 Réglage du délai de WCAG 2.1.

C.9.2.2.1 Réglage du délai

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifiez si la page Web n’échoue pas au critère de succès 2.2.1 Réglage du délai des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.2.1 Réglage du délai des WCAG 2.1.

9.2.2.2 Mettre en pause, arrêter, masquer

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.2.2 Mettre en pause, arrêter, masquer de WCAG 2.1.

C.9.2.2.2 Mettre en pause, arrêter, masquer

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.2.2 Mettre en pause, arrêter, masquerdes WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.2.2 Mettre en pause, arrêter, masquer des WCAG 2.1.

9.2.3 Crises et réactions physiques
Clause de la norme EN 301 549Détermination de la conformité

9.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.3.1 Pas plus de trois flashs ou sous le seuil critique.

C.9.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.3.1 Pas plus de trois flashs ou sous le seuil critique des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.3.1 Pas plus de trois flashs ou sous le seuil critique des WCAG 2.1.

9.2.4 Navigable
Clause de la norme EN 301 549Détermination de la conformité

9.2.4.1 Contourner des blocs

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.1 Contourner des blocs.

C.9.2.4.1 Contourner des blocs

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.1 Contourner des blocs des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.1 Contourner des blocs des WCAG 2.1.

9.2.4.2 Titre de page

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.2 Titre de page.

C.9.2.4.2 Titre de page

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.2 Titre de page des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.2 Titre de page des WCAG 2.1.

9.2.4.3 Parcours du focus

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.3 Parcours de la cible de saisie.

C.9.2.4.3 Parcours du focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.3 Parcours de la cible de saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.3 Parcours du focus des WCAG 2.1.

9.2.4.4 Fonction du lien (selon le contexte)

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.4 Fonction du lien (selon le contexte).

C.9.2.4.4 Fonction du lien (selon le contexte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.4 Objectif du lien (selon le contexte) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

9.2.4.5 Accès multiples

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.5 Accès multiples.

C.9.2.4.5 Accès multiples

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.5 Accès multiples des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.5 Accès multiples des WCAG 2.1.

9.2.4.6 En-têtes et étiquettes

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.6 En-têtes et étiquettes.

C.9.2.4.6 En-têtes et étiquettes

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

9.2.4.7 Visibilité Au focus

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.4.7 Visibilité de la cible de saisie.

C.9.2.4.7 Visibilité Au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au Critère de succès 2.4.7 Visibilité Au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.7 Visibilité du focus des WCAG 2.1..

9.2.5 Modalités d’entrée
Clause de la norme EN 301 549Détermination de la conformité

9.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.1 Mouvements du pointeur.

C.9.2.5.1 Gestes pour le contrôle du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.5.1 Mouvements du pointeur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1.

9.2.5.2 Annulation de l’action du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.2 Annulation de l’action du pointeur.

C.9.2.5.2 Annulation de l’action du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.5.2 Annulation du pointeur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1.

9.2.5.3 Étiquette dans le nom

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom de WCAG 2.1.

C.9.2.5.3 Étiquette dans le nom

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

9.2.5.4 Activation par le mouvement

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement.

C.9.2.5.4 Activation par le mouvement

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

9.3 Compréhensible
9.3.1 Lisible
Clause de la norme EN 301 549Détermination de la conformité

9.3.1.1 Langue de la page

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.1.1 Langue de la page.

C.9.3.1.1 Langue de la page

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.1.1 Langue de la page des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.1.1 Langue de la page des WCAG 2.1.

9.3.1.2 Langue d’un passage

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.1.2 Langue d’un passage.

C.9.3.1.2 Langue d’un passage

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.1.2 Langue d’un passage des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.1.2 Langue d’un passage des WCAG 2.1.

9.3.2 Prévisible
Clause de la norme EN 301 549Détermination de la conformité

9.3.2.1 Au focus

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.2.1 Au focus.

C.9.3.2.1 Au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.2.1 Au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.1 Au focus des WCAG 2.1.

9.3.2.2 À la saisie

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès À la saisie.

C.9.3.2.2 À la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.2.2 À la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.2 À la saisie des WCAG 2.1

9.3.2.3 Navigation cohérente

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.2.3 Navigation cohérente.

C.9.3.2.3 Navigation cohérente

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.2.3 Navigation cohérente des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.3 Navigation cohérente des WCAG 2.1.

9.3.2.4 Identification cohérente

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.2.4 Identification cohérente.

C.9.3.2.4 Identification cohérente

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.2.4 Identification cohérente des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.4 Identification cohérente des WCAG 2.1.

9.3.3 Assistance à la saisie
Clause de la norme EN 301 549Détermination de la conformité

9.3.3.1 Identification des erreurs

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.3.1 Identification des erreurs.

C.9.3.3.1 Identification des erreurs

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

9.3.3.2 Étiquettes ou instructions

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.3.2 Étiquettes ou instructions.

C.9.3.3.2 Étiquettes ou instructions

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

9.3.3.3 Suggestion après une erreur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.3.3 Suggestion après une erreur.

C.9.3.3.3 Suggestion après une erreur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

9.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 3.3.4 Prévention des erreurs (juridiques, financières, de données).

C.9.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 3.3.4 Identification des erreurs des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.4 Prévention des erreurs (juridiques, financières, de données) des WCAG 2.1.

9.4 Robuste
9.4.1 Compatible
Clause de la norme EN 301 549Détermination de la conformité

9.4.1.1 Analyse syntaxique

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.1 Analyse syntaxique.

C.9.4.1.1 Analyse syntaxique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 4.1.1 Analyse syntaxique des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 4.1.1 Analyse syntaxique des WCAG 2.1.

9.4.1.2 Nom, rôle et valeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.2 Nom, rôle et valeur.

C.9.4.1.2 Nom, rôle et valeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 4.1.2 Nom, rôle et valeur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 4.1.2 Nom, rôle et valeur des WCAG 2.1.

9.4.1.3 Messages d’état

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

C.9.4.1.3 Messages d’état

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 4.1.3 Messages d’état des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou la page Web ne renferme pas de contenu pertinent pour le critère de succès 4.1.3 Messages d’état des WCAG 2.1.

9.5 Critères de succès de niveau AAA des WCAG 2.1

Outre les critères de succès de niveau AA, les Règles pour l’accessibilité des contenus Web comprennent les critères de succès pour le niveau AAA, aux clauses 9.1 à 9.4. Ces critères sont énumérés dans le tableau 9.1. Les auteurs de sites Web et les spécialistes de l’approvisionnement en matière d’accessibilité sont invités à tenir compte des critères de succès de niveau AAA des WCAG 2.1 qui, lorsqu’il est possible de les appliquer, peuvent fournir un accès au-delà de ce qui est requis dans le présent document.

REMARQUE : Le W3C stipule qu’« il n’est pas recommandé de se fixer le niveau AAA comme objectif à l’échelle de sites entiers car il n’est pas possible de satisfaire à tous les critères de succès du niveau AAA pour certains contenus ». Consulter le Tableau 9.1 : Critères de succès de niveau AAA des WCAG 2.1 dans l'Annexe - Tableaux et figures (de la norme EN 301 549).

9.5 Critères de succès de niveau AAA des WCAG 2.1

La clause 9.5 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

9.6 Exigences de conformité aux WCAG

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire aux cinq exigences de conformité aux WCAG 2.1 de niveau AA énumérées ci-dessous [5].

1. Niveau de conformité

2. Pages complètes

3. Processus complets

4. L’usage des technologies selon des méthodes exclusivement compatibles avec l’accessibilité

5. Non-interférence

REMARQUE 1: Une page Web qui satisfait aux exigences 9.1 à 9.4, ou lorsqu’une version de remplacement conforme au niveau AA (tel que défini dans la WCAG 2.1[5]) est fournie, satisfera à l’exigence de conformité 1.

REMARQUE 2: Selon le W3C: « Les WCAG 2.1 élargissent les Directives pour l’accessibilité des contenus Web 2.0[4], qui ont été publiées comme Recommandation du W3C en décembre 2008. Le contenu qui est conforme aux WCAG 2.1 est également conforme aux WCAG 2.0, et, par conséquent, aux politiques qui font référence aux WCAG 2.0. » [4]

REMARQUE 3: L’exigence de conformité 5 stipule que tout le contenu de la page, y compris le contenu dont on ne dépend pas autrement pour atteindre la conformité, respecte les clauses 9.1.4.2, 9.2.1.2, 9.2.2.2 et 9.2.3.1.

Critères de succès de niveau AAA des WCAG 2.1 2.1 de niveau AA[5]

C.9.6 Exigences de conformité aux WCAG

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une page Web.

Procédure

1. Vérifier que la page Web satisfait à l’exigence de conformité aux WCAG 2.1 [5] « 1: Niveau de conformité » au niveau AA.

2. Vérifier que la page Web satisfait à l’exigence de conformité aux WCAG 2.1 [5] « 2: Pages complètes ».

3. Vérifier que la page Web satisfait à l’exigence de conformité aux WCAG 2.1 [5] « 3: Processus complets ».

4. Vérifier que la page Web satisfait à l’exigence de conformité aux WCAG 2.1 [5] « 4: L’usage des technologies selon des méthodes exclusivement compatibles avec l’accessibilité ».

5. Vérifier que la page Web satisfait à l’exigence de conformité aux WCAG 2.1 [5] « 5: Non-interférence ».

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: N’importe quel énoncé testable est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10 Contenu non Web

Clause de la norme EN 301 549Détermination de la conformité

10.0 Généralités (information)

Les exigences énoncées à la clause 10 s’appliquent aux documents:

  • qui ne sont pas des pages Web;
  • qui ne sont pas intégrés dans des pages Web;
  • qui sont intégrés dans des pages Web, qui ne sont pas utilisés dans le rendu et qui ne sont pas destinés à être rendus avec la page Web dans laquelle ils sont intégrés.

L’article 9 prévoit les exigences de conformité des documents qui se trouvent dans des pages Web ou qui sont intégrés dans des pages Web, et qui sont utilisés dans le rendu ou qui sont destinés à être rendus avec la page Web dans laquelle ils sont intégrés.

REMARQUE 1: Voici quelques exemples de documents: lettres, feuilles de calcul, messages électroniques, livres, images, présentations et films qui sont associés à un agent utilisateur comme un lecteur de documents, un éditeur ou un lecteur multimédia.

REMARQUE 2: Un document peut être composé de plusieurs fichiers, comme du contenu vidéo, des sous-titres, etc. La plupart du temps, cela n’est pas apparent pour l’utilisateur final qui parcourt le document/contenu.

REMARQUE 3: Les documents nécessitent un agent utilisateur pour que le contenu soit présenté à l’utilisateur. Les exigences relatives aux agents utilisateurs se trouvent à La clause 11.

REMARQUE 4: Les exigences relatives au contenu qui fait partie du logiciel se trouvent à la clause 11.

REMARQUE 5: Les critères de succès énoncés à la clause 10 visent à s’harmoniser avec la Note du groupe de travail [i.26] produite par le WCAG2ICT Task Force du W3C.

REMARQUE 6 : Des clauses « nul » ont été insérées afin de maintenir l’harmonisation avec la numérotation des clauses 9, 10 et 11.

REMARQUE 7 : Les exigences de la clause 10 s’appliquent également aux documents qui sont protégés par des mécanismes tels que les signatures numériques, le chiffrement, la protection par mot de passe et les filigranes lorsqu’ils sont présentés à l’utilisateur.

REMARQUE 8 : La pratique exemplaire consiste à utiliser WebSchemas/Accessibility 2.0 [i.38] pour fournir des métadonnées sur l’accessibilité du document au sein ou séparément du document.

C.10.0 Généralités (information)

La clause 10.0 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

10.1 Perceptible
10.1.1 Équivalents textuels
Clause de la norme EN 301 549Détermination de la conformité

10.1.1.1 Contenu non textuel

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.1.1 Contenu non textuel.

REMARQUE: Les CAPTCHAS n’apparaissent pas actuellement hors du Web. Cependant, s’ils apparaissent, ce conseil est pertinent.

C.10.1.1.1 Contenu non textuel

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

10.1.2 Médias temporels
Clause de la norme EN 301 549Détermination de la conformité

10.1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés)

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés).

REMARQUE: Le média de remplacement peut être fourni directement dans le document – ou fourni dans une version de remplacement qui satisfait au critère de succès.

C.10.1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.1 Contenus seulement audio et seulement vidéo (pré-enregistrés) des WCAG 2.1.

10.1.2.2 Sous-titres (pré-enregistrés)

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.2.2 Sous-titres (pré-enregistrés).

REMARQUE: La définition de « sous-titres » donnée par les WCAG 2.1 précise que « dans certains pays, les sous-titres sont appelés captions et subtitles ». On les appelle aussi parfois « sous-titres pour malentendants ». Selon la définition des WCAG 2.1, pour satisfaire à ce critère de succès, qu’il s’agisse de captions ou de subtitles, les sous-titres doivent fournir un « visuel synchronisé ou équivalent textuel pour l’information audio avec ou sans paroles nécessaires à la compréhension du contenu d’un média », lorsque l’information sans paroles comprend des « effets sonores, de la musique, des rires, l’identification et le positionnement des interlocuteurs ».

C.10.1.2.2 Sous-titres (pré-enregistrés)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non-Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

10.1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré)

Lorsque la technologie n’est pas un document Web, celle­ci doit satisfaire au critère de succès 1.2.3 audio-description ou version de remplacement pour un média temporel (pré-enregistré).

REMARQUE 1: La définition des WCAG 2.1 précise qu « audio-description » est également nommée « vidéo-description » et « narration descriptive ».

REMARQUE 2: Des pistes audio secondaires ou de remplacement sont couramment utilisées à cette fin.

C.10.1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.3 audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

10.1.2.4 Sous-titres (en direct)

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.2.4 Sous-titres (en direct).

REMARQUE: La définition de « sous-titres » donnée par les WCAG 2.1 précise que « dans certains pays, les sous-titres sont appelés captions et subtitles ». On les appelle aussi parfois « sous-titres pour malentendants ». Selon la définition des WCAG 2.1, pour satisfaire à ce critère de succès, qu’il s’agisse de captions ou de subtitles, les sous-titres doivent fournir un « visuel synchronisé ou équivalent textuel pour l’information audio avec ou sans paroles nécessaires à la compréhension du contenu d’un média », lorsque l’information sans paroles comprend des « effets sonores, de la musique, des rires, l’identification et le positionnement des interlocuteurs ».

C.10.1.2.4 Sous-titres (en direct)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1).

10.1.2.5 Audio-description (pré-enregistrée)

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.2.5 audio-description (pré-enregistrée).

REMARQUE 1: La définition des WCAG 2.1 précise qu’une «audio-description» est également nommée « vidéo-description » et « narration descriptive ».

REMARQUE 2: Des pistes audio secondaires ou de remplacement sont couramment utilisées à cette fin.

C.10.1.2.5 Audio-description (pré-enregistrée)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.5 audio-description (pré-enregistrée)des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.5 Audio-description (pré-enregistrée) des WCAG 2.1.

10.1.3 Adaptable
Clause de la norme EN 301 549Détermination de la conformité

10.1.3.1 Information et relations

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 1.3.1 Information et relations.

REMARQUE : Lorsque les documents contiennent des types de structure non standard (rôles), la pratique exemplaire consiste à les faire correspondre à un type de structure standard comme solution de secours pour le lecteur.

C.10.1.3.1 Information et relations

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.3.1 Information et relations des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.1 Information et relations des WCAG 2.1.

10.1.3.2 Ordre séquentiel logique

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

C.10.1.3.2 Ordre séquentiel logique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

10.1.3.3 Caractéristiques sensorielles

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

C.10.1.3.3 Caractéristiques sensorielles

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

10.1.3.4 Orientation

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

C.10.1.3.4 Orientation

Type d’évaluation

Inspection

Conditions préalables:

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.3.4 Orientation des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.4 Orientation des WCAG 2.1.

10.1.3.5 Identifier la finalité de la saisie

Dans le cas où la TIC est un document hors ligne, elle remplit le Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

C.10.1.3.5 Identifier la finalité de la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

10.1.4 Distinguable
Clause de la norme EN 301 549Détermination de la conformité

10.1.4.1 Utilisation de la couleur

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

C.10.1.4.1 Utilisation de la couleur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

10.1.4.2 Contrôle du son

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.1.

Tableau 10.1: Critère de succès du document: Contrôle du son

Si la lecture d’un fichier audio tiré d’un document dure plus de 3 secondes, un mécanisme est disponible pour le mettre en pause, l’arrêter ou pour en contrôler le volume de façon indépendante du niveau de volume du système général.

REMARQUE 1: Puisque toute partie d’un document ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le document entier, tout le contenu présent dans le document (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) doit satisfaire à ce critère de succès.

REMARQUE 2: Ce critère de succès est identique au critère de succès 1.4.2 Contrôle du son des WCAG 2.1, après remplacement de « sur une page Web » par « sur un document », de « tout contenu » par « toute partie d’un document », de « page entière » par « document entier », de « sur la page Web » par « sur le document », après suppression de « Voir l’exigence de conformité 5: Non-interférence » et après l’ajout de la note 1.

C.10.1.4.2 Contrôle du son

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.1.4.3 Contraste (minimum)

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.4.3 Contraste des WCAG 2.1.

C.10.1.4.3 Contraste (minimum)

Type d’évaluation: Inspection

Conditions préalables

· 1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

10.1.4.4 Redimensionnement du texte

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

REMARQUE 1: Les contenus pour lesquels il existe des lecteurs de logiciels, des visualiseurs ou des éditeurs dotés d’une fonction de zoom de 200% répondraient automatiquement à ce critère de succès lorsqu’ils sont utilisés avec ces lecteurs, à moins que le contenu ne fonctionne pas avec le zoom.

REMARQUE 2: Ce critère de succès concerne la capacité de permettre aux utilisateurs d’agrandir le texte à l’écran au moins jusqu’à 200% sans avoir besoin d’avoir recours à des technologies d’assistance. Cela signifie que l’application fournit un moyen d’agrandir le texte à 200% (zoom ou autre) sans perte de contenu ou de fonctionnalité ou que l’application fonctionne avec les fonctions de la plateforme qui répondent à cette exigence.

REMARQUE 3: La pratique exemplaire consiste à n’utiliser que des polices qui permettent une mise à l’échelle sans perte de qualité (p. ex. une présentation pixellisée). Cela s'applique en particulier aux polices intégrées.

C.10.1.4.4 Redimensionnement du texte

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

10.1.4.5 Texte sous forme d’image

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

C.10.1.4.5 Texte sous forme d’image

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès1.4.5 Texte sous forme d’image des WCAG 2.1.

10.1.4.10 Redistribution

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.2.

Tableau 10.2: Critère de succès du document: Redistribution

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessiter de défilement en deux dimensions en ce qui a trait aux éléments suivants:

  • Contenu à défilement vertical d’une largeur équivalente à 320 pixels CSS;
  • Contenu à défilement horizontal d’une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1: 320 pixels CSS équivalent à une largeur de fenêtre de départ de 1 280 pixels CSS avec un zoom de 400%. Pour les documents qui sont conçus pour défiler horizontalement (par exemple avec du texte vertical), les 256 pixels CSS équivalent à une hauteur de fenêtre de départ de 1 024 pixels avec un zoom de 400%.

REMARQUE 2: Les exemples de contenu qui nécessitent une mise en page bidimensionnelle sont les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données et les interfaces où il est nécessaire de garder les barres d’outils en vue pendant la manipulation du contenu.

REMARQUE 3: Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

C.10.1.4.10 Redistribution

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.2.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

C.10.1.4.11 Contraste du contenu non textuel

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un document hors ligne qui n’a pas de zone de présentation de contenu de taille fixe qui est essentielle à l’information véhiculée.

Procédure

1. Vérifier que le document n’échoue pas au Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

10.1.4.12 Espacement du texte

Dans le cas où la TIC est un document hors ligne qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

C.10.1.4.12 Espacement du texte

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

10.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un document hors ligne, elle remplit le Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

C.10.1.4.13 Contenu au survol ou au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.13 Contenu en mode survol ou focus des WCAG 2.1.

10.2 Utilisable
10.2.1 Accessibilité au clavier
Clause de la norme EN 301 549Détermination de la conformité

10.2.1.1 Clavier

Dans le cas où la TIC est un document hors ligne, elle remplit le critère de succès 2.1.1 Clavier des WCAG 2.1.

C.10.2.1.1 Clavier

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 2.1.1 Clavier des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.1 Clavier des WCAG 2.1.

10.2.1.2 Pas de piège au clavier

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.3.

Tableau 10.3: Critère de succès du document: Pas de piège au clavier

Si la Au focus du clavier peut être positionnée sur un élément de la page à l’aide d’une interface clavier, réciproquement, il peut être déplacé hors de ce même composant simplement à l’aide d’une interface clavier et, si ce déplacement exige plus que l’utilisation d’une simple touche flèche ou tabulation ou toute autre méthode standard de sortie, l’utilisateur est informé de la méthode permettant de déplacer la Au focus hors de ce composant.

REMARQUE 1: Puisque toute partie d’un document ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le document entier, il est nécessaire que tout le contenu présent dans le document (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) satisfasse à ce critère de succès.

REMARQUE 2: La méthode standard de sortie pourrait varier d’une plateforme à l’autre. Par exemple, la touche Échap est une méthode standard de sortie sur de nombreuses plateformes de bureau.

C.10.2.1.2 Pas de piège au clavier

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.3.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier des caractères des WCAG 2.1 .

C.10.2.1.4 Raccourcis clavier utilisant des caractères

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure:

1. Vérifier que la page Web n’échoue pas au critère de succès 2.1.4 Raccourcis clavier des caractères des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

10.2.2 Délai suffisant
Clause de la norme EN 301 549Détermination de la conformité

10.2.2.1 Réglage du délai

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.4.

Tableau 10.4: Critère de succès du document: Réglage du délai

Pour chaque limite de temps fixée par le document, au moins l’un des points suivants est vrai:

  • Suppression: L’utilisateur a la possibilité de désactiver la limite de temps avant de l’atteindre; ou
  • Ajustement: L’utilisateur a la possibilité d’ajuster la limite de temps avant de la rencontrer dans un intervalle d’au moins dix fois la durée paramétrée par défaut; ou
  • Extension: L’utilisateur est averti avant que la limite de temps expire et il lui est accordé au moins 20 secondes pour étendre cette limite par une action simple (par exemple, « appuyer sur la barre d’espace ») et l’utilisateur a la possibilité d’étendre la limite de temps au moins dix fois; ou
  • L’exception du temps réel: La limite de temps est une partie constitutive d’un événement en temps réel (par exemple, une enchère) et aucune solution de rechange n’est possible; ou
  • L’exception de la limite essentielle: La limite de temps est essentielleet l’étendre invaliderait alors l’activité; ou
  • L’exception des 20 heures: La limite de temps est supérieure à 20 heures.

REMARQUE 1: Ce critère de succès permet de s’assurer que les utilisateurs peuvent accomplir les tâches sans changements inattendus dans le contenu ou le contexte résultant d’une limite de temps. Ce critère de succès doit être considéré conjointement avec le critère de succès 3.2.1 des WCAG 2.1, qui impose des limites aux changements de contenu ou de contexte résultant de l’action des utilisateurs.

REMARQUE 2: Ce critère de succès est identique au critère de succès 2.2.1 Réglage du délai des WCAG 2.1, après le remplacement de « le contenu » par « documents » et l’ajout des mots « des WCAG 2.1 » après les mots « critère de succès » à la note 1 ci-dessus.

C.10.2.2.1 Réglage du délai

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.4.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.2.2 Mettre en pause, arrêter, masquer

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.5.

Tableau 10.5: Critère de succès du document: Mettre en pause, arrêter, masquer

Pour déplacer, faire clignoter, faire défiler ou mettre à jour automatiquement des informations, tous les éléments suivants sont vrais:

  • Déplacement, clignotement, défilement: Pour toute information en mouvement, clignotante ou défilante qui (1) démarre automatiquement, (2) dure plus de cinq secondes et (3) est présentée en parallèle avec d’autres contenus, il existe un mécanisme permettant à l’utilisateur de mettre en pause, d’arrêter ou de masquer l’information à moins que le déplacement, le clignement ou le défilement fasse partie d’une activité où cela est essentiel; et
  • Mise à jour automatique: Pour toute mise à jour qui (1) démarre automatiquement et (2) est présentée en parallèle avec d’autres contenus, il existe un mécanisme permettant à l’utilisateur de la mettre en pause, de l’arrêter, de la masquer ou de contrôler sa fréquence, sauf si la mise à jour automatique fait partie d’une activité où elle est essentielle.

REMARQUE 1: Pour les exigences relatives au contenu clignotant ou avec flash, se référer à la règle 2.3 des WCAG 2.1.

REMARQUE 2: Puisque toute partie d’un document ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le document entier, il est nécessaire que tout le contenu présent dans le document (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) satisfasse à ce critère de succès.

REMARQUE 3: Le contenu qui est mis à jour périodiquement par un logiciel ou qui est transmis en continu à l’agent utilisateur n’est pas tenu de préserver ou de présenter l’information générée ou reçue entre le début de la pause et la reprise de la présentation, car cela pourrait ne pas être techniquement possible et, dans de nombreuses situations, être trompeur.

REMARQUE 4: Une animation qui se produit dans le cadre d’une phase de préchargement ou d’une situation similaire peut être considérée comme essentielle si l’interaction ne peut pas se produire pendant cette phase pour tous les utilisateurs et si le fait de ne pas indiquer les progrès pouvait dérouter les utilisateurs ou leur faire croire que le contenu était gelé ou séparé.

REMARQUE 5: Ce critère de succès est identique au critère de succès 2.2.2 Mettre en pause, arrêter, masquer des WCAG 2.1, après remplacement de « page » et de « page Web » par « document », suppression de « Voir l’exigence de conformité 5: Non-ingérence » dans la note 2 du critère de succès, l’ajout des mots « des WCAG 2.1 » à la suite de « règle 2.3 » à la note 1 et la reformulation de la note 2 de façon à éviter le verbe « devoir ».

C.10.2.2.2 Mettre en pause, arrêter, masquer

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.5.

Résultat

Réussite: L’énoncé testable no 1 est vrai. Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.2.2 Mettre en pause, arrêter, masquer des WCAG 2.1.

10.2.3 Crises et réactions physiques
Clause de la norme EN 301 549Détermination de la conformité

10.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Lorsque la TIC est un document hors ligne, elle doit satisfaire au critère de succès indiqué dans le tableau 10.6.

Tableau 10.6: Critère de succès du document: Pas plus de trois flashs ou sous le seuil critique

Un document doit être exempt de tout élément qui flashe plus de trois fois dans n’importe quel intervalle d’une seconde ou ce flash doit se situer sous le seuil de flash générique et le seuil de flash rouge.

REMARQUE 1: Puisque toute partie d’un document ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le document entier, il est nécessaire que tout le contenu présent dans le document (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) satisfasse à ce critère de succès.

REMARQUE 2: Ce critère de succès est identique au critère de succès 2.3.1 Pas plus de trois flashs ou sous le seuil critique des WCAG 2.1 après remplacement de « pages Web » par « documents », de « la page entière » par « le document entier », « la page Web » par « le document », après suppression de « Voir l’exigence de conformité 5: Non-ingérence » et après la reformulation de la note 1 ci-dessus pour éviter le verbe « devoir ».

C.10.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.6.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.4 Navigable
Clause de la norme EN 301 549Détermination de la conformité

10.2.4.2 Titre de document

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.7.

Tableau 10.7: Critère de succès du document: Titre de document

Les documents présentent un titre qui décrit leur sujet ou leur but.

REMARQUE 1: Le nom d’un document (p. ex. document, fichier multimédia) peut servir de titre s’il décrit le sujet ou le but.

REMARQUE 2: Ce critère de succès est identique au critère de succès 2.4.2 Titre de page des WCAG 2.1 après remplacement de « pages Web » par « documents » et après ajout de la note 1 ci-dessus.

C.10.2.4.2 Titre de document

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.7.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.4.3 Parcours du focus

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.8.

Tableau 10.8: Critère de succès du document: Parcours du focus

Si un document peut être parcourue de façon séquentielle et que les séquences de navigation affectent la signification ou l’action, les éléments reçoivent la Au focus dans un ordre qui préserve la signification et l’opérabilité.

REMARQUE: Ce critère de succès est identique au critère de succès 2.4.3 Parcours de la cible de saisie des WCAG 2.1 après remplacement de « page Web » par « document ».

C.10.2.4.3 Parcours du focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.8.

Résultat

Réussite: L’énoncé testable no 1 est vrai. Échec: L’énoncé testable no 1 est faux.

10.2.4.4 Fonction du lien (selon le contexte)

Dans le cas où la technologie est un document, celle-ci doit satisfaire au critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

C.10.2.4.4 Fonction du lien (selon le contexte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez que le document n’échoue pas au critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

10.2.4.6 En-têtes et étiquettes

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

C.10.2.4.6 En-têtes et étiquettes

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

10.2.4.7 Visibilité du focus

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 2.4.7 Visibilité de la cible de saisie des WCAG 2.1.

C.10.2.4.7 Visibilité du focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 2.4.7 Visibilité de la cible de saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.7 Visibilité du focus des WCAG 2.1.

10.2.5 Modalités d’entrée
Clause de la norme EN 301 549Détermination de la conformité

10.2.5.1 Gestes pour le contrôle du pointeur

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.9.

Tableau 10.9: Critère de succès du document: Gestes pour le contrôle du pointeur

Toutes les fonctions qui utilisent des mouvements multipoints ou basés sur un tracé pour exécuter une commande peuvent être utilisées avec un seul pointeur sans mouvement basé sur un tracé, à moins qu’un mouvement multipoint ou basé sur un tracé soit essentiel.

REMARQUE 1: cette exigence s’applique aux documents qui interprètent les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 2: ce critère de succès est identique au critère de succès 2.5.1 Mouvements du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

C.10.2.5.1 Gestes pour le contrôle du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.9.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.5.2 Annulation de l’action du pointeur

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.10.

Tableau 10.10: Critère de succès du document: Annulation de l’action du pointeur

Dans le cas des fonctions qui peuvent fonctionner à l’aide d’un seul pointeur, au moins l’un des éléments suivants est vrai:

  • Aucun événement descendant: l’événement descendant n’est pas utilisé pour exécuter une partie de la fonction;
  • Abandonner ou Annuler: la fonction se termine avec l’événement ascendant et un mécanisme est disponible pour abandonner la fonction avant la fin ou pour annuler la fonction une fois l’exécution de la fonction terminée;
  • Inversion de l’événement: l’événement montant inverse tout résultat de l’événement descendant précédent;
  • Essentiel: terminer la fonction sur inversion de l’événement est essentiel.

REMARQUE 1: les fonctions qui émulent un appui clavier ou un pavé numérique sont considérées comme essentielles.

REMARQUE 2: cette exigence s’applique au contenu Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 3: Ce critère de succès est identique au critère de succès 2.5.2 Annulation du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

C.10.2.5.2 Annulation de l’action du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.10.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.2.5.3 Étiquette dans le nom

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

C.10.2.5.3 Étiquette dans le nom

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que la page Web n’échoue pas au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

10.2.5.4 Activation par le mouvement

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

C.10.2.5.4 Activation par le mouvement

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

10.3 Compréhensible
10.3.1 Lisible
Clause de la norme EN 301 549Détermination de la conformité

10.3.1.1 Langue du document

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.11.

Tableau 10.11: Critère de succès du document: Langue du document

La langue par défaut de chaque document peut être déterminée par un programme informatique.

REMARQUE: Ce critère de succès est identique au critère de succès 3.1.1 Langue de la page des WCAG 2.1 après remplacement de « page Web » par « document ».

C.10.3.1.1 Langue du document

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.11.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.3.1.2 Langue d’un passage

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.12.

Tableau 10.12: Critère de succès du document: Langue d’un passage

La langue de chaque passage ou expression du document peut être déterminée par un programme informatique sauf pour un nom propre, pour un terme technique, pour un mot dont la langue est indéterminée ou pour un mot ou une expression faisant partie du langage courant de la langue utilisée dans le contexte immédiat.

REMARQUE 1: Pour certaines technologies de documentation, il n’existe pas de méthode de technologie d’assistance pouvant indiquer la langue des différents passages ou expressions du document, et il ne serait pas possible de satisfaire au critère de succès en utilisant ces technologies.

REMARQUE 2: L’héritage est une méthode courante. Par exemple, un document fournit la langue qu’il utilise et on peut supposer que tous les éléments de texte ou d’un élément d’interface utilisateur de ce document utiliseront la même langue, sauf indication contraire.

REMARQUE 3: Ce critère de succès est identique au critère de succès 3.1.2 Langue d’un passage des WCAG 2.1 après remplacement de « contenu » par « document » et après ajout des notes 1 et 2 ci-dessus.

C.10.3.1.2 Langue d’un passage

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.12.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.3.2 Prévisible
Clause de la norme EN 301 549Détermination de la conformité

10.3.2.1 Au focus

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 3.2.1 Au focus des WCAG 2.1.

REMARQUE: Certains documents composés et leurs agents utilisateurs sont conçus pour offrir des fonctions d’affichage et de modification très différentes selon la partie du document composé où les interactions ont lieu (par exemple, une présentation qui contient une feuille de calcul intégrée, dans laquelle les menus et les barres d’outils de l’agent utilisateur changent selon que l’utilisateur interagit avec le contenu de la présentation ou celui de la feuille de calcul intégrée). Si l’utilisateur utilise un mécanisme autre que celui de mettre la Au focus sur la partie du document composite avec laquelle il veut interagir (p. ex. par un choix de menu ou un mouvement spécial de clavier), tout changement de contexte qui en résulterait ne serait pas soumis à ce critère de succès parce qu’il n’a pas été causé par un déplacement de la Au focus.

C.10.3.2.1 Au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez si le document n’échoue pas au critère de succès 3.2.1 Au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.1 Au focus des WCAG 2.1.

10.3.2.2 À la saisie

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 3.2.2 À la saisie des WCAG 2.1.

C.10.3.2.2 À la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez que le document n’échoue pas au critère de succès 3.2.2 À la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.2 À la saisie des WCAG 2.1.

10.3.3 Assistance à la saisie
Clause de la norme EN 301 549Détermination de la conformité

10.3.3.1 Identification des erreurs

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

C.10.3.3.1 Identification des erreurs

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez que le document n’échoue pas au critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

10.3.3.2 Étiquettes ou instructions

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

C.10.3.3.2 Étiquettes ou instructions

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez que le document n’échoue pas au critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

10.3.3.3 Suggestion après une erreur

Dans le cas où la technologie n’est pas un document Web, celle-ci doit satisfaire au critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

C.10.3.3.3 Suggestion après une erreur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifiez que le document n’échoue pas au critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

Résultat:

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

10.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.13.

Tableau 10.13: Critère de succès du document: Prévention des erreurs (juridiques, financières, de données)

Lorsqu’un document donne lieu à des engagements juridiques ou à des transactions financières de la part de l’utilisateur qui soit modifient ou effacent des données contrôlables par l’utilisateur dans des systèmes de stockages de données, soit enregistrent les réponses de l’utilisateur à un test ou un examen, au moins l’une des conditions suivantes est vraie:

1. Réversible: les actions d’envoi sont réversibles

2. Vérifiée: les données saisies par l’utilisateur sont vérifiées au niveau des erreurs de saisie et la possibilité est donnée à l’utilisateur de les corriger.

3. Confirmée: un mécanisme est disponible pour revoir, confirmer et corriger les informations avant leur soumission finale.

REMARQUE: Ce critère de succès est identique au critère de succès 3.3.4 Prévention des erreurs (juridique, financier, de données) des WCAG 2.1après remplacement de « pages Web » par « documents ».

C.10.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.13.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.4 Robuste
10.4.1 Compatible
Clause de la norme EN 301 549Détermination de la conformité

10.4.1.1 Analyse syntaxique

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.14.

Tableau 10.14: Critère de succès du document: Analyse syntaxique

Lorsqu’un document utilise un langage de balisage de telle sorte que le balisage est visible et mis à la disposition des technologies d’assistance et des fonctions d’accessibilité du logiciel ou à un agent utilisateur sélectionnable par l’utilisateur, les éléments ont des balises de début et de fin complètes, les éléments sont imbriqués selon leurs spécifications, les éléments ne contiennent pas d’attributs en double et tout identifiant est unique, sauf lorsque les spécifications permettent ces fonctions.

REMARQUE 1: Les balises de début et de fin auxquelles il manque un caractère critique, comme une parenthèse fermante ou un guillemet de valeur d’attribut mal appropriée, sont considérées incomplètes.

REMARQUE 2: Le balisage n’est pas toujours mis à la disposition des technologies d’assistance ou des agents utilisateurs sélectionnables par l’utilisateur tels que les navigateurs. Dans de tels cas, la conformité à cette disposition n’aurait aucune incidence sur l’accessibilité, comme c’est le cas pour le contenu Web lorsqu’il est exposé.

REMARQUE 3: Les exemples de balisage qui sont exposés séparément et disponibles pour les technologies d’assistance et les agents utilisateurs comprennent, sans s’y limiter: les documents encodés en HTML, ODF et OOXML. Dans ces exemples, le balisage peut être entièrement analysé de deux façons: a) par des technologies d’assistance qui peuvent ouvrir directement le document, b) par des technologies d’assistance utilisant des API DOM d’agents utilisateurs pour ces formats de document.

REMARQUE 4: Ce critère de succès est identique au critère de succès 4.1.1 Analyse syntaxique des WCAG 2.1 après remplacement de « Dans le contenu mis en œuvre en utilisant des langages de balisage » par « Lorsqu’un document utilise un langage de balisage de telle sorte que le balisage est visible et mis à la disposition des technologies d’assistance et des fonctions d’accessibilité du logiciel ou à un agent utilisateur sélectionnable par l’utilisateur » et après l’ajout des notes 2 et 3 ci-dessus.

C.10.4.1.1 Analyse syntaxique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.14.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.4.1.2 Nom, rôle et valeur

Lorsque la TIC n’est pas un document Web, elle doit satisfaire au critère de succès indiqué dans le tableau 10.15.

Tableau 10.15: Critère de succès du document: Nom, rôle et valeur

Pour tout composant d’interface utilisateur (comprenant, mais n’étant pas limité aux éléments de formulaire, liens et composants générés par des scriptes), le nom et le rôle peuvent être déterminés par un programme informatique ; les états, les propriétés et les valeurs qui peuvent être paramétrés par l’utilisateur peuvent être définis par un programme informatique ; et la notification des changements de ces éléments est disponible aux agents utilisateurs, incluant les technologies d’assistance.

REMARQUE 1: Ce critère de succès s’adresse principalement aux développeurs de logiciels qui développent ou utilisent des composants d’interface utilisateur personnalisés. Les composants d’interface utilisateur standard de la plupart des plateformes qui prennent en charge l’accessibilité répondent déjà à ce critère de succès lorsqu’ils sont utilisés conformément aux spécifications.

REMARQUE 2: Pour les formats de documents qui prennent en charge l’interopérabilité avec la technologie d’assistance, les composants d’interface utilisateur standard satisfont souvent à ce critère de succès lorsque leur usage est conforme aux indications générales en matière de conception et d’accessibilité pour le format du document.

REMARQUE 3: Ce critère de succès est identique au critère de succès 4.1.2 Nom, rôle et valeur des WCAG 2.1 après remplacement de la note originale des WCAG 2.1 par note 1 et après ajout de la note 2 ci-dessus.

C.10.4.1.2 Nom, rôle et valeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC n’est pas un document Web.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès indiqué dans le tableau 10.15.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

10.4.1.3 Messages d’état

Tableau 10.15: Critère de succès du document: Nom, rôle et valeur

Lorsque la TIC est un document non Web, elle doit satisfaire critère de succès 4.1.3 Messages d’état des WCAG 2.1.

C.10.4.1.3 Messages d’état

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un document non Web

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 4.1.3 Messages d’état des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

Non applicable : La condition préalable 1 n’est pas remplie ou le document non Web ne renferme pas de contenu pertinent pour le critère de succès 4.1.3 Messages d’état des WCAG 2.1.

10.5 Positionnement des sous-titres

Lorsque la TIC est un document hors ligne qui contient des médias synchronisés avec des sous-titres, ces sous-titres ne doivent pas masquer l’information pertinente contenue dans les médias synchronisés.

C.10.5 Positionnement des sous-titres

La clause 10.5 est un avis seulement et ne contient aucune exigence testable.

10.6 Synchronisation de la audio description

Lorsque la TIC est un document hors ligne qui contient un média synchronisé avec description sonore, cette description sonore ne doit pas interférer avec les informations audio pertinentes du média synchronisé.

C.10.6 Synchronisation de la audio description

La clause 10.6 est un avis seulement et ne contient aucune exigence testable.

11 Logiciels

Clause de la norme EN 301 549Détermination de la conformité

11.0 Généralités (information)

Cette clause précise les exigences qui s’appliquent:

  • aux logiciels de plateformes;
  • aux logiciels qui ont une interface utilisateur, y compris le contenu du logiciel;
  • aux outil-auteurs;
  • aux logiciels qui servent de technologie d’assistance.

REMARQUE 1: L’agent utilisateur est un exemple de logiciel qui possède une interface utilisateur.

REMARQUE 2: Les exigences relatives au contenu Web, notamment aux logiciels qui sont du contenu Web, se trouvent à La clause 9.

REMARQUE 3: Les exigences relatives aux documents, qui peuvent être présentés par les agents utilisateurs, se trouvent à La clause 10.

REMARQUE 4: Bien que l’accessibilité des interfaces de ligne de commande ne soit pas abordée dans le présent document, l’accessibilité peut être réalisée au moyen d’exigences contextuelles, dont certaines se trouvent dans les clauses 5 et 11.

Les exigences des clauses 11.1 à 11.5 s’appliquent aux logiciels:

  • qui ne sont pas des pages Web;
  • qui ne sont pas intégrés dans une page Web ni utilisés dans le rendu ou le fonctionnement de la page.

La clause 9 énonce les exigences de conformité des logiciels qui se trouvent dans des pages Web ou qui sont intégrés dans des pages Web, et qui sont utilisés dans le rendu ou qui sont destinés à être rendus avec la page Web dans laquelle ils sont intégrés.

Certaines exigences des clauses 11.1 à 11.5 ont des versions différentes selon que la fonctionnalité est non restreinte ou restreinte. Dans ces cas, La clause correspondante est divisée en deux sous-dispositions.

Les critères de succès énoncés dans les clauses 11.1 à 11.5 visent à s’harmoniser avec la Note du groupe de travail [i.26] produite par le WCAG2ICT Task Force du W3C.

REMARQUE 5: Le logiciel qui fournit une interface utilisateur comprend son propre contenu. Voici quelques exemples de contenu présent dans un logiciel: les composants d’interface et le texte d’une barre de menu issus d’une application d’interface utilisateur graphique, les icônes d’une barre d’outils, les invites prononcées dans une interface utilisateur audio, les autres commandes d’interaction utilisateur et les textes, graphiques ou documents qui sont chargés à l'extérieur du logiciel.

C.11.0 Généralités (information)

La clause 11.0 n’a qu’une valeur informative et ne contient aucune exigence relative aux tests de conformité.

11.1 Perceptible
11.1.1 Équivalents textuels
11.1.1.1 Contenu non textuel
Clause de la norme EN 301 549Détermination de la conformité

11.1.1.1.1 Contenu non textuel (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

REMARQUE: Les CAPTCHAS n’apparaissent pas actuellement hors du Web. Cependant, s’ils apparaissent, la présente directive est pertinente.

C.11.1.1.1.1 Contenu non textuel (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.1.1.1.2 Contenu non textuel (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, cette technologie satisfait à l’exigence 5.1.3.6 (sortie vocale pour contenu non textuel).

C.11.1.1.1.2 Contenu non textuel (fonction restreinte)

Type d’évaluation

Examen

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. Le contenu non textuel est présenté aux utilisateurs via la sortie vocale.

Procédure

1. Vérifier que la sortie vocale est fournie comme solution de rechange au contenu non textuel.

2. Vérifier que le contenu non textuel n’est pas seulement présent à titre décoratif.

3. Vérifier que le contenu non textuel n’est pas utilisé uniquement pour le formatage visuel.

4. Vérifier que la sortie vocale est conforme aux indications relatives à l’ équivalent textuel » décrit dans les critères de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite: Les énoncés testables nos 1, 2, 3 et 4 sont vrais; ou le no 1 et le no 2 sont faux; ou le no 1 et le no 3 sont faux.

Échec: L’énoncé testable no 1 est vrai et le no 2 est faux; ou le no 1 est vrai et le no 3 est faux; ou les nos 1, 2 et 3 sont vrais et le no 4 est faux.

Non applicable : La condition préliminaire 1, 2 ou 3 n’est pas remplie.

11.1.2 Médias temporels
11.1.2.1 Contenu seulement audio et seulement vidéo (préenregistré)
Clause de la norme EN 301 549Détermination de la conformité

11.1.2.1.1 Contenu seulement audio et seulement vidéo (pré-enregistré – fonction non restreinte)

Dans le cas où la TIC est un logiciel non-Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran et où un contenu audio préenregistré n’est pas nécessaire pour permettre l’utilisation des fonctions restreintes des TIC, la technologie remplit le Critère de succès 1.2.1 Contenu seulement audio et seulement vidéo (pré-enregistré) des WCAG 2.1.

REMARQUE: Le média de remplacement peut être fourni directement dans le logiciel – ou fourni dans une version de remplacement qui satisfait au critère de succès.

C.11.1.2.1.1 Contenu seulement audio ou vidéo (pré-enregistré – fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. Un contenu audio pré-enregistré n’est pas nécessaire pour permettre l’utilisation des fonctions restreintes de la TIC.

Procédure

1. Vérifier que le document n’échoue pas au critère de succès 1.2.1 Contenu seulement audio ou vidéo (pré-enregistré) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.2.1.2 Contenu seulement audio et seulement vidéo (pré-enregistré – fonction restreinte)
Clause de la norme EN 301 549Détermination de la conformité

11.1.2.1.2.1 Contenu pré-enregistré seulement audio (fonction restreinte)

Lorsque la TIC est un logiciel non-Web qui fournit une interface utilisateur qui ne prend pas en charge les technologies d’assistance pour la lecture d’écran et où des informations auditives pré-enregistrées sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, la fonctionnalité des logiciels qui fournissent une interface utilisateur doit satisfaire à l’exigence 5.1.5 (sortie visuelle pour informations auditives).

C.11.1.2.1.2.1 Contenu pré-enregistré seulement audio (fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. Un contenu audio pré-enregistré est nécessaire pour permettre l’utilisation des fonctions restreintes de la TIC.

Procédure

1. Vérifier que l’information visuelle est équivalente à la sortie auditive pré-enregistrée.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.2.1.2.2 Contenu pré-enregistré seulement vidéo (fonction restreinte)

Dans le cas où la technologie d’information et de communications (TIC) est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit l’exigence 5.1.3.7 (sortie vocale pour information vidéo).

C.11.1.2.1.2.2 Contenu pré-enregistré seulement vidéo (fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. Un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation des fonctions restreintes de la TIC.

4. La sortie vocale est fournie comme mode alternatif à une utilisation sans vision du contenu non textuel affiché sur une fonction restreinte.

Procédure

1. Vérifier que la sortie vocale présente des informations équivalentes pour le contenu vidéo pré-enregistré.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2, 3 ou 4 n’est pas remplie.

11.1.2.2 Sous-titres (pré-enregistrés)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

REMARQUE: La définition de « sous-titres » donnée par les WCAG 2.1 précise que « dans certains pays, les sous-titres sont appelés captions et subtitles ». On les appelle aussi parfois « sous-titres pour malentendants ». Selon la définition des WCAG 2.1, pour satisfaire à ce critère de succès, qu’il s’agisse de captions ou de subtitles, les sous-titres doivent fournir un « visuel synchronisé ou équivalent textuel pour l’information audio avec ou sans paroles nécessaires à la compréhension du contenu d’un média », lorsque l’information sans paroles comprend des « effets sonores, de la musique, des rires, l’identification et le positionnement des interlocuteurs ».

Critères de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1

Comprendre les sous-titres (pré-enregistrés) (en anglais seulement)

Comment satisfaire au critère Sous-titres (pré-enregistrés) (en anglais seulement)

(Niveau A)

Fournir des sous-titres pour tout contenu audio préenregistré dans un média synchronisé, excepté lorsque le média est un média de remplacement pour un texte et qu’il est clairement identifié comme tel.

C.11.1.2.2 Sous-titres (pré-enregistrés)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.2 Sous-titres (pré-enregistrés) des WCAG 2.1.

11.1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré)
Clause de la norme EN 301 549Détermination de la conformité

11.1.2.3.1 Audio-description ou version de remplacement pour un média temporel (pré-enregistré et fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 1.2.3 audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

REMARQUE 1: La définition des WCAG 2.1 précise qu’ « audio-description » est également nommée « vidéo-description » et « narration descriptive ».

REMARQUE 2: Des pistes audio secondaires ou de remplacement sont couramment utilisées à cette fin.

C.11.1.2.3.1 Audio-description ou version de remplacement pour un média temporel (pré-enregistré et fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.2.3 audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

11.1.2.3.2 Audio-description ou version de remplacement pour un média temporel (pré-enregistré et fonction restreinte)

Dans le cas où la technologie d’information et de communications (TIC) est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit l’exigence 5.1.3.7 (sortie vocale pour information vidéo).

C.11.1.2.3.2 Audio-description ou version de remplacement pour un média temporel (pré-enregistré et fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. La sortie vocale est fournie comme mode alternatif à une utilisation sans vision du contenu non textuel affiché sur une fonction restreinte.

Procédure

1. Vérifier que la sortie vocale présente des informations équivalentes pour le contenu vidéo pré-enregistré.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.2.4 Sous-titres (en direct)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

REMARQUE: La définition de « sous-titres » donnée par les WCAG 2.1 précise que « dans certains pays, les sous-titres sont appelés captions et subtitles ». On les appelle aussi parfois « sous-titres pour malentendants ». Selon la définition des WCAG 2.1, pour satisfaire à ce critère de succès, qu’il s’agisse de captions ou de subtitles, les sous-titres doivent fournir un « visuel synchronisé ou équivalent textuel pour l’information audio avec ou sans paroles nécessaires à la compréhension du contenu d’un média », lorsque l’information sans paroles comprend des « effets sonores, de la musique, des rires, l’identification et le positionnement des interlocuteurs ».

C.11.1.2.4 Sous-titres (en direct)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.4 Sous-titres (en direct) des WCAG 2.1.

11.1.2.5 Audio-description (pré-enregistrée)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.2.5 audio-description (pré-enregistrée) des WCAG 2.1.

REMARQUE 1: La définition des WCAG 2.1 précise « audio-description » est également nommée « vidéo-description » et « narration descriptive ».

REMARQUE 2: Des pistes audio secondaires ou de remplacement sont couramment utilisées à cette fin.

C.11.1.2.5 Audio-description (pré-enregistrée)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.2.5 audio-description(pré-enregistrée) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.2.5 Audio-description (pré-enregistrée) des WCAG 2.1).

11.1.3 Adaptable
11.1.3.1 Information et relations
Clause de la norme EN 301 549Détermination de la conformité

11.1.3.1.1 Information et relations (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE: Dans le domaine des logiciels, la meilleure façon de déterminer par un programme informatique est d’utiliser les services d’accessibilité fournis par les logiciels de plateforme visant à permettre l’interopérabilité entre les logiciels et les technologies d’assistance et les fonctions d’accessibilité des logiciels. (voir La clause 11.5 Interopérabilité avec la technologie d’assistance).

C.11.1.3.1.1 Information et relations (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 1.3.1 Information et relations des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.1.3.1.2 Information et relations (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran et où l’information affichée à l’écran, la TIC devrait fournir des informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio et l’information affichée à l’écran.

REMARQUE 1: De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que la du focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2: Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées par la présentation.

C.11.1.3.1.2 Information et relations (fonction restreinte)

Clause 11.1.3.1.2 est un avis seulement et ne contient aucune exigence testable.

11.1.3.2 Ordre séquentiel logique
Clause de la norme EN 301 549Détermination de la conformité

11.1.3.2.1 Ordre séquentiel logique (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

C.11.1.3.2.1 Ordre séquentiel logique (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.1.3.2.2 Ordre séquentiel logique (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran et où l’information affichée à l’écran, la TIC devrait fournir des informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio et l’information affichée à l’écran.

REMARQUE 1: De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que la du focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2: Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées par la présentation.

C.11.1.3.2.2 Ordre séquentiel logique (fonction restreinte)

Clause 11.1.3.2.2 est un avis seulement et ne contient aucune exigence testable.

11.1.3.3 Caractéristiques sensorielles

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

C.11.1.3.3 Caractéristiques sensorielles

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.3.3 Caractéristiques sensorielles des WCAG 2.1.

11.1.3.4 Orientation

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

C.11.1.3.4 Orientation

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.3.4 Orientation des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès critère de succès 1.3.4 Orientation des WCAG 2.1.

11.1.3.5 Identifier la finalité de la saisie
Clause de la norme EN 301 549Détermination de la conformité

11.1.3.5.1 Identifier la finalité de la saisie (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit remplir le Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

C.11.1.3.5.1 Identifier la finalité de la saisie (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1

11.1.3.5.2 Identifier la finalité de la saisie (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui est restreint aux technologies d’assistance, elle doit prévoir au moins un mode de fonctionnement selon lequel l’utilisateur est présenté, sous forme audio, la finalité de chaque champ de saisie recueillant des renseignements sur l’utilisateur, lorsque ce champ sert une finalité définie à la section Critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

C.11.1.3.5.2 Identifier la finalité de la saisie (fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. La sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte.

Procédure

1. Vérifier que la sortie sonore est fournie par le biais d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci.

2. Vérifier que la sortie sonore est fournie au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

3. Vérifier que la sortie sonore comprend la finalité de la section Finalité de saisie des composants d’interface utilisateur

Résultat

Réussite : L’énoncé testable (no 1 ou no 2) est vrai et l’énoncé testable no 3 est vrai.

Échec : Les énoncés testables (nos 1 et 2) sont faux ou l’énoncé testable no 3 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.4 Distinguable
Clause de la norme EN 301 549Détermination de la conformité

11.1.4.1 Utilisation de la couleur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

C.11.1.4.1 Utilisation de la couleur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.1 Utilisation de la couleur des WCAG 2.1.

11.1.4.2 Contrôle du son

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès indiqué dans le tableau 11.1.

Tableau 11.1: Critère de succès du logiciel: Contrôle du son

Si la lecture d’un fichier audio tiré d’un document dure plus de 3 secondes, un mécanisme est disponible pour le mettre en pause, l’arrêter ou pour en contrôler le volume de façon indépendante du niveau de volume du système général.

REMARQUE 1: Puisque toute partie d’un document ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le document entier, tout le contenu présent dans le document (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) doit satisfaire à ce critère de succès.

REMARQUE 2: Ce critère de succès est identique au critère de succès 1.4.2 Contrôle du son des WCAG 2.1, après remplacement de « sur une page Web » par « sur un document », de « tout contenu » par « toute partie d’un document », de « page entière » par « document entier », de « sur la page Web » par « sur le document », après suppression de « Voir l’exigence de conformité 5: Non-interférence » et après l’ajout de la note 1.

C.11.1.4.2 Contrôle du son

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.1.4.3 Contraste (minimum)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

C.11.1.4.3 Contraste (minimum)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.3 Contraste (minimum) des WCAG 2.1.

11.1.4.4 Redimensionnement du texte
Clause de la norme EN 301 549Détermination de la conformité

11.1.4.4.1 Redimensionnement du texte (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux fonctions d’élargissement de la plateforme ou de la technologie d’assistance, elle remplit le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

REMARQUE 1: Les contenus pour lesquels il existe des lecteurs de logiciels, des visualiseurs ou des éditeurs dotés d’une fonction de zoom de 200% répondraient automatiquement à ce critère de succès lorsqu’ils sont utilisés avec ces lecteurs, à moins que le contenu ne fonctionne pas avec le zoom.

REMARQUE 2: Ce critère de succès concerne la capacité de permettre aux utilisateurs d’agrandir le texte à l’écran au moins jusqu’à 200% sans avoir besoin d’avoir recours à des technologies d’assistance. Cela signifie que l’application fournit un moyen d’agrandir le texte à 200% (zoom ou autre) sans perte de contenu ou de fonctionnalité ou que l’application fonctionne avec les fonctions de la plateforme qui répondent à cette exigence.

C.11.1.4.4.1 Redimensionnement du texte (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge les fonctions d’élargissement de la plateforme ou de la technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.4 Redimensionnement du texte des WCAG 2.1.

11.1.4.4.2 Redimensionnement du texte (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne pas prend en charge l’accès aux fonctions d’agrandissement de la plateforme ou à la technologie d’assistance, elle remplit l’exigence 5.1.4 (fonction restreinte à l’agrandissement du texte).

REMARQUE: Comme la prise en charge du texte dans un environnement restreinte peut être plus limitée que celle des agents utilisateurs pour le Web, satisfaire au critère 11.1.4.4.2 dans un environnement restreint peut imposer un fardeau beaucoup plus lourd à l’auteur du contenu.

C.11.1.4.4.2 Redimensionnement du texte (fonction restreinte)

Type d’évaluation

Inspection et établissement de mesures

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur est restreinte aux fonctions d’agrandissement de la plateforme ou de la technologie d’assistance.

3. Une distance de visualisation est définie par le fournisseur.

Procédure

1. Mesurer la hauteur de la lettre H en majuscule.

2. Vérifier qu’il sous-entend un angle d’au moins 0,7 degré à la distance de visualisation définie.

Résultat

Réussite: L’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.4.5 Texte sous forme d’image
Clause de la norme EN 301 549Détermination de la conformité

11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

Critère 1.4.5 Texte sous forme d’image

Comprendre le texte sous forme d’image (en anglais seulement)

Comment satisfaire au critère Texte sous forme d’image (en anglais seulement)

(Niveau AA)

Si les technologies utilisées peuvent réaliser la présentation visuelle, le texteest utilisé pour véhiculer de l’information plutôt que du texte sous forme d’image, sauf dans les cas suivants:

· Personnalisable: Le texte sous forme d’image peut être personnalisé visuellement selon les exigences de l’utilisateur;

· Essentielle: Une présentation spécifique du texte est essentielle à l’information véhiculée.

Remarque: Les logotypes sont considérés comme essentiels (le texte qui fait partie d’un logo ou d’un nom de marque).

C.11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

11.1.4.5.2 Texte sous forme d’image (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge les technologies d’assistance pour la lecture d’écran, il n’est pas nécessaire qu’elle remplisse le critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1, car il n’y a pas lieu d’imposer une exigence à toutes les fonctions restreintes que le texte affiché à l’écran soit effectivement représenté en interne sous forme de texte (au sens des WCAG 2.1) puisqu’il n’y a pas d’interopérabilité avec les technologies d’assistance.

Critère 1.4.5 Texte sous forme d’image

Comprendre le texte sous forme d’image (en anglais seulement)

Comment satisfaire au critère Texte sous forme d’image (en anglais seulement)

(Niveau AA)

Si les technologies utilisées peuvent réaliser la présentation visuelle, le texteest utilisé pour véhiculer de l’information plutôt que du texte sous forme d’image, sauf dans les cas suivants:

  • Personnalisable: Le texte sous forme d’image peut être personnalisé visuellement selon les exigences de l’utilisateur;
  • Essentielle: Une présentation spécifique du texte est essentielle à l’information véhiculée.

Remarque: Les logotypes sont considérés comme essentiels (le texte qui fait partie d’un logo ou d’un nom de marque).

C.11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. Le contenu non textuel est présenté aux utilisateurs via la sortie vocale.

Procédure

1. Vérifier que la sortie vocale est fournie comme solution de rechange au contenu non textuel.

2. Vérifier que le contenu non textuel n’est pas seulement présent à titre décoratif.

3. Vérifier que le contenu non textuel n’est pas utilisé uniquement pour le formatage visuel.

4. Vérifier que la sortie vocale est conforme aux indications relatives à l’« équivalent textuel » décrit dans le critère de succès 1.1.1 Contenu non textuel des WCAG 2.1.

Résultat

Réussite : Les énoncés testables (nos 1, 2, 3 et 4) sont vrais ou le (no 1 et le no 2) sont faux ou le (no 1 et le no 3) sont faux.

Échec : L’énoncé testable (no 1 est vrai et le no 2 est faux); ou (le no 1 est vrai et le no 3 est faux); ou les (nos 1, 2 et 3 sont vrais et le no 4 est faux).

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.1.4.10 Redistribution

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès indiqué dans le tableau 11.2.

Tableau 11.2: Documenter le critère de succès: Redistribution

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • Contenu à défilement vertical d’une largeur équivalente à 320 pixels CSS;
  • Contenu à défilement horizontal d’une hauteur équivalente à 256 pixels CSS;

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1: 320 pixels CSS équivalent à une largeur de fenêtre de départ de 1 280 pixels CSS avec un zoom de 400%. Pour les logiciels non Web qui sont conçus pour défiler horizontalement (par exemple avec du texte vertical), les 256 pixels CSS équivalent à une hauteur de fenêtre de départ de 1 024 pixels avec un zoom de 400%.

REMARQUE 2: Les exemples de contenu qui nécessitent une mise en page bidimensionnelle sont les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données et les interfaces où il est nécessaire de garder les barres d’outils en vue pendant la manipulation du contenu.

REMARQUE 3: Ce critère de succès est identique au critère de succès 1.4.10 Redisposition des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

C.11.1.4.10 Redistribution

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.2.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.1.4.11 Contraste du contenu non textuel

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

C.11.1.4.11 Contraste du contenu non textuel

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas le Critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.11 Contraste des éléments non textuels des WCAG 2.1.

11.1.4.12 Espacement du texte

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

C.11.1.4.12 Espacement du texte

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

1. Vérifier que le logiciel n’échoue pas le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

11.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

C.11.1.4.13 Contenu au survol ou au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le Critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

11.2 Utilisable
11.2.1 Accessibilité au clavier
11.2.1.1 Clavier
Clause de la norme EN 301 549Détermination de la conformité

11.2.1.1.1 Clavier (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès à des claviers ou à une interface clavier, elle doit satisfaire au critère de succès 2.1.1 Clavier des WCAG 2.1.

REMARQUE: cela ne signifie pas qu’un logiciel est nécessaire pour prendre directement en charge un clavier ou une « interface clavier ». Cela n’implique pas non plus qu’un logiciel soit requis pour fournir un clavier programmable. Le logiciel de plateforme sous-jacent peut fournir des services de saisie indépendants de dispositifs à des applications qui assurent l’exploitation à l’aide d’un clavier. Le logiciel qui prend en charge l’exploitation par l’intermédiaire de ces services indépendants pourrait être utilisé par un clavier et serait conforme.

C.11.2.1.1.1 Clavier (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge les claviers ou une interface clavier.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 2.1.1 Clavier des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.1 Clavier des WCAG 2.1.

11.2.1.1.2 Clavier (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier: fonction restreinte).

C.11.2.1.1.2 Clavier (fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur est restreinte aux claviers ou aux interfaces clavier.

Procédure

1. Vérifier que toutes les fonctions de l’interface utilisateur sont utilisables sans vision.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.2.1.2 Pas de piège au clavier

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès indiqué dans le tableau 11.3.

Tableau 11.3: Critère de succès du logiciel: Pas de piège au clavier

Si la du focus du clavier peut être positionnée sur un élément du logiciel à l’aide d’une interface clavier, réciproquement, il peut être déplacé hors de ce même composant simplement à l’aide d’une interface clavier et, si ce déplacement exige plus que l’utilisation d’une simple touche flèche ou tabulation ou toute autre méthode standard de sortie, l’utilisateur est informé de la méthode permettant de déplacer la du focus hors de ce composant.

REMARQUE 1: puisque toute partie d’un logiciel ne satisfaisant pas à ce critère de succès peut interférer avec la capacité de l’utilisateur à exploiter le logiciel entier, il est nécessaire que tout le contenu présent dans le logiciel (qu’il soit utilisé pour satisfaire à d’autres critères de succès ou non) satisfasse à ce critère de succès.

REMARQUE 2: La méthode standard de sortie pourrait varier d’une plateforme à l’autre. Par exemple, la touche Échap est une méthode standard de sortie sur de nombreuses plateformes de bureau.

REMARQUE 3: ce critère de succès est identique au critère de succès 2.1.2 Pas de piège au clavier des WCAG 2.1 à clavier après remplacement de « contenu », « page » et « page Web » par « logiciel », après suppression de « Voir l’exigence de conformité 5: Non-interférence », après l’ajout de la note 2 ci-dessus et la reformulation de la note 1 ci-dessus de manière à éviter le verbe « devoir ».

C.11.2.1.2 Pas de piège au clavier

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.3.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.2.1.4 Raccourcis clavier des caractères
Clause de la norme EN 301 549Détermination de la conformité

11.2.1.4.1 Raccourcis clavier utilisant des caractères (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au Critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

C.11.2.1.4.1 Raccourcis clavier utilisant des caractères (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas au Critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

11.2.1.4.2 Raccourcis clavier utilisant des caractères (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier: fonction restreinte).

C.11.2.1.4.2 Raccourcis clavier utilisant des caractères (fonction restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La fonctionnalité des TIC est f restreintes aux claviers ou aux interfaces clavier.

2. La fonctionnalité des TIC est restreintes aux claviers ou aux interfaces clavier.

Procédure

1. Vérifier que toutes les fonctions sont utilisables sans vision.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.2.2 Délai Suffisant
Clause de la norme EN 301 549Détermination de la conformité

11.2.2.1 Réglage du délai

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès indiqué dans le tableau 11.4.

Tableau 11.4: Critère de succès du logiciel: réglage du délai

Pour chaque limite de temps fixée par le logiciel, au moins l’un des points suivants est vrai:

  • Suppression : l’utilisateur a la possibilité de supprimer la limite de temps avant de la rencontrer ; ou
  • Ajustement : l’utilisateur a la possibilité d’ajuster la limite de temps avant de la rencontrer dans un intervalle d’au moins dix fois la durée paramétrée par défaut ; ou
  • Extension: l’utilisateur est averti avant que la limite de temps expire et il lui est accordé au moins 20 secondes pour étendre cette limite par une action simple (par exemple, « appuyer sur la barre d’espace ») et l’utilisateur a la possibilité d’étendre la limite de temps au moins dix fois.
  • Extension : l’utilisateur est averti avant que la limite de temps n’expire et il lui est accordé au moins 20 secondes pour étendre cette limite par une action simple (par exemple, « appuyer sur la barre d’espace ») et l’utilisateur a la possibilité d’étendre la limite de temps au moins dix fois ; ou
  • L’exception du temps réel : la limite de temps est une partie constitutive d’un événement en temps réel (par exemple, une enchère) et aucune alternative n’est possible ; ou
  • L’exception de la limite essentielle : la limite de temps est essentielleessentielle et l’étendre invaliderait alors l’activité ; ou
  • L’exception des 20 heures : la limite de temps est supérieure à 20 heures.

REMARQUE 1: Ce critère de succès permet de s’assurer que les utilisateurs peuvent accomplir les tâches sans changements inattendus dans le contenu ou le contexte résultant d’une limite de temps. Ce critère de succès doit être considéré conjointement avec le critère de succès 3.2.1 des WCAG 2.1, qui impose des limites aux changements de contenu ou de contexte résultant de l’action des utilisateurs.

REMARQUE 2: ce critère de succès est identique au critère de succès 2.2.1 Réglage du délai des WCAG 2.1, après remplacement de « le contenu » par « logiciel » et l’ajout des mots « des WCAG 2.1 » après les mots « critère de succès » à la note 1 ci-dessus.

C.11.2.2.1 Réglage du délai

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.4.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Échec: L’énoncé testablNon applicable : La condition préalable 1 n’est pas remplie.

11.2.2.2 Mettre en pause, arrêter, masquer

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès indiqué dans le tableau 11.5.

Tableau 11.5: Critère de succès du logiciel: mettre en pause, arrêter, masquer

Pour déplacer, faire clignoter, faire défiler ou mettre à jour automatiquement des informations, tous les éléments suivants sont vrais:

  • Déplacement, clignotement, défilement: pour toute information en mouvement, clignotante ou défilante qui (1) démarre automatiquement, (2) dure plus de cinq secondes et (3) est présentée en parallèle avec d’autres contenus, il existe un mécanisme permettant à l’utilisateur de mettre en pause, d’arrêter ou de masquer l’information à moins que le déplacement, le clignement ou le défilement fasse partie d’une activité où cela est essentiel.
  • Mise à jour automatique: pour toute mise à jour qui (1) démarre automatiquement et (2) est présentée en parallèle avec d’autres contenus, il existe un mécanisme permettant à l’utilisateur de la mettre en pause, de l’arrêter, de la masquer ou de contrôler sa fréquence, sauf si la mise à jour automatique fait partie d’une activité où elle est essentielle.

REMARQUE 1: Pour les exigences relatives au contenu clignotant ou avec flash, se référer à la règle 2.3 des WCAG 2.1.

REMARQUE 2: ce critère de succès s’applique à tout le contenu du logiciel (qu’il existe ou non un autre mode de fonctionnement accessible du logiciel), car toute partie d’un logiciel qui ne satisfait pas à ce critère de succès peut nuire à la capacité de l’utilisateur d’utiliser le logiciel en entier (y compris un élément d’interface utilisateur qui lui permet d’activer le deuxième mode accessible).

REMARQUE 3: Il n’est pas exigé que le contenu mis à jour périodiquement par logiciel ou diffusé en flux à l’agent utilisateur conserve ou présente l’information générée ou reçue entre la mise en pause et la reprise de la présentation, puisque cela peut ne pas être techniquement possible et s’avérer trompeur dans beaucoup de situations.

REMARQUE 4: Une animation survenant dans une phase de pré-chargement ou dans une situation similaire peut être considérée comme essentielle si aucune interaction n’est permise à tous les utilisateurs durant cette phase et si l’absence d’indication de progression est susceptible de perturber les utilisateurs ou de leur faire croire que le contenu est figé ou défectueux.

REMARQUE 5: cela s’applique à tous les contenus. Tout contenu, informatif ou décoratif, qui est mis à jour automatiquement, clignote ou bouge peut créer un obstacle à l’accessibilité.

REMARQUE 6: ce critère de succès est identique au critère de succès 2.2.2 Mettre en pause, arrêter, masquer des WCAG 2.1, après remplacement de « page » et de « page Web » par « logiciel », suppression de « Voir l’exigence de conformité 5: non-ingérence » dans la note 2 du critère de succès, l’ajout des mots « des WCAG 2.1 » à la suite de « règle » à la note 1, la reformulation de la note 2 de façon à éviter le verbe « devoir » et l’ajout de la note 5 ci-dessus.

C.11.2.2.2 Mettre en pause, arrêter, masquer

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.5.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.2.3 Crises et réactions physiques
Clause de la norme EN 301 549Détermination de la conformité

11.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès indiqué dans le tableau 11.6.

Tableau 11.6: Critère de succès du logiciel: Pas plus de trois flashs ou sous le seuil critique

Un logiciel doit être exempt de tout élément qui flashe plus de trois fois dans n’importe quel intervalle d’une seconde ou ce flash doit se situer sous le seuil de flash générique et le seuil de flash rouge.

REMARQUE 1: ce critère de succès s’applique à tout le contenu du logiciel (qu’il existe ou non un autre mode de fonctionnement accessible du logiciel), car toute partie d’un logiciel qui ne satisfait pas à ce critère de succès peut nuire à la capacité de l’utilisateur d’utiliser le logiciel en entier (y compris un élément d’interface utilisateur qui lui permet d’activer le deuxième mode accessible).

REMARQUE 2: ce critère de succès est identique au critère de succès 2.3.1 Pas plus de trois flashs des WCAG 2.1 après remplacement de « pages Web » par « logiciel », de « la page entière » par « le logiciel entier », « la page Web » par « le logiciel », après suppression de « Voir l’exigence de conformité 5: Non-ingérence » et après la reformulation de la note 1 ci-dessus pour éviter le verbe « devoir ».

C.11.2.3.1 Pas plus de trois flashs ou sous le seuil critique

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.6.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.2.4 Navigable
Clause de la norme EN 301 549Détermination de la conformité

11.2.4.3 Parcours du focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès indiqué dans le tableau 11.7.

Tableau 11.7: Critère de succès du logiciel: Parcours du focus

Si un logiciel peut être parcourue de façon séquentielle et que les séquences de navigation affectent la signification ou l’action, les éléments reçoivent la du focus dans un ordre qui préserve la signification et l’opérabilité.

REMARQUE: ce critère de succès est identique au critère de succès 2.4.3 Parcours de la cible de saisie des WCAG 2.1 après le remplacement de « page Web » par « logiciel ».

C.11.2.4.3 Parcours du focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.7.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.2.4.4 Fonction du lien (selon le contexte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

C.11.2.4.4 Fonction du lien (selon le contexte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez que le logiciel n’échoue pas au critère de succès 2.4.4 Objectif du lien (selon le contexte) des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.4 Fonction du lien (selon le contexte) des WCAG 2.1.

11.2.4.6 En-têtes et étiquettes

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

REMARQUE: dans un logiciel, les en-têtes et les étiquettes sont utilisés pour décrire les sections du contenu et les contrôles respectivement. Dans certains cas, il peut être difficile de savoir si un élément de texte statique est un en-tête ou une étiquette. Mais qu’il s’agisse d’une étiquette ou d’un en-tête, l’exigence est la même: s’ils sont présents, ils doivent décrire le sujet ou le but des éléments auxquels ils sont associés.

C.11.2.4.6 En-têtes et étiquettes

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.4.6 En-têtes et étiquettes des WCAG 2.1.

11.2.4.7 Visibilité du focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.4.7 Visibilité du focus des WCAG 2.1.

C.11.2.4.7 Visibilité du focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 2.4.7 Visibilité de la cible de saisie des WCAG 2.1 des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès critère de succès 2.4.7 Visibilité du focus des WCAG 2.1.

11.2.5 Modalités d’entrée
Clause de la norme EN 301 549Détermination de la conformité

11.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès indiqué dans le tableau 11.8.

Tableau 11.8: Critère de succès du logiciel: Gestes pour le contrôle du pointeur

Toutes les fonctions qui utilisent des mouvements multipoints ou basés sur un tracé pour exécuter une commande peuvent être utilisées avec un seul pointeur sans mouvement basé sur un tracé, à moins qu’un mouvement multipoint ou basé sur un tracé soit essentiel.

REMARQUE 1: cette exigence s’applique au logiciel non Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 2: ce critère de succès est identique au critère de succès 2.5.1 Mouvements du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

C.11.2.5.1 Gestes pour le contrôle du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.8.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.2.5.2 Annulation de l’action du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès indiqué dans le tableau 11.9.

Tableau 11.9: Critère de succès du logiciel: Annulation de l’action du pointeur

Dans le cas des fonctions qui peuvent fonctionner à l’aide d’un seul pointeur, au moins l’un des éléments suivants est vrai:

  • Aucun événement descendant: l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction
  • Abandonner ou Annuler: l’achèvement de la fonction se fait sur l’événement ascendant (up-event) et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion de l’événement: l’événement montant inverse tout résultat de l’événement descendant précédent.
  • Essentiel: terminer la fonction sur inversion de l’événement est essentiel.

REMARQUE 1: les fonctions qui émulent un appui clavier ou un pavé numérique sont considérées comme essentielles.

REMARQUE 2: cette exigence s’applique au logiciel non Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 3: Ce critère de succès est identique au critère de succès 2.5.2 Annulation du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

C.11.2.5.2 Annulation de l’action du pointeur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.9.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.2.5.3 Étiquette dans le nom
Clause de la norme EN 301 549Détermination de la conformité

11.2.5.3.1 Étiquette dans le nom (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

C.11.2.5.3.1 Étiquette dans le nom (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

11.2.5.3.2 Étiquette dans le nom (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.3 (Corrélation de sortie sonore).

C.11.2.5.3.2 Étiquette dans le nom (fonction restreinte)

La clause 11.2.5.3.2 a pour seul but d’informer et ne contient aucune exigence en matière de test.

11.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

C.11.2.5.4 Activation par le mouvement

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifier que le logiciel n’échoue pas au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

11.3 Compréhensible
11.3.1 Lisible
11.3.1.1 Langue du logiciel
Clause de la norme EN 301 549Détermination de la conformité

11.3.1.1.1 Langue du logiciel (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès indiqué dans le tableau 11.10.

Tableau 11.10: Critère de succès du logiciel: langue du logiciel

La langue par défaut du logiciel peut être déterminée par un programme informatique.

REMARQUE 1: lorsque les plateformes logicielles fournissent un paramètre « endroit/langue », les applications qui utilisent ce paramètre et rendent leur interface propre à cet « endroit » ou cette « langue » seraient conformes à ce critère de succès. Les applications qui n’utilisent pas le paramètre « endroit/langue » de la plateforme, mais qui utilisent une méthode d’exposition de la langue humaine du logiciel basée sur l’accessibilité seraient également conformes à ce critère de succès. Les applications mises en œuvre dans des technologies où les technologies d’assistance ne peuvent pas déterminer la langue humaine et ne prennent pas en charge le paramètre « endroit/langue » de la plateforme peuvent ne pas être en mesure de satisfaire à ce critère de succès pour cet endroit ou cette langue.

REMARQUE 2: ce critère de succès est identique au critère de succès 3.1.1 Langue de la page des WCAG 2.1 après remplacement de « pages Web » par « logiciel » et après l’ajout de la note 1 ci-dessus.

C.11.3.1.1.1 Langue du logiciel (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.10.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.3.1.1.2 Langue du logiciel (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit l’exigence 5.1.3.14 (Langues parlées).

C.11.3.1.1.2 Langue du logiciel (fonction restreinte)

Type d’évaluation

Examen

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

4. La sortie vocale n’est pas utilisée pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement.

5.Le contenu n’est pas généré à l’extérieur et est sous le contrôle du fournisseur de TIC.

6. Les langues affichées peuvent être sélectionnées à l’aide d’un accès non visuel.

7. L’utilisateur n’a pas sélectionné une langue vocale différente de la langue du contenu affiché.

Procédure

1. Vérifier que la sortie vocale est dans la même langue humaine que le contenu affiché.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1, 2, 3, 4, 5, 6 ou 7 n’est pas remplie.

11.3.2 Prévisible
Clause de la norme EN 301 549Détermination de la conformité

11.3.2.1 Au focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au Critère de succès 3.2.1 Au focus des WCAG 2.1.

REMARQUE: Certains documents composés et leurs agents utilisateurs sont conçus pour offrir des fonctions d’affichage et de modification très différentes selon la partie du document composé où les interactions ont lieu (par exemple, une présentation qui contient une feuille de calcul intégrée, dans laquelle les menus et les barres d’outils de l’agent utilisateur changent selon que l’utilisateur interagit avec le contenu de la présentation ou celui de la feuille de calcul intégrée). Si l’utilisateur utilise un mécanisme autre que celui de mettre la du focus sur la partie du document composite avec laquelle il veut interagir (p. ex. par un choix de menu ou un mouvement spécial de clavier), tout changement de contexte qui en résulterait ne serait pas soumis à ce critère de succès parce qu’il n’a pas été causé par un déplacement du focus.

C.11.3.2.1 Au focus

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez si le logiciel n’échoue pas au Critère de succès 3.2.1 Au focus des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.1 Au focus des WCAG 2.1.

11.3.2.2 À la saisie

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 3.2.2 À la saisie des WCAG 2.1.

C.11.3.2.2 À la saisie

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez que le logiciel n’échoue pas au critère de succès 3.2.2 À la saisie des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 3.2.2 À la saisie des WCAG 2.1.

11.3.3 Assistance à la saisie
11.3.3.1 Identification des erreurs
Clause de la norme EN 301 549Détermination de la conformité

11.3.3.1.1 Identification d’erreur (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

C.11.3.3.1.1 Identification d’erreur (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifiez que la page Web n’échoue pas au critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.1 Identification des erreurs des WCAG 2.1.

11.3.3.1.2 Identification d’erreur (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit l’exigence 5.1.3.15 (Identification non visuelle des erreurs).

C.11.3.3.1.2 Identification d’erreur (fonction restreinte)

Type d’évaluation

Examen

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. L’interface utilisateur ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran.

3. La sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte.

4. Une erreur de saisie est automatiquement détectée.

Procédure

1. Vérifiez que la sortie vocale identifie l’élément qui est en erreur.

2. Vérifiez que la sortie vocale décrit l’élément qui est en erreur.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1, 2, 3 ou 4 n’est pas remplie.

11.3.3.2 Étiquettes ou instructions

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

C.11.3.3.2 Étiquettes ou instructions

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez que le logiciel n’échoue pas au critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.2 Étiquettes ou instructions des WCAG 2.1.

11.3.3.3 Suggestion après une erreur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

C.11.3.3.3 Suggestion après une erreur

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez que le logiciel n’échoue pas au critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 3.3.3 Suggestion après une erreur des WCAG 2.1.

11.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès indiqué dans le tableau 11.11.

Tableau 11.11: Critère de succès du logiciel: Prévention des erreurs (juridiques, financières, de données)

Pour les logiciels qui donnent lieu à des engagements juridiques ou à des transactions financières de la part de l’utilisateur qui soit modifient ou effacent des données contrôlables par l’utilisateur dans des systèmes de stockages de données, soit enregistrent les réponses de l’utilisateur à un test ou un examen, au moins l’une des conditions suivantes est vraie:

1. Réversible: les actions d’envoi sont réversibles

2. Vérifiée: les données saisies par l’utilisateur sont vérifiées au niveau des erreurs de saisie et la possibilité est donnée à l’utilisateur de les corriger.

3. Confirmée: un mécanisme est disponible pour revoir, confirmer et corriger les informations avant leur soumission finale.

REMARQUE: Ce critère de succès est identique au critère de succès 3.3.4 Prévention des erreurs (juridique, financier, de données) des WCAG 2.1remplaçant « pages Web » par « logiciel ».

C.11.3.3.4 Prévention des erreurs (juridiques, financières, de données)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

Procédure

1. Vérifiez que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.1.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.4 Robuste
11.4.1 Compatible
11.4.1.1 Analyse syntaxique
Clause de la norme EN 301 549Détermination de la conformité

11.4.1.1.1 Analyse syntaxique (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance, elle remplit le critère de succès indiqué dans le tableau 11.12.

Tableau 11.12: Critère de succès du logiciel: Analyse syntaxique

Pour les logiciels qui utilisent des langages de balisage, de manière à ce que le balisage soit exposé et disponible séparément aux technologies d’assistance et aux fonctions d’accessibilité du logiciel ou à un agent utilisateur sélectionnable par l’utilisateur, les éléments ont des balises de début et de fin complètes, les éléments sont imbriqués selon leurs spécifications, les éléments ne contiennent pas d’attributs en double et tout identifiant est unique, sauf lorsque les spécifications permettent ces fonctions.

REMARQUE 1: Les balises de début et de fin auxquelles il manque un caractère critique, comme une parenthèse fermante ou un guillemet de valeur d’attribut mal appropriée, sont considérées incomplètes.

REMARQUE 2: Le balisage n’est pas toujours mis à la disposition des technologies d’assistance ou des agents utilisateurs sélectionnables par l’utilisateur tels que les navigateurs. Dans de tels cas, la conformité à cette disposition n’aurait aucune incidence sur l’accessibilité, comme c’est le cas pour le contenu Web lorsqu’il est exposé.

REMARQUE 3: Les exemples de balisage qui sont exposés séparément et disponibles pour les technologies d’assistance et les agents utilisateurs comprennent, sans s’y limiter: les documents encodés en HTML, ODF et OOXML. Dans ces exemples, le balisage peut être entièrement analysé de deux façons: (a) par des technologies d’assistance qui peuvent ouvrir directement le document, (b) par des technologies d’assistance utilisant des API DOM d’agents utilisateurs pour ces formats de document.

REMARQUE 4: Les exemples de balisage utilisé à l’interne pour la persistance de l’interface utilisateur du logiciel qui ne sont jamais exposés à la technologie d’assistance comprennent, sans s’y limiter: XUL, GladeXML et FXML. Dans ces exemples, la technologie d’assistance n’interagit qu’avec l’interface utilisateur du logiciel généré.

REMARQUE 5: Ce critère de succès est identique au critère de succès 4.1.1 Analyse syntaxique des WCAG 2.1 en remplaçant « Dans le contenu mis en œuvre en utilisant des langages de balisage » par « Pour les logiciels qui utilisent des langages de balisage, de manière à ce que le balisage soit exposé et disponible séparément aux technologies d’assistance et aux fonctions d’accessibilité du logiciel ou à un agent utilisateur sélectionnable par l’utilisateur » avec l’ajout des notes 2, 3 et 4 ci-dessus.

C.11.4.1.1.1 Analyse syntaxique (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifiez que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.12.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.4.1.1.2 Analyse syntaxique (fonction restreinte)

Sans objet.

REMARQUE : Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui ne prend pas en charge l’accès aux technologies d’assistance, elle ne remplit pas le critère de succès Analyse syntaxique indiqué dans le tableau 11.10, parce que le but de ce critère de succès est d’assurer la cohérence afin que différents agents utilisateurs ou technologies d’assistance donnent le même résultat.

C.11.4.1.1.2 Analyse syntaxique (fonction restreinte)

La clause 11.4.1.1.2 ne contient aucune exigence en matière de test.

11.4.1.2 Nom, rôle et valeur
Clause de la norme EN 301 549Détermination de la conformité

11.4.1.2.1 Nom, rôle et valeur (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance, elle remplit le critère de succès indiqué dans le tableau 11.13.

Tableau 11.13: Critère de succès du logiciel: Nom, rôle, valeur

Pour tout composant d’interface utilisateur (comprenant, mais n’étant pas limité aux éléments de formulaire, liens et composants générés par des scriptes), le nom et le rôle peuvent être déterminés par un programme informatique ; les états, les propriétés et les valeurs qui peuvent être paramétrés par l’utilisateur peuvent être définis par un programme informatique ; et la notification des changements de ces éléments est disponible aux agents utilisateurs, incluant les technologies d’assistance.

REMARQUE 1: Ce critère de succès s’adresse principalement aux développeurs de logiciels qui développent ou utilisent des composants d’interface utilisateur personnalisés. Les composants d’interface utilisateur standard de la plupart des plateformes qui prennent en charge l’accessibilité répondent déjà à ce critère de succès lorsqu’ils sont utilisés conformément aux spécifications.

REMARQUE 2: Pour se conformer à ce critère de succès, il est généralement préférable que les interfaces utilisateur des logiciels utilisent les services d’accessibilité fournis par les logiciels de plateforme. Ces services d’accessibilité permettent l’interopérabilité entre les interfaces utilisateur des logiciels et les technologies d’assistance et les caractéristiques d’accessibilité des logiciels de manière normalisée. La plupart des services d’accessibilité de plateforme vont au-delà de l’exposition programmatique du nom et du rôle, et de l’établissement programmatique des états, des propriétés et des valeurs (et de leur notification), et spécifient des informations supplémentaires qui pourraient ou doivent être exposées et/ou établies (p. ex. une liste des actions disponibles pour un composant d’interface utilisateur donné, et un moyen pour exécuter par un programme informatique une des actions indiquées).

REMARQUE 3: Ce critère de succès est identique au critère de succès 4.1.2 Nom, rôle et valeur des WCAG 2.1 remplaçant la note initiale des WCAG 2.1 par la suivante: « Ce critère de succès s’adresse principalement aux développeurs de logiciels qui développent ou utilisent des composants d’interface utilisateur personnalisés. Les composants d’interface utilisateur standard de la plupart des plateformes qui prennent en charge l’accessibilité répondent déjà à ce critère de succès lorsqu’ils sont utilisés conformément aux spécifications » et l’ajout de la note 2 ci-dessus.

C.11.4.1.2.1 Nom, rôle et valeur (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge au moins une technologie d’assistance.

Procédure

1. Vérifiez que le logiciel n’échoue pas le critère de succès indiqué dans le tableau 11.13.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.4.1.2.2 Nom, rôle et valeur (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui ne prend pas en charge l’accès aux technologies d’assistance, elle ne remplit pas le critère de succès « Nom, rôle, valeur » du tableau 11.11, parce que ce critère de succès exige des informations sous une forme pouvant être déterminée par le programme.

C.11.4.1.2.2 Nom, rôle et valeur (fonction restreinte)

La clause 11.4.1.2.2 ne contient aucune exigence en matière de test.

La clause 11.4.1.3.2 ne contient pas d’exigences testables.

11.4.1.3 Messages d’état
Clause de la norme EN 301 549Détermination de la conformité

11.4.1.3.1 Messages d’état (fonction non restreinte)

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 4.1.3 Messages d’état des WCAG 2.1.

C.11.4.1.3.1 Messages d’état (fonction non restreinte)

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est un logiciel non Web qui est doté d’une interface utilisateur.

2. Le logiciel prend en charge l’accès aux technologies d’assistance pour la lecture d’écran.

Procédure

1. Vérifier que le logiciel n’échoue pas le critère de succès 4.1.3 Messages d’état des WCAG 2.1.

Résultat

Réussite : L’énoncé testable no 1 est vrai.

Échec : L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie ou le logiciel non Web ne renferme pas de contenu pertinent pour le critère de succès 4.1.3 Messages d’état des WCAG 2.1.

11.4.1.3.2 Messages d’état (fonction restreinte)

Sans objet.

C.11.4.1.3.2 Messages d’état (fonction restreinte)
11.5 Interopérabilité avec la technologie d’assistance
Clause de la norme EN 301 549Détermination de la conformité

11.5.1 Fonction restreinte

Lorsque la fonction restreinte du logiciel est conforme à La clause 5.1 (Fonction restreinte), il n’est pas nécessaire de se conformer aux clauses 11.5.2 à 11.5.2.17.

C.11.5.1 Fonction restreinte

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel a une fonction restreinte.

Procédure

1. Vérifiez que la fonction restreinte est conforme à La clause 5.1.

Résultat

Si l’énoncé testable no 1 est vrai, le logiciel n’est pas tenu de se conformer aux clauses 11.5.2 à 11.5.17.

Si l’énoncé testable no 1 est faux, le logiciel est tenu de se conformer aux clauses 11.5.2 à 11.5.17.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2 Services d’accessibilité
Clause de la norme EN 301 549Détermination de la conformité

11.5.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur.

Les logiciels de plateforme fournissent un ensemble de services de plateforme documentés qui permettent aux logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme d’interagir avec la technologie d’assistance.

Le logiciel de la plateforme doit prendre en charge les exigences 11.5.2.5 à 11.5.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.5.2.14 (Modification des attributs de du focus et de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1: Elles définissent la fonctionnalité minimale des logiciels fournissant des interfaces utilisateur lors de l’utilisation des services de la plateforme.

REMARQUE 2: Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 3: Les services d’interface utilisateur qui fournissent par défaut un soutien à l’accessibilité sont considérés comme faisant partie des services fournis pour se conformer à cette clause (par exemple, le service de création d’un nouvel élément d’interface utilisateur fournit un rôle, un état, une limite, un nom et une description).

REMARQUE 4: Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

REMARQUE 5: Dans des environnements de un programme informatique particuliers, les attributs techniques associés aux propriétés de l’interface utilisateur décrites dans les clauses 11.5.2.5 à 11.5.2.17 peuvent avoir des noms différents de ceux utilisés dans ces clauses.

C.11.5.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur.

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel de plateforme.

Procédure

1. Vérifiez que la documentation du logiciel de plateforme comprend des informations sur les services de la plateforme qui peuvent être utilisés par un logiciel qui fournit une interface utilisateur pour interagir avec la technologie d’assistance.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Le logiciel de la plateforme doit fournir un ensemble de services d’accessibilité documentés qui permettent à la technologie d’assistance d’interagir avec les logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme.

Le logiciel de plateforme doit prendre en charge les exigences 11.5.2.5 à 11.5.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.5.2.14 (Modification des attributs de du focus et de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1: Celles-ci définissent les fonctions minimales disponibles pour les technologies d’assistance lors de l’utilisation des services de plateforme.

REMARQUE 2: La définition de plateforme dans la clause 3.1 s’applique aux logiciels qui fournissent des services à d’autres logiciels, y compris, mais sans s’y limiter, les systèmes d’exploitation, les navigateurs Web et les machines virtuelles.

REMARQUE 3: Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 4: Généralement, ces services appartiennent au même ensemble de services qui sont décrits dans La clause 11.5.2.1.

REMARQUE 5: Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

C.11.5.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel de plateforme.

Procédure

1. Vérifiez que la documentation du logiciel de plateforme comprend des informations sur les services d’accessibilité de la plateforme qui permettent à la technologie d’assistance d’interagir avec le logiciel qui fournit une interface utilisateur fonctionnant sur le logiciel de plateforme.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.3 Utilisation des services d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, il utilise les services d’accessibilité de plateforme documentés applicables. Si les services d’accessibilité de la plateforme documentés ne permettent pas au logiciel de satisfaire aux exigences applicables des clauses 11.5.2.5 à 11.5.2.17, le logiciel qui fournit une interface utilisateur doit utiliser d’autres services documentés pour interagir avec la technologie d’assistance.

REMARQUE: L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.5.2.1 et 11.5.2.2.

Il est préférable de développer des logiciels à l’aide de boîtes à outils qui mettent en œuvre automatiquement les services d’accessibilité de la plateforme sous-jacente.

C.11.5.2.3 Utilisation des services d’accessibilité

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

Procédure

1. Vérifiez que le logiciel utilise les services d’accessibilité de plateforme documentés applicables.

2. Vérifiez que le logiciel peut répondre aux exigences applicables de 11.5.2.5 à 11.5.2.17 tout en utilisant les services d’accessibilité documentés de la plateforme.

3. Vérifiez que le logiciel peut répondre aux exigences de 11.5.2.5 à 11.5.2.17 tout en utilisant les services d’accessibilité documentés de la plateforme et autres services documentés.

Résultat

Réussite: L’énoncé testable no 1 est vrai et l’énoncé testable no 2 ou 3 est vrai.

Échec: Les énoncés testables no 1 ou 3 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.4 Technologie d’assistance

Lorsque la TIC est une technologie d’assistance, elle doit utiliser les services d’accessibilité de la plateforme documentés.

REMARQUE: L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.5.2.1 et 11.5.2.2.

REMARQUE 2: Les technologies d’assistance peuvent également utiliser d’autres services d’accessibilité documentés.

C.11.5.2.4 Technologie d’assistance

Type d’évaluation

Inspection

Conditions préalables

1. La TIC est une technologie d’assistance.

Procédure

1. Vérifiez que la technologie d’assistance utilise les services d’accessibilité documentés de la plateforme.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.5 Renseignements sur les objets

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre au rôle, aux états, à la limite, au nom et à la description des éléments d’interface utilisateur d’être déterminés par un programme informatique au moyen de technologies d’assistance.

C.11.5.2.5 Renseignements sur les objets

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

Procédure

1. Vérifiez que le rôle de l’élément d’interface utilisateur peut être déterminé par un programme informatique à l’aide de technologies d’assistance.

2. Vérifiez que l’état ou les états l’élément d’interface utilisateur peuvent être déterminés par un programme informatique à l’aide de technologies d’assistance.

3. Vérifiez que la limite de l’élément d’interface utilisateur peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

4. Vérifiez que le nom de l’élément d’interface utilisateur peut être déterminé par un programme informatique à l’aide de technologies d’assistance.

5. Vérifiez que la description de l’élément d’interface utilisateur peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 1, 2, 3, 4 et 5 sont vrais.

Échec: Les énoncés testables nos 1, 2, 3, 4 ou 5 sont faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.6 Ligne, colonne et en-têtes

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la ligne et la colonne de chaque cellule d’un tableau de données, y compris les en-têtes de la ligne et de la colonne, le cas échéant, déterminables par un programme informatique au moyen de technologies d’assistance.

C.11.5.2.6 Ligne, colonne et en-têtes

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il y a des tableaux de données dans l’interface utilisateur.

Procédure

1. Sélectionnez une table de données dans laquelle les tests doivent être effectués.

2. Vérifiez que la rangée de chaque cellule peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

3. Vérifiez que la colonne de chaque cellule peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

4. Vérifiez que l’en-tête de ligne de chaque cellule, si elle existe, peut être déterminé par un programme informatique à l’aide de technologies d’assistance.

5. Vérifiez que l’en-tête de la colonne de chaque cellule, si elle existe, peut être déterminé par un programme informatique à l’aide de technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 2, 3, 4 et 5 sont vrais.

Échec: Les énoncés testables nos 2, 3, 4 ou 5 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.7 Valeurs

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la valeur actuelle d’un élément d’interface utilisateur et toute valeur minimale ou maximale de la plage, si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, pouvant être déterminées par un programme informatique par des technologies d’assistance.

C.11.5.2.7 Valeurs

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Certains éléments d’interface utilisateur peuvent avoir des valeurs.

Procédure

1. Sélectionnez un élément d’interface utilisateur qui peut avoir une valeur.

2. Vérifiez que la valeur actuelle peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

3. Si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, vérifiez que la valeur minimale peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

4. Si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, vérifiez que la valeur maximale peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 2, 3 et 4 sont vrais.

Échec: Les énoncés testables nos 2, 3, ou 4 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.8 Liens entre les étiquettes

Lorsque le logiciel fournit une interface utilisateur, il expose le lien qu’entretient un élément d’interface utilisateur en tant qu’étiquette pour un autre élément ou en tant qu’élément étiqueté par un autre élément, en utilisant les services décrits dans la clause 11.5.2.3, de sorte que ces informations puissent être déterminées par un programme informatique par des technologies d’assistance.

C.11.5.2.8 Liens entre les étiquettes

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il existe des éléments d’interface utilisateur qui sont des étiquettes d’autres éléments d’interface utilisateur.

Procédure

1. Obtenir les informations de chaque élément d’interface utilisateur.

2. Vérifiez que les informations de l’élément d’interface utilisateur incluent la relation avec l’élément d’interface utilisateur qui est son étiquette, si l’élément d’interface utilisateur actuel a une étiquette, et que cette relation peut être déterminée par un programme informatique par des technologies d’assistance.

3. Vérifiez que les informations de l’élément d’interface utilisateur incluent la relation avec l’élément d’interface utilisateur qu’il étiquette, si l’élément d’interface utilisateur actuel est une étiquette, et que cette relation peut être déterminée par un programme informatique par des technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 2 ou 3 sont vrais

Échec: Les énoncés testables nos 2 et 3 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.9 Relations parents-enfants

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, la relation entre un élément d’interface utilisateur et tout élément parent ou enfant.

C.11.5.2.9 Relations parents-enfants

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il existe des éléments d’interface utilisateur qui sont les parents d’autres éléments d’interface utilisateur dans une structure hiérarchique.

Procédure

1. Pour les éléments d’interface utilisateur qui ont un parent, vérifiez que les informations de l’élément d’interface utilisateur incluent la relation avec l’élément d’interface utilisateur qui est son parent.

2. Vérifiez que les informations des éléments d’interface utilisateur qui sont les parents de l’élément d’interface utilisateur sélectionné dans l’énoncé testable no 1 incluent la relation avec les éléments d’interface utilisateur qui sont ses enfants, et que cette relation peut être déterminée par un programme informatique par des technologies d’assistance.

3. Pour les éléments d’interface utilisateur qui sont le parent d’autres éléments d’interface utilisateur, vérifiez que les informations de l’élément d’interface utilisateur incluent la relation avec les éléments d’interface utilisateur qui sont ses enfants, et que cette relation peut être déterminée par un programme informatique par des technologies d’assistance.

4. Vérifiez que les informations des éléments d’interface utilisateur qui sont les enfants de l’élément d’interface utilisateur sélectionné dans l’énoncé testable no 3 incluent la relation avec les éléments d’interface utilisateur qui sont ses parents, et que cette relation peut être déterminée par un programme informatique par des technologies d’assistance.

Résultat

Réussite: L’énoncé testable no 1 ou 2 est vrai et l’énoncé testable no 3 ou 4 est vrai.

Échec: Les énoncés testables nos 1 et 2 sont faux ou les énoncés testables nos 3 et 4 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

REMARQUE: Pour cette exigence, il suffit que l’une des deux directions d’une relation parent-enfant puisse être déterminée par le programme. C’est la raison pour laquelle les vérifications de l’exigence sont effectuées par paires et l’exigence est satisfaite si un membre de chaque paire est vrai.

11.5.2.10 Texte

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, le contenu textuel, les attributs textuels et la limite du texte rendu à l’écran.

C.11.5.2.10 Texte

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il y a du texte rendu à l’écran.

Procédure

1. Pour les exemples de texte rendu à l’écran, vérifiez que l’information du texte inclut son contenu textuel et que cette information peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

2. Pour les exemples de texte rendu à l’écran, vérifiez que l’information du texte inclut ses attributs et que cette information peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

3. Pour les exemples de texte rendu à l’écran, vérifiez que l’information du texte inclut sa limite et que cette information peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 1, 2 et 3 sont vrais

Échec: Les énoncés testables no 1, 2 ou 3 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.11 Liste des actions disponibles

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, une liste des actions disponibles qui peuvent être exécutées sur un élément d’interface utilisateur.

C.11.5.2.11 Liste des actions disponibles

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Certains éléments d’interface utilisateur ont des actions qui peuvent être exécutées par l’utilisateur.

Procédure

1. Vérifiez que les informations de l’élément d’interface utilisateur contiennent la liste des actions qui peuvent être exécutées.

2. Vérifiez que cette liste peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.12 Exécution des actions disponibles

Lorsque les exigences de sécurité le permettent, le logiciel qui fournit une interface utilisateur doit, en utilisant les services décrits à la clause 11.5.2.3, permettre l’exécution programmatique des actions exposées, au moyen des technologies d’assistance, conformément à la clause 11.5.2.11.

REMARQUE 1: Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2: Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

C.11.5.2.12 Exécution des actions disponibles

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Certains éléments d’interface utilisateur offrent des actions qui peuvent être exécutées par l’utilisateur.

3. Les exigences en matière de sécurité permettent à la technologie d’assistance d’exécuter par un programme informatique les actions de l’utilisateur.

Procédure

1. Vérifiez que les informations de l’élément d’interface utilisateur incluent la liste des actions qui peuvent être exécutées par les technologies d’assistance selon la clause 11.5.2.11.

2. Vérifiez que toutes les actions de la liste peuvent être exécutées avec succès par des technologies d’assistance.

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.5.2.13 Suivi des attributs de du focus et de sélection

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre l’information et les mécanismes nécessaires au suivi de la cible de saisie, du point d’insertion du texte et des attributs de sélection des éléments d’interface utilisateur, déterminables par un programme informatiques par les technologies d’assistance.

C.11.5.2.13 Suivi des attributs de du focus et de sélection

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Certains éléments d’interface utilisateur permettent la modification de textes.

Procédure

1. Vérifiez que les informations de l’élément d’interface utilisateur comprennent des mécanismes de suivi de la du focus, du point d’insertion du texte et des attributs de sélection.

2. Vérifiez que cette information peut être déterminée par un programme informatique à l’aide de technologies d’assistance.

3. Activez ces mécanismes de suivi.

4. En tant qu’utilisateur, utilisez la fonctionnalité d’édition de texte dans le produit logiciel évalué.

5. Vérifiez que le suivi de la du focus, du point d’insertion de texte et des attributs de sélection fonctionne.

Résultat

Réussite: Les énoncés testables nos 2 et 5 sont vrais.

Échec: Les énoncés testables no 1 ou 5 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.5.2.14 Modification des attributs de du focus et de sélection

Lorsque les exigences de sécurité le permettent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique le foyer, le point d’insertion de texte et les attributs de sélection des éléments d’interface utilisateur où l’utilisateur peut modifier ces éléments.

REMARQUE 1: Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2: Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

C.11.5.2.14 Modification des attributs de du focus et de sélection

Type d’évaluation

Examen

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Certains éléments d’interface utilisateur peuvent recevoir une du focus ou permettre l’édition de texte.

3. Les exigences de sécurité permettent au logiciel de plateforme de modifier par un programme informatique la du focus, le point d’insertion du texte et les attributs de sélection des éléments d’interface utilisateur.

Procédure

1. Pour les éléments d’interface utilisateur qui peuvent recevoir la du focus et où la cible de saisie peut être modifiée par un utilisateur sans l’utilisation d’une technologie d’assistance, vérifier que la du focus peut être modifiée par un programme informatique par des technologies d’assistance.

2. Pour les éléments d’interface utilisateur qui permettent à un utilisateur de modifier du texte sans l’aide d’une technologie d’assistance, vérifier que la position du point d’insertion du texte peut être modifiée par un programme informatique à l’aide de technologies d’assistance.

3. Pour les éléments d’interface utilisateur qui permettent l’édition de texte, vérifiez que les attributs de sélection peuvent être modifiés par un programme informatique par des technologies d’assistance, dans les cas où ils peuvent être modifiés par l’utilisateur sans l’aide de technologies d’assistance.

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: N’importe quel énoncé testable est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.5.2.15 Avis de modification

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, aviser les technologies d’assistance des changements apportés aux attributs des éléments d’interface utilisateur pouvant être déterminés par un programme informatique qui sont mentionnés dans les exigences 11.5.2.5 à 11.5.2.11 et 11.5.2.13.

C.11.5.2.15 Avis de modification

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

Procédure

1. Activer les avis de modification dans les éléments d’interface utilisateur.

2. Vérifier que les avis de modification des renseignements sur les objets (rôle, état, limite, nom et description) sont envoyés aux technologies d’assistance, si ces renseignements changent dans l’interface utilisateur du logiciel.

3. Vérifier que les avis de modification des lignes, colonnes et en-têtes des tableaux de données sont envoyés aux technologies d’assistance, si ces renseignements changent dans le logiciel.

4. Vérifier que des avis de modification de valeurs (valeur actuelle, valeur minimale et valeur maximale) sont envoyés, si ces renseignements changent dans le logiciel.

5. Vérifier que des avis de modification des liens entre les étiquettes sont envoyés aux technologies d’assistance, si ces renseignements changent dans le logiciel.

6. Vérifier que des avis de modification des relations parent-enfant sont envoyés aux technologies d’assistance, si ces informations changent dans le logiciel.

7. Vérifier que des avis de modification du texte (contenu ou attributs du texte et limite du texte rendu à l’écran) sont envoyés aux technologies d’assistance, si ces renseignements changent dans le logiciel.

8. Vérifier que des avis de modifications apportées à liste des actions disponibles sont envoyés aux technologies d’assistance, si ces renseignements changent dans le logiciel.

9. Vérifier que des avis de modification de la du focus, du point d’insertion du texte et des attributs de sélection sont envoyés aux technologies d’assistance, si ces renseignements changent dans le logiciel.

Résultat

Réussite: les énoncés testables no 2, 3, 4, 5, 6, 7, 8 et 9 sont vrais

Échec: les énoncés testables no 2, 3, 4, 5, 6, 7, 8 ou 9 sont faux

Non applicable : La condition préalable 1 n’est pas remplie.

11.5.2.16 Modifications d’états ou de propriétés

Lorsque les exigences de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique les états et propriétés des éléments d’interface utilisateur grâce auxquels l’utilisateur peut modifier ces articles.

REMARQUE 1: Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2: Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

C.11.5.2.16 Modifications d’états ou de propriétés

Type d’évaluation

Examen

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il existe des éléments d’interface utilisateur dont l’état ou les propriétés peuvent être modifiés par un utilisateur sans l’aide d’une technologie d’assistance.

3. Les exigences de sécurité permettent à la technologie d’assistance de modifier par un programme informatique les états et les propriétés des éléments d’interface utilisateur.

Procédure

1. Vérifier que l’état des éléments d’interface utilisateur, dont l’état peut être changé par un utilisateur sans l’aide d’une technologie d’assistance, est susceptible d’être modifié par un programme informatique par des technologies d’assistance.

2. Vérifier que les propriétés des éléments d’interface utilisateur, dont les propriétés peuvent être modifiées par un utilisateur sans l’utilisation de technologies d’assistance, sont susceptibles d’être changées par un programme informatique par des technologies d’assistance.

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: N’importe quel énoncé testable est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.5.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à La clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recours aux technologies d’assistance.

REMARQUE 1: Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2: Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

C.11.5.2.17 Modifications des valeurs et du texte

Type d’évaluation

Examen

Conditions préalables

1. Le logiciel évalué est un logiciel qui fournit une interface utilisateur.

2. Il existe des éléments d’interface utilisateur dont les valeurs ou le texte peuvent être modifiés par un utilisateur sans l’aide d’une technologie d’assistance.

3. Les exigences de sécurité permettent à la technologie d’assistance de modifier par un programme informatique les valeurs et le texte des éléments d’interface utilisateur.

Procédure

1. Vérifier que les valeurs des éléments d’interface utilisateur, dont les valeurs peuvent être modifiées par un utilisateur sans l’aide d’une technologie d’assistance, peuvent être changées par des technologies d’assistance utilisant les méthodes de saisie de la plateforme.

2. Vérifier que le texte des éléments d’interface utilisateur, dont le texte peut être modifié par un utilisateur sans l’aide d’une technologie d’assistance, peut être changé par des technologies d’assistance utilisant les méthodes de saisie de la plateforme.

Résultat

Réussite: Tous les énoncés testables sont vrais.

Échec: N’importe quel énoncé testable est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.6 Utilisation documentée de l’accessibilité
Clause de la norme EN 301 549Détermination de la conformité

11.6.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Lorsque le logiciel est une plateforme, il doit offrir des modes de fonctionnement suffisants permettant à l’utilisateur de contrôler les caractéristiques d’accessibilité de la plateforme documentées comme étant destinées aux utilisateurs.

C.11.6.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Type d’évaluation

Examen

Conditions préalables

1. Certaines fonctions de la plateforme sont définies dans la documentation de celle-ci comme étant des caractéristiques d’accessibilité destinées aux utilisateurs.

Procédure

1. Vérifier qu’il existe suffisamment de modes de fonctionnement pour permettre à l’utilisateur de contrôler les fonctions de la plateforme, qui sont définies dans la documentation de celle-ci comme étant des caractéristiques d’accessibilité destinées aux utilisateurs.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.6.2 Aucune perturbation des caractéristiques d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, elle ne doit pas perturber les caractéristiques d’accessibilité documentées qui sont définies dans la documentation de la plateforme, sauf si l’utilisateur en fait la demande pendant le fonctionnement du logiciel.

C.11.6.2 Aucune perturbation des caractéristiques d’accessibilité

Type d’évaluation

Examen

Conditions préalables

1. Certaines fonctions de la plateforme sont définies dans la documentation de celle-ci comme étant des caractéristiques d’accessibilité.

Procédure

1. Vérifier si un logiciel qui fournit une interface utilisateur perturbe le fonctionnement normal des caractéristiques d’accessibilité de la plateforme.

2. Vérifier si la perturbation a été spécifiquement demandée ou confirmée par l’utilisateur.

Résultat

Réussite: L’énoncé testable no 1 est faux ou les deux énoncés sont vrais.

Échec: L’énoncé testable no 1 est vrai et l’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.7 Préférences de l’utilisateur

Lorsque le logiciel n’est pas conçu pour être isolé de sa plateforme et qu’il fournit une interface utilisateur, cette interface utilisateur doit respecter les valeurs des préférences de l’utilisateur pour les réglages de la plateforme en ce qui concerne les unités de mesure, la couleur, le contraste, le type et la taille de police et le curseur du focus, sauf s’ils sont surclassés par l’utilisateur.

REMARQUE 1: Les logiciels isolés de leur plateforme sous-jacente n’ont pas accès aux paramètres de l’utilisateur de la plateforme et ne peuvent donc pas respecter cette clause.

REMARQUE 2 : Pour le contenu Web, la plateforme sous-jacente est l’agent utilisateur.

REMARQUE 3 : Cela n’empêche pas le logiciel d’avoir des valeurs supplémentaires pour un paramètre, tant qu’il existe un mode dans lequel l’application suivra les paramètres du système, même s’ils sont plus restreints.

C.11.7 Préférences de l’utilisateur

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel est un logiciel qui fournit une interface utilisateur.

Procédure

1. Vérifier si le logiciel offre suffisamment de modes de fonctionnement se servant des préférences de l’utilisateur pour les paramètres de la plateforme en ce qui concerne la couleur, le contraste, le type et la taille de police ainsi que le curseur de du focus.

2. Vérifier que la documentation du logiciel indique que le logiciel est conçu pour être isolé de sa plateforme sous-jacente.

Résultat

Réussite: L’énoncé testable no 1 est vrai ou l’énoncé testable no 1 est faux et l’énoncé testable no 2 est vrai.

Échec: L’énoncé testable no 1 est faux et l’énoncé testable no 2 est faux.

Non applicable : La condition préalable 1, 2 ou 3 n’est pas remplie.

11.8 Outils-auteurs
Clause de la norme EN 301 549Détermination de la conformité

11.8.1 Technologie du contenu

Les outils-auteurs doivent être conformes aux clauses 11.8.2 à 11.8.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

C.11.8.1 Technologie du contenu

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel est un outil-auteur.

2. Le format de l’extrant de l’outil-auteur prend en charge les renseignements nécessaires à l’accessibilité.

Procédure

1. Vérifier si l’outil-auteur est conforme aux clauses 11.8.2 à 11.8.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

REMARQUE: Lorsque le format des extrants de l’outil-auteur ne prend pas en charge certains types de renseignements requis pour l’accessibilité, il n’est pas nécessaire de respecter les exigences relatives à ce type de renseignements.

11.8.2 Création de contenu accessible

Les outils-auteurs doivent permettre et orienter la production de contenu conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

REMARQUE: Les outils-auteurs peuvent s’appuyer sur des outils supplémentaires lorsqu’il n’est pas possible de respecter des exigences spécifiques avec un seul outil. Par exemple, un outil de montage vidéo peut permettre la création de fichiers vidéo aux fins de diffusion via la télévision et le Web, mais la création de fichiers de sous-titres pour des formats multiples peut être assurée par un outil différent.

C.11.8.2 Création de contenu accessible

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel est un outil-auteur.

Procédure

1. Vérifier si l’outil-auteur possède des caractéristiques qui permettent et orientent la production conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web).

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

11.8.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Lorsque l’outil-auteur fournit des transformations de restructuration ou de recodage, les renseignements sur l’accessibilité doivent alors être préservés dans l’extrant s’il existe des mécanismes équivalents dans la technologie du contenu de l’extrant.

REMARQUE 1: Les transformations de restructuration sont des transformations dans le cadre desquelles la technologie du contenu reste identique, mais les caractéristiques structurelles du contenu sont modifiées (par exemple, linéarisation des tableaux, division d’un document en pages).

REMARQUE 2: Les transformations de recodage sont des transformations dans le cadre desquelles la technologie utilisée pour coder le contenu est modifiée.

C.11.8.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Type d’évaluation

Inspection et essais

Conditions préalables

1. Le logiciel est un outil-auteur.

2. L’outil-auteur fournit des transformations de restructuration ou de recodage.

Procédure

1. Pour une transformation de restructuration, vérifier si les renseignements d’accessibilité sont préservés dans l’extrant.

2. Pour une transformation de restructuration, vérifier si la technologie du contenu prend en charge les renseignements d’accessibilité dans la forme restructurée de l’information.

3. Pour une transformation de recodage, vérifier si les renseignements d’accessibilité sont préservés dans l’extrant.

4. Pour une transformation de recodage, vérifier si les renseignements d’accessibilité sont pris en charge par la technologie de l’extrant recodé.

Résultat

Réussite: L’énoncé testable no 1 est vrai ou les énoncés testables no 1 et 2 sont faux ou l’énoncé testable no 3 est vrai ou les énoncés testables no 3 et 4 sont faux.

Échec: L’énoncé testable no 1 est faux et l’énoncé testable no 2 est vrai.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.8.4 Aide à la réparation

Si la fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, alors l’outil-auteur doit formuler des suggestions en matière de réparation.

REMARQUE: Cela n’exclut pas les réparations automatisées ou semi-automatisées qui sont possibles (et recommandées) pour de nombreux types de problèmes d’accessibilité du contenu.

C.11.8.4 Aide à la réparation

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel est un outil-auteur.

2. La fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

Procédure

1. L’outil-auteur formule des suggestions en matière de réparation lorsque le contenu fournit des suggestions de réparation lorsque le contenu n’est pas conforme à l’une des exigences des clauses 9 ou 10 (selon le cas).

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

11.8.5 Modèles

Lorsque l’outil-auteur fournit des modèles, au moins l’un des modèles qui prend en charge la création de contenu conforme aux exigences des clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, doit être disponible et identifié en tant que tel.

C.11.8.5 Modèles

Type d’évaluation

Inspection

Conditions préalables

1. Le logiciel est un outil-auteur.

2. L’outil-auteur fournit des modèles

Procédure

1. Vérifier que l’outil-auteur fournit au moins un modèle qui prend en charge la création de contenu conforme aux exigences 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

2. Vérifier qu’au moins un modèle indiqué à l’étape 1 est disponible et qu’il est identifié comme étant conforme aux clauses 9 ou 10 (selon le cas).

Résultat

Réussite: Les énoncés testables nos 1 et 2 sont vrais.

Échec: Les énoncés testables nos 1 ou 2 sont faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

REMARQUE: L’indication que le modèle est conforme aux exigences des clauses 9 ou 10 (selon le cas) mentionnée dans l’énoncé testable 2 peut être, par exemple, formulée dans les termes suivants: « Conforme à la directive WCAG 2.1 ». Lorsque l’indication n’indique pas explicitement que toutes les exigences énoncées aux clauses 9 ou 10 (selon le cas) sont respectées, il peut être nécessaire d’utiliser le modèle pour créer un site Web ou un document, puis de mettre à l’essai ce site Web ou ce document conformément aux exigences des clauses 9 ou 10 afin d’avoir la certitude que le modèle se comporte tel que requis.

12 Documentation et soutien technique

12.1 Documentation du produit
Clause de la norme EN 301 549Détermination de la conformité

12.1.1 Caractéristiques d’accessibilité et de compatibilité

La documentation du produit fournie avec les TIC, qu’elle soit fournie séparément ou intégrée aux TIC doit énumérer et expliquer les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

REMARQUE 1: Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

REMARQUE 2 : La pratique exemplaire consiste à utiliser WebSchemas/Accessibility 2.0 [i.38] pour fournir des métadonnées sur l’accessibilité des TIC.

REMARQUE 3 : L’énoncé sur l'accessibilité et les pages d’aide sont deux exemples de diffusion de renseignements sur les produits.

C.12.1.1 Caractéristiques d’accessibilité et de compatibilité

Type d’évaluation

Inspection

Conditions préalables

1. La documentation du produit est fournie avec les TIC.

Procédure

1. Vérifier que la documentation du produit fournie avec les TIC énumère et explique les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants:

1. un format Web conforme aux exigences de la clause 9;

2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1: Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2: Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3: Lorsque la documentation fait partie intégrante des TIC, elle est fournie par l’intermédiaire de l’interface utilisateur qui est accessible.

REMARQUE 4: Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

C.12.1.2 Documentation accessible

Type d’évaluation

Inspection

Conditions préalables

1. La documentation du produit en format électronique est fournie avec les TIC.

Procédure

1. Vérifier que la documentation du produit en format électronique fournie avec les TIC est conforme aux exigences des clauses 9 ou 10, selon le cas.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

12.2 Services de soutien
Clause de la norme EN 301 549Détermination de la conformité

12.2.1 Généralités (information)

Les services d’appui en matière de TIC comprennent, sans s’y limiter, les centres d’assistance, les centres d’appel, le soutien technique, les services de relais et les services de formation.

C.12.2.1 Généralités (information)

La clause 12.2.1 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent fournir des renseignements sur les caractéristiques d’accessibilité et de compatibilité inclus dans la documentation du produit.

REMARQUE: Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

C.12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Type d’évaluation

Inspection

Conditions préalables

1. Des services de soutien en matière de TIC sont fournis.

Procédure

1. Vérifier que les services de soutien en matière de TIC fournissent des renseignements sur les caractéristiques d’accessibilité et de compatibilité figurant dans la documentation du produit.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

12.2.3 Communication efficace

Les services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

C.12.2.3 Communication efficace

Type d’évaluation

Inspection

Conditions préalables

1. Des services de soutien en matière de TIC sont fournis.

Procédure

1. Vérifier que les services de soutien en matière TIC répondent aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

REMARQUE: La prestation de tout niveau de soutien visant à répondre aux besoins en communication des personnes handicapées constitue une réussite pour cette exigence. Les fournisseurs voudront peut-être fournir davantage de renseignements sur le niveau de soutien fourni pour permettre de juger de la pertinence et de la qualité du soutien.

12.2.4 Documentation accessible

La documentation fournie par les services de soutien doit être disponible dans au moins un des formats électroniques suivants:

1. un format Web conforme aux exigences de la clause 9;

2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1: Cela n’exclut pas la possibilité de fournir également la documentation dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2: Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3: Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

C.12.2.4 Documentation accessible

Type d’évaluation

Inspection

Conditions préalables

1. La documentation est fournie par les services de soutien en matière de TIC.

Procédure

1. Vérifier que la documentation en format électronique fournie par les services de soutien en matière de TIC est conforme aux exigences des clauses 9 ou 10, selon le cas.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13 TIC assurant l’accès aux services de relais ou d’urgence

13.1 Exigences en matière de services de relais
Clause de la norme EN 301 549Détermination de la conformité

13.1.1 Généralités (information)

Les services de relais permettent aux utilisateurs de différents modes de communication (texte, signes, parole, etc.) d’interagir à distance, grâce aux TIC et à la communication bidirectionnelle, en assurant une conversion entre les modes de communication, normalement effectuée par un opérateur humain.

Une pratique exemplaire consiste à respecter les exigences de la norme en vigueur ETSI ES 202 975 [i.5] en matière de services de relais.

C.13.1.1 Généralités (information)

La clause 13.1.1 n’a qu’une valeur informative et ne contient aucune exigence en matière de tests.

13.1.2 Services de relais de textes

Lorsque les TIC visent à fournir un service de relais de textes, celui-ci doit permettre aux utilisateurs de textes et aux utilisateurs de la parole d’interagir en assurant la conversion entre les deux modes de communication.

C.13.1.2 Services de relais de textes

Type d’évaluation

Inspection

Conditions préalables

1. Le service est un service de relais de textes.

Procédure

1. Vérifier que le service permet aux utilisateurs de textes et aux utilisateurs de la parole d’interagir en assurant la conversion entre les deux modes de communication.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13.1.3 Services de relais de signes

Lorsque les TIC visent à fournir un service de relais de signes, celui-ci doit permettre aux utilisateurs des langues des signes et aux utilisateurs de la parole d’interagir en assurant la conversion entre les deux modes de communication.

REMARQUE: Les services de relais de signes sont aussi parfois appelés services de relais des langues des signes ou services de relais vidéo.

C.13.1.3 Services de relais de signes

Type d’évaluation

Inspection

Conditions préalables

1. Le service est un service de relais de signes.

Procédure

1. Vérifier que le service permet aux utilisateurs des langues des signes et aux utilisateurs de la parole d’interagir en assurant la conversion entre les deux modes de communication.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13.1.4 Services de relais de lecture labiale

Lorsque les TIC visent à fournir un service de relais de lecture labiale, le service de lecture labiale doit permettre aux personnes qui lisent sur les lèvres et aux utilisateurs de téléphonie vocale d’interagir en assurant la conversion entre les deux modes de communication.

C.13.1.4 Services de relais de lecture labiale

Type d’évaluation

Inspection

Conditions préalables

1. Il s’agit d’un service de relais de lecture labiale.

Procédure

1. Vérifier que le service permet aux personnes qui lisent sur les lèvres et aux utilisateurs de téléphonie vocale d’interagir en assurant la conversion entre les deux modes de communication.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13.1.5 Services de téléphonie sous-titrée

Lorsque les TIC visent à fournir un service de téléphonie sous-titrée, celui-ci doit aider un utilisateur sourd ou malentendant qui participe à un dialogue oral en lui fournissant des sous-titres traduisant l’appel entrant.

C.13.1.5 Services de téléphonie sous-titrée

Type d’évaluation

Inspection

Conditions préalables

1. Le service est un service de téléphonie sous-titré.

Procédure

1. Vérifier que le service aide un utilisateur sourd ou malentendant qui participe à un dialogue oral en lui fournissant des sous-titres traduisant l’appel entrant.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13.1.6 Services de relais de la parole à la parole

Lorsque les TIC visent à fournir un service de relais de la parole à la parole, celui-ci doit permettre aux utilisateurs de téléphones souffrant de troubles de l’élocution ou de troubles cognitifs et à tout autre utilisateur de communiquer en leur fournissant une assistance mutuelle.

C.13.1.6 Services de relais de la parole à la parole

Type d’évaluation

Inspection

Conditions préalables

1. Le service est un service de relais de la parole à la parole.

Procédure

1. Vérifier que le service permet aux utilisateurs de téléphone souffrant de troubles de l’élocution ou de troubles cognitifs et à tout autre utilisateur de communiquer en leur fournissant une assistance mutuelle.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 n’est pas remplie.

13.2 Accès aux services de relais

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services de relais, l’accès à ces services de relais ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par un service de relais et le système des TIC.

REMARQUE 1: La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services de relais, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

C.13.2 Accès aux services de relais

Type d’évaluation

Inspection

Conditions préalables

1. Le système des TIC prend en charge la communication bidirectionnelle.

2. Un ensemble de services de relais pour la communication bidirectionnelle est spécifié.

Procédure

1. Vérifier que le système n’empêche pas l’accès à ces services de relais pour les appels entrants et sortants.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

13.3 Accès aux services d’urgence

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services d’urgence, l’accès à ces services d’urgence ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par le service d’urgence et le système des TIC.

REMARQUE 1: La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services d’urgence, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

C.13.3 Accès aux services d’urgence

Type d’évaluation

Inspection

Conditions préalables

1. Le système des TIC prend en charge la communication bidirectionnelle.

2. Un ensemble de services d’urgence pour la communication bidirectionnelle est spécifié.

Procédure

1. Vérifier que le système n’empêche pas l’accès à ces services d’urgence pour les appels entrants et sortants.

Résultat

Réussite: L’énoncé testable no 1 est vrai.

Échec: L’énoncé testable no 1 est faux.

Non applicable : La condition préalable 1 ou 2 n’est pas remplie.

Annexe - Tableaux et figures (de la norme EN 301 549)

Les tableaux et figures ci-dessous proviennent des clauses de la norme EN 301 549 (2021) et n’ont pas été modifiés. Pour chaque tableau ou figure, un lien hypertexte a été créé pour référencer la clause associée, ce qui n'existe pas dans le PDF officiel EN 301 549 (2021) car le PDF officiel inclut ces tableaux et figures en ligne avec la clause.

Tableau 5.1: Relation entre la distance de visualisation du dessin maximale et la hauteur minimale des caractères à un angle sous-tendu minimal de 0,7 degré

Distance de visualisation du dessin maximaleHauteur minimale des caractères

100 mm

1,2 mm

200 mm

2,4 mm

250 mm

3,1 mm

300 mm

3,7 mm

350 mm

4,3 mm

400 mm

4,9 mm

450 mm

5,5 mm

500 mm

6,1 mm

550 mm

6,7 mm

600 mm

7,3 mm

Figure 1 : Relation entre la hauteur minimale des caractères et la distance de visualisation du dessin maximale
Diagramme illustrant le contenu linéaire du texte 5.1.4 Fonctionnalité fermée à l'agrandissement du texte

Contenu connexe:

Figure 2 : Portée avant libre
Un diagramme illustrant le contenu du texte 8.3.2.2 Hauteur minimum de la portée avant libre. Personne en fauteuil roulant tendue vers l'avant.

Contenu connexe:

Figure 3 : Portée avant obstruée
Un diagramme illustrant le contenu du texte 8.3.2.3.3. Portée avant (<635 mm) obstruée. Personne en fauteuil roulant qui s'étend au-dessus d'un bureau et qui démontre qu'il n'y a pas d'obstacles et qu'il y a une obstruction à avant portée.

Contenu connexe:

Figure 4 : Espace libre pour les pieds
Un diagramme illustrant le contenu du texte 8.3.2.5 Espace libre pour les pieds.

Contenu connexe:

Figure 5 : Espace libre pour les genoux
Un diagramme illustrant le contenu du texte 8.3.2.6 Espace libre pour les genoux.

Contenu connexe:

Figure 6 : Portée latérale libre
Un diagramme illustrant le contenu du texte 8.3.3.2 Hauteur minimale de la portée latérale libre. Personne en fauteuil roulant qui se penche sur le côté.

Contenu connexe:

Figure 7 : Portée latérale haute obstruée
Un diagramme illustrant le contenu du texte 8.3.3.3.2 Portée latérale haute obstruée (≤ 610 mm). Personne en fauteuil roulant tendre à le côté et qui démontre qu'il n'y a pas d'obstacles et qu'il y a un obstruction à haute latérale portée.

Contenu connexe:

Figure 8 : Changement de niveau vertical
Un diagramme illustrant le contenu du texte 8.3.4.1. Changement de niveau.

Contenu connexe:

Figure 9 : Changement de niveau en biseau
Un diagramme illustrant le contenu du texte 8.3.4.1. Changement de niveau.

Contenu connexe:

Figure 10 : Surface au sol dégagée
Diagramme illustrant le contenu du texte 8.3.4.2 Surface de plancher ou de sol dégagée. Personne en fauteuil roulant démontrant un espace libre minimal.

Contenu connexe:

Figure 11 : Espace libre de manœuvre dans une alcôve, approche avant
Un diagramme illustrant le contenu du texte 8.3.4.3.2 Approche avant. Personne dans un fauteuil roulant dans un alcôve.

Contenu connexe:

Figure 12 : Espace libre de manœuvre dans une alcôve approche parallèle
Un diagramme illustrant le contenu du texte 8.3.4.3.3 Approche parallèle. Personne dans un fauteuil roulant dans un alcôve.

Contenu connexe:

Tableau 9.1 : Critères de succès de niveau AAA des WCAG 2.1
No.RègleNuméro du critère de succèsNom du critère de succès
1Média temporel1.2.6Langue des signes (pré-enregistrée)
2Média temporel1.2.7Audio-description étendue (pré-enregistrée)
3Média temporel1.2.8Version de remplacement pour un média temporel (pré-enregistrée)
4Média temporel1.2.9Seulement audio (en direct)
5Adaptable1.3.6Identifier la fonction
6Distinguable1.4.6Contraste (amélioré)
7Distinguable1.4.7Arrière-plan sonore de faible volume ou absent
8Distinguable1.4.8Présentation visuelle
9Distinguable1.4.9Texte sous forme d’image (sans exception)
10Accessibilité au clavier2.1.3Clavier (pas d’exception)
11Délai suffisant2.2.3Pas de délai d’exécution
12Délai suffisant2.2.4Interruptions
13Délai suffisant2.2.5Nouvelle authentification
14Délai suffisant2.2.6Délais d’expiration
15Crises et réactions physiques2.3.2Trois flashs
16Crises et réactions physiques2.3.3Animation résultant d’interactions
17Navigable2.4.8Localisation
18Navigable2.4.9Fonction du lien (lien uniquement)
19Navigable2.4.10En-têtes de section
20Modalités d’entrée2.5.5Taille de la cible
21Modalités d’entrée2.5.6Modalités d’entrées concurrentes
22Lisible3.1.3Mots rares
23Lisible3.1.4Abréviations
24Lisible3.1.5Niveau de lecture
25Lisible3.1.6Prononciation
26Prévisible3.2.5Changement à la demande
27Assistance à la saisie3.3.5Aide
28Assistance à la saisie3.3.6Prévention des erreurs (toutes)

Annexe – Chapitre 14 - Conformité

La conformité au présent document est obtenue en respectant toutes les exigences applicables, c’est-à-dire les clauses contenant le mot « doit ». Les clauses contenant le mot « devrait » sont des recommandations et ne sont pas requises pour la conformité.

Toutes les clauses, à l’exception de la clause 12, comprennent une autoévaluation de la portée. Cela signifie qu’elles sont introduites par la locution « Lorsque les TIC'.Une exigence est respectée lorsque la condition préalable est vraie et que le test correspondant (en annexe C) est réussi. Lorsque l’une des conditions préalables est fausse, l’exigence est non applicable. Par conséquent, le résultat des tests de l’annexe C peut être : non applicable, réussite, échec ou (dans des circonstances exceptionnelles) non testable.

Les TIC sont souvent constituées d’un assemblage de deux ou plusieurs éléments de TIC. Dans certains cas, au moins deux éléments interopérables de TIC peuvent, ensemble, répondre à davantage d’exigences de la norme lorsqu’un élément complète la fonctionnalité de l’autre et que l’ensemble répond à davantage d’exigences d’accessibilité. Toutefois, la combinaison de deux éléments de TIC, qui ne réussissent pas à satisfaire à une exigence particulière, n’aboutira pas à un système de TIC combiné qui répond à cette exigence.

Le présent document n’établit pas l’ordre de priorité des exigences.

REMARQUE 1 : Une mise en œuvre ou une maintenance ultérieure pourrait avoir une incidence sur la conformité aux exigences d’accessibilité.

REMARQUE 2 : Un échantillonnage est souvent nécessaire pour les TIC complexes lorsqu’il y a trop d’instances de l’objet à tester. Le présent document ne peut pas recommander de techniques d’échantillonnage précises pour l’évaluation des TIC car celles-ci sont propres au contexte.

La nature inhérente de certaines situations fait qu’il est impossible de faire des déclarations fiables et définitives sur le respect des exigences d’accessibilité. Par conséquent, dans ces situations, les exigences du présent document sont sans objet :

REMARQUE 3 : Même dans les situations ci-dessus, la pratique exemplaire consiste à appliquer les exigences du présent document chaque fois qu’il est possible de le faire en toute sécurité.

Annexe - Références (de la norme EN 301 549 – en anglais seulement)

2.1 Références normatives

Les références sont spécifiques, identifiées par leur date de publication et/ou leur numéro d'édition ou leur numéro de version. Seule la version citée est applicable.

Les documents cités en référence qui ne sont pas disponibles publiquement à l'emplacement prévu peuvent se trouver à ETSI References in docbox (en anglais seulement).

Les documents de référence suivants sont nécessaires à l’application du présent document.

[1] ETSI ETS 300 381 (Edition 1) (December 1994): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids".

[2] ETSI ES 200 381-1 (V1.2.1) (October 2012): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids Part 1: Fixed-line speech terminals".

[3] ETSI ES 200 381-2 (V1.1.1) (October 2012): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids; Part 2: Cellular speech terminals".

[4] W3C Recommendation (December 2008) /ISO/IEC 40500:2012: "Web Content Accessibility Guidelines (WCAG) 2.0".

[5] W3C Proposed Recommendation (June 2018): "Web Content Accessibility Guidelines (WCAG) 2.1".

2.2 Références informatives

Les références sont soit spécifiques (identifiées par la date de publication et/ou le numéro d'édition ou le numéro de version), soit non spécifiques. Pour des références spécifiques, seule la version citée est applicable. En ce qui concerne les références non spécifiques, la dernière version du document cité en référence (y compris les modifications éventuelles) est applicable.

Les documents de référence suivants ne sont pas nécessaires pour l’application du présent document, mais ils aident l’utilisateur dans un domaine particulier.

[i.1] ANSI/IEEE C63.19 (2011): "American National Standard Method of Measurement of Compatibility between Wireless Communication Devices and Hearing Aids". 

[i.2] ANSI/TIA-4965: "Receive volume control requirements for digital and analogue wireline terminals". 

[i.3] European Commission M 376-EN: "Standardization Mandate to CEN, CENELEC and ETSI in support of European accessibility requirements for public procurement of products and services in the ICT domain". 

[i.4] ETSI EG 201 013: "Human Factors (HF); Definitions, abbreviations and symbols". 

[i.5] ETSI ES 202 975: "Human Factors (HF); Requirements for relay services". 

[i.6] ETSI ETS 300 767: "Human Factors (HF); Telephone Prepayment Cards; Tactile Identifier". 

[i.7] ETSI CEN/CENELEC/ETSI Translations 101 550: "Documents relevant to EN 301 549 "Accessibility requirements suitable for public procurement of ICT products and services in Europe"". 

[i.8] ETSI CEN/CENELEC/ETSI Translations 101 551: "Guidelines on the use of accessibility award criteria suitable for publicly procured ICT products and services in Europe". 

[i.9] ETSI Translations 102 612: "Human Factors (HF); European accessibility requirements for public procurement of products and services in the ICT domain (European Commission Mandate M 376, Phase 1)". 

[i.10] ETSI TS 126 114: "Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction (3GPP TS 26.114)". 

[i.11] ETSI TS 122 173: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 (3GPP TS 22.173)". 

[i.12] ETSI TS 134 229: "Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification (3GPP TS 34.229)". 

[i.13] IETF RFC 4103 (2005): "RTP Payload for Text Conversation".

[i.14] ISO/IEC 17007:2009: "Conformity assessment - Guidance for drafting normative documents suitable for use for conformity assessment". 

[i.15] ISO 9241-11:2018:"Ergonomics of human-system interaction - Part 11: Usability: Definitions and concepts". 

[i.16] ISO 9241-110:2006: "Ergonomics of human-system interaction -- Part 110: Dialogue principles". 

[i.17] ISO 9241-171:2008: "Ergonomics of human-system interaction-Part 171: Guidance on software accessibility". 

[i.18] void

[i.19] ISO/IEC 13066-1:2011: "Information technology - Interoperability with assistive technology (AT) - Part 1: Requirements and recommendations for interoperability". 

[i.20] Recommendation ITU-T E.161 (2001): "Arrangement of digits, letters and symbols on telephones and other devices that can be used for gaining access to a telephone network". 

[i.21] Recommendation ITU-T G.722 (1988): "7 kHz audio-coding within 64 kbit/s". 

[i.22] Recommendation ITU-T G.722.2 (2003): "Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB)". 

[i.23] Recommendation ITU-T V.18 (2000): "Operational and interworking requirements for DCEs operating in the text telephone mode". 

[i.24] TIA-1083-A (2010): "Telecommunications; Telephone Terminal equipment; Handset magnetic measurement Procédures and performance requirements". 

[i.25] Section 508 of the United States Rehabilitation Act of 1973, revised 2017. REMARQUE: Disponible à https://www.section508.gov/manage/laws-and-policies . 

[i.26] W3C Working Group Note 5 September 2013: "Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT)". 

[i.27] M 554 Commission Implementing Decision C(2017)2585 of 27.4.2017 on a standardisation request to the European standardisation organisations in support of Directive (EU) 2016/2102 of the European Parliament and of the Council on the accessibility of the websites and mobile applications of public sector bodies. 

[i.28] Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies. 

[i.29]ETSI/CEN/CENELEC EN 301 549 (V2.1.2) (August 2018): "Accessibility requirements for ICT products and services". 

[i.30] ETSI/CEN/CENELEC Translations 101 552: "Guidance for the application of conformity assessment to accessibility requirements for public procurement of ICT products and services in Europe".

[i.31] ISO/IEC TS 20071-25:2017: "Information technology - User interface component accessibility - Part 25: Guidance on the audio presentation of text in videos, including captions, subtitles and other on-screen text".

[i.32] W3C Recommendation (September 2015): "Authoring Tool Accessibility Guidelines (ATAG) 2.0". REMARQUE: Disponible à https://www.w3.org/WAI/standards-guidelines/atag/.

[i.33] W3C Recommendation (September 2015): "User Agent Accessibility Guidelines (UAAG) 2.0". REMARQUE: Disponible à https://www.w3.org/WAI/standards-guidelines/uaag/.

[i.34]ISO 21542:2011: "Building construction - Accessibility and usability of the built environment".

[i.35]ISO/IEC Guide 71:2014: "Guide for addressing accessibility in standards".

[i.36]Recommendation ITU-T T.140 (1988): "Protocol for multimedia application text conversation".

[i.37]Recommendation ITU-T F.703 (2000): "Multimedia conversational services".

[i.38] W3C WebSchemas/Accessibility 2.0. REMARQUE: Disponible à https://www.w3.org/wiki/WebSchemas/Accessibility.

[i.39]Void

[i.40]Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on public procurement and repealing Directive 2004/18/EC.

Annexe – Définition des termes, symboles et abréviations (d’après la norme EN 301 549)

3.1 Termes

Aux fins du présent document, les termes figurant dans la norme EG 201 013[i.4] de l’ETSI et les définitions suivantes s’appliquent :

accessibilité:

degré selon lequel des produits, systèmes, services, environnements et installations peuvent être utilisés par des membres d'une population présentant le plus large éventail possible de caractéristiques et de capacités en vue d'atteindre un objectif spécifié dans un contexte d'utilisation donné ISO 9241-11:2018 [i.15])

  • REMARQUE 1: Le contexte d’utilisation comprend l’utilisation directe et l’utilisation assistée par des technologies d’assistance.
  • REMARQUE 2: Le contexte dans lequel les TIC sont utilisées peut avoir une incidence sur leur accessibilité globale. Le contexte peut comprendre d’autres produits et services avec lesquels les TIC sont susceptibles d’interagir.
espace d’accès:

l’espace destiné à être occupé par la personne, y compris sa technologie d’assistance, pendant qu’elle utilise le produit

Aide de suppléance à l’audition (ASA):

appareils qui aident à séparer les sons, en particulier la parole, qu’une personne veut entendre du bruit de fond en apportant le son directement dans l'oreille.

  • REMARQUET: On les trouve souvent dans les réunions et les lieux publics tels que les théâtres, les concerts et les lieux de culte. Ils peuvent également être utilisés à la maison avec les téléviseurs et autres produits à sortie sonore
Technologie d’aide (TA):

équipement, système, matériel informatique, logiciel ou service utilisé pour augmenter, maintenir ou améliorer les capacités des individus (d’après la norme ISO/CEI Guide 71:2014 [i.35]).

  • REMARQUE 1 : Technologie d'aide est un terme général plus large que produits d'assistance.
  • REMARQUE 2 : La technologie d'aide peut inclure les services d'aide et les services professionnels nécessaires à l'évaluation, la recommandation et la mise à disposition.
  • REMARQUE 3 : Lorsque les TIC ne prennent pas en charge directement la technologie d’assistance connectée, les dispositifs qui peuvent être exploités par un système mis en réseau ou connecté par un autre système de connexion à distance, ledit système distinct (y compris la technologie d’assistance incluse) peut également être considéré comme étant une technologie d’assistance.
Audiodescription

Narration ajoutée à une piste sonore intercalée avec le dialogue, qui décrit les aspects importants du contenu visuel de médias audiovisuels qui ne pourraient être compris à partir de la piste sonore principale uniquement.

  • REMARQUE: On parle aussi de “vidéo description » ou “narration descriptive ».
Outil-auteur:

Logiciel pouvant être utilisé pour créer ou modifier du contenu.

  • REMARQUE 1: Un outil-auteur peut être utilisé par un seul utilisateur ou par plusieurs utilisateurs travaillant ensemble.
  • REMARQUE 2: Un outil-auteur peut être une application autonome unique ou être composé d’un ensemble d’applications.
  • REMARQUE 3: Un outil de création peut produire un contenu destiné à être modifié ou à être utilisé par les utilisateurs finaux.
Légende

Texte ou élément visuel synchronisé constituant une solution de remplacement pour l’information sonore, vocale ou non vocale nécessaire à la compréhension du contenu média (d’après la directive WCAG 2.1[5])

  • REMARQUE: On parle également de “sous-titres » ou de “sous-titres pour les sourds et les malentendants ».
Fonction restreinte

Fonctionnalité limitée par des caractéristiques qui empêche un utilisateur de joindre, d’installer ou d’utiliser une technologie d’assistance.

Contenu

Information et expérience sensorielle à communiquer à l’utilisateur au moyen d’un logiciel, y compris le code ou le balisage qui définit la structure, la présentation et les interactions du contenu (d’après WCAG2ICT[i.26])

  • REMARQUE: Le contenu se trouve dans trois endroits: les pages Web, les documents et les logiciels. Lorsqu’il s’agit du contenu d’une page Web ou d’un document, un agent utilisateur est nécessaire afin de pouvoir communiquer à l’utilisateur l’information et l’expérience sensorielle du contenu. Lorsqu’il s’agit du contenu d’un logiciel, un agent utilisateur n’est pas nécessaire pour pouvoir communiquer à l’utilisateur l’information et l’expérience sensorielle du contenu – le logiciel exécute lui-même cette fonction.
contexte d’utilisation

combinaison d’utilisateurs, d’objectifs et de tâches, de ressources et d’environnement (d’après la norme ISO 9241-11:2018 [i.15]).

  • REMARQUE : Dans un contexte d’utilisation, l’ « environnement » inclut les environnements technique, physique, social, culturel et organisationnel.
document:

ensemble de contenu logiquement distinct (tel qu’un fichier, un ensemble de fichiers ou un média diffusé en continu) qui fonctionne comme une entité unique plutôt que comme une collection, qui ne fait pas partie d’un logiciel et qui n’inclut pas son propre agent utilisateur (d’après WCAG2ICT [i.26]).

  • REMARQUE 1 : Un document nécessite toujours un agent utilisateur pour présenter son contenu à l'utilisateur.
  • REMARQUE 2 : Les lettres, les messages électroniques, les feuilles de calcul, les livres, les images, les présentations et les films sont des exemples de documents.
  • REMARQUE 3 : Les fichiers de configuration et de stockage des logiciels, tels que les bases de données et les définitions de virus, ainsi que les fichiers d’instructions informatiques, tels que le code source, les fichiers batch/script et les micrologiciels, sont des exemples de fichiers qui font partie du logiciel et ne sont donc pas des exemples de documents. Si et quand le logiciel récupère « l’information et l’expérience sensorielle à communiquer à l’utilisateur » à partir de tels fichiers, il s’agit simplement d’une autre partie du contenu qui se produit dans le logiciel et qui est couvert par WCAG2ICT comme toute autre partie du logiciel. Lorsque de tels fichiers contiennent un ou plusieurs documents intégrés, les documents intégrés restent des documents selon cette définition.
  • REMARQUE 4 : Une collection de fichiers zippés, stockés dans un seul fichier de disque dur virtuel ou stockés dans un seul fichier chiffré du système de fichiers ne constitue pas un document unique lorsque les fichiers sont ainsi rassemblés. Le logiciel qui archive/chiffre ces fichiers ou gère le contenu du disque dur virtuel ne fonctionne pas comme un agent utilisateur pour les fichiers individuels de cette collection, car ce logiciel ne fournit pas une présentation entièrement fonctionnelle de ce contenu.
  • REMARQUE 5 : Tout ce qui peut présenter son propre contenu sans faire appel à un agent utilisateur, comme un livre automatique, n’est pas un document mais un logiciel.
  • REMARQUE 6 : Un document unique peut être composé de plusieurs fichiers, tels que le contenu vidéo et le texte des sous-titres. Ce fait n’est généralement pas apparent pour l’utilisateur final qui consomme le document/contenu.
  • REMARQUE 7 : Un assemblage de fichiers représentant les fichiers vidéo, audio, de sous-titres et de synchronisation d’un film est un exemple de document.
  • REMARQUE 8 : Une reliure utilisée pour relier les différentes pièces à conviction d’une affaire judiciaire ne serait pas un document.
  • REMARQUE 9 : Les documents pourraient contenir des sous-documents.
intégré:

directement inclus dans le contenu qui est téléchargé vers l’agent utilisateur et son extension, et qui est destiné à être utilisé pour le rendu de la page Web.

  • REMARQUE : Un élément qui est téléchargé à l’aide d’un mécanisme sur la page Web mais qui n’est pas utilisé pour rendre la page n’est pas « intégré » dans la page.
Réseau de TIC:

technologie et ressources permettant la connexion et le fonctionnement de TIC interconnectées.

Technologies de l’information et des communications (TIC):

technologie, équipement ou système ou sous-système interconnecté d’équipements dont la fonction principale est la création, la conversion, la duplication, l’acquisition automatique, le stockage, l’analyse, l’évaluation, la manipulation, la gestion, le déplacement, le contrôle, l’affichage, la commutation, l’échange, la transmission, la réception ou la diffusion de données ou d’informations.

  • REMARQUE : Les pages Web, le contenu électronique, les produits de télécommunications, les ordinateurs et les équipements auxiliaires, les logiciels, y compris les applications mobiles, les kiosques d’information et les machines de transaction, les vidéos, les services informatiques et les machines de bureau multifonctions qui copient, numérisent et télécopient des documents sont des exemples de TIC.
pièce manœuvrablee mécanique:

pièce manoeuvrable qui possède une interface mécanique pour activer, désactiver ou ajuster la TIC.

  • REMARQUE : Les couvercles de scanners, les stations d’accueil d’ordinateurs portables et les couvercles, ainsi que les interrupteurs et les verrous physiques sont des exemples de pièces manœuvrables mécaniques.
mécanisme d’écoute privée:

sortie sonore conçue pour que seul l'utilisateur actuel puisse recevoir le son.

  • REMARQUE : Les casques d’écoute personnels, les haut-parleurs directionnels et les capots audio sont des exemples de mécanismes d’écoute privée.
contenu non textuel:

contenu qui n’est pas une séquence de caractères pouvant être déterminée par un programme informatique ou dans lequel la séquence n’exprime pas quelque chose en langage humain (d’après WCAG 2.1 [5]).

document non Web:

document qui n’est pas une page Web, qui n’est pas intégré dans une page Web et qui n’est pas utilisé pour le rendu ou le fonctionnement de la page.

logiciel non Web:

logiciel qui n’est pas une page Web, qui n’est pas intégré dans une page Web et qui n’est pas utilisé pour le rendu ou le fonctionnement de la page.

Fonction non restreinte:

fonctionnalité qui prend en charge l’accès par une technologie d’assistance

  • REMARQUE: C’est le contraire de la fonction restreinte.
Pièce manœuvrable:

Composante des TIC utilisée pour les activer, les désactiver ou les ajuster.

  • REMARQUE 1: Les pièces manœuvrables peuvent être fournies pour le matériel (voir les pièces manœuvrables mécaniques ci-dessus) et les logiciels. Un bouton à l’écran est un exemple d’une pièce manœuvrable fournie par un logiciel.
  • REMARQUE 2 : Les pièces manoeuvrables ne comprennent pas les pièces utilisées uniquement pour l’entretien ou la réparation ou d’autres interventions qui ne sont pas attendues d’un utilisateur typique si le produit fonctionne bien. Ces interventions comprennent : l’élimination des bourrages papier à l’intérieur de la machine, le remplacement des éléments ou des pièces internes de la machine qui peuvent exposer l’utilisateur final à des surfaces tranchantes ou chaudes, le remplacement ou la réparation des éléments désignés par les fabricants comme des éléments de service ou d’entretien dans la documentation utilisateur.
Logiciel de plateforme (plateforme):

ensemble de composants logiciels qui s’exécute sur une couche logicielle ou matérielle sous-jacente et qui fournit un ensemble de services logiciels à d’autres composants logiciels permettant d’isoler ces applications de la couche logicielle ou matérielle sous-jacente (d’après ISO/IEC 13066-1[i.19])

  • REMARQUE: Un composant logiciel particulier peut jouer le rôle d’une plateforme dans certaines situations et d’un client dans d’autres.
Déterminable par programmation:

capable d’être lu par un logiciel à partir de données fournies par le développeur de sorte que d’autres logiciels, y compris les technologies d’assistance, puissent extraire et présenter ces renseignements aux utilisateurs selon différentes modalités.

  • REMARQUE: La directive WCAG 2.1 utilise l’adjectif “déterminé » alors que la présente définition utilise l’expression “capable d’être lu » (pour éviter toute ambiguïté avec le mot “déterminé »).
Texte en Temps Réel (TTR):

form of a text conversation in point to point situations or in multipoint conferencing where the text being entered is sent in such a way that the communication is perceived by the user as being continuous

  • REMARQUE 1 : Les utilisateurs percevront la communication comme continue si le délai entre la création du texte par l’expéditeur et sa réception par le destinataire est inférieur à 500 ms. Toutefois, le délai réel dépendra du réseau de communication.
  • REMARQUE 2 : La création de texte différera selon que le système permet d’entrer le texte mot par mot (p. ex., la conversion de la voix en texte et la saisie du texte prédictif) ou d’entrer un caractère à la fois. La création de texte sera différente selon qu’il s’agit de systèmes où le texte est saisi mot par mot (p. ex. les systèmes de transmission automatique de la parole et de texte prédictif) ou de systèmes où chaque caractère est généré séparément (par exemple, la saisie sur un clavier physique).
Satisfait à un critère de réussite

Le critère de réussite ne se révèle pas faux lorsqu’il est appliqué au TIC (d’après la directive WCAG 2.1 [5])

Connexion utilisateur unique:

connexion constituée de son, de TTR ou de vidéo (ou d’une combinaison de deux ou trois de ces médias) établie par une seule action de l'utilisateur.

  • REMARQUE : Même si les différents médias peuvent emprunter des canaux différents et impliquent plusieurs composants matériels, l’utilisateur a l’impression qu’il s’agit d’une connexion unique, et elle est traitée par toutes les technologies intermédiaires (p. ex. le réseau, l'auto-réception) comme une connexion unique à des fins comme le transfert.
Sous-titres vocaux/sous-titres audio:

les sous-titres qui sont exprimés vocalement sur le contenu audiovisuel (d’après la norme ISO/IEC TS 20071-25 [i.31])

TIC fixes:

TIC qui reposent sur le sol, ou qui sont montées sur un mur ou une autre structure immobile, et qui ne sont pas destinées à être déplacées par leur utilisateur.

  • REMARQUE 1 : En général, les TIC fixes reposent sur le sol (comme un kiosque d’information) ou sont installées dans un mur (comme une machine qui distribue de l’argent ou effectue d’autres services bancaires).
  • REMARQUE 2 : Un fabricant ne peut pas contrôler la hauteur des TIC posées sur une table par quelqu’un d’autre, mais il est en mesure de contrôler les dimensions de la portée des TIC autonomes qui reposent sur le sol et peut spécifier les hauteurs d’installation dans les murs.
Terminal

Ensemble de matériel et de logiciel grâce auquel l’utilisateur final interagit directement et qui fournit l’interface utilisateur.

  • REMARQUE 1: Le matériel peut être composé de plusieurs appareils fonctionnant ensemble, par exemple un appareil mobile et un ordinateur.
  • REMARQUE 2: Pour certains systèmes, le logiciel qui fournit l’interface utilisateur peut se trouver sur plusieurs appareils, comme un téléphone et un serveur.
À tour de rôle:

type d’organisation dans la conversation et le discours selon lequel les participants parlent un à la fois, chacun leur tour.

Agent utilisateur:

Tout logiciel qui récupère et présente le contenu aux utilisateurs (d’après la directive WCAG 2.1[5])

  • Tout logiciel qui récupère et présente le contenu aux utilisateurs (d’après la directive WCAG 2.1[5])
  • REMARQUE 2: À titre d’exemple de logiciel qui n’est pas un agent utilisateur, on peut citer une application de calculatrice qui n’obtient pas les résultats des calculs à l’extérieur du logiciel afin de les présenter à un utilisateur. Dans ce cas, le logiciel de la calculatrice n’est pas un agent utilisateur, c’est simplement un logiciel doté d’une interface utilisateur.
  • REMARQUE 3: Les logiciels qui n’affichent qu’un aperçu du contenu tel qu’une vignette ou toute autre présentation qui n’est pas entièrement opérationnelle ne fournissent pas de fonctionnalité d’agent utilisateur.
Interface utilisateur:

Toutes les composantes d’un système interactif (logiciel ou matériel) qui fournissent des renseignements ou des commandes permettant à l’utilisateur d’accomplir des tâches spécifiques avec le système interactif (d’après la norme ISO 9241-110[i.16])

Élément d’interface utilisateur:

Entité de l’interface utilisateur qui est présentée à l’utilisateur par le logiciel (d’après la norme ISO 9241¬171[i.17])

  • REMARQUE 1: On parle aussi de “composante d’interface utilisateur ».
  • REMARQUE 2: Les éléments d’interface utilisateur peuvent être interactifs ou non.
Contenu Web:

contenu qui se trouve dans une page Web, et qui est utilisé dans la restitution ou qui est conçu pour être utilisé dans la restitution de la page Web.contenu qui se trouve dans une page Web, et qui est utilisé dans la restitution ou qui est conçu pour être utilisé dans la restitution de la page Web.

Page Web:

Une ressource autonome obtenue depuis un URI unique grâce au protocole HTTP, accompagnée de toutes les autres ressources utilisées dans la restitution ou conçues pour être restituées simultanément par un agent utilisateur (d’après la directive WCAG 2.1[5])

3.2 Symboles

Sans objet

3.3 Abréviations

Aux fins du présent document, les abréviations suivantes sont employées :

ANSI
American National Standards Institute/ Loi sur les Américains en situation de handicap
AT
Assistive Technology/ Technologie d’Assistance (TA)
ATAG
Authoring Tool Accessibility Guidelines (of W3C)/ Règles d'accessibilité pour les outils d'édition (du W3C)
CEN
Comité Européen de Normalisation
CSS
Cascading Style Sheets/ Feuilles de style en cascade
DOM
Document Object Model/ Modèle d'objets de document
EU
European Union/ Union européenne
IPS
Images par seconde
FXML
XML-based user interface markup language (pas de terme en français)
HTML
HyperText Markup Language (pas de terme en français)
HTTP
HyperText Transfer Protocol (pas de terme en français)
ICT
Information and Communication Technology/ Technologies de l’information et des communications (TIC)
IETF
Internet Engineering Task Force (pas de terme en français)
IMS
IP Multimedia System/ Sous-système multimédia IP
IP
Internet Protocol/ Protocole internet
JWG
Joint Working Group (of CEN/CENELEC/ETSI)
ODF
Open Document Format/ Format OpenDocument
OOXML
Office Open eXtensible Markup Language (pas de terme en français)
RTPC
Réseau téléphonique public commuté
RFC
Request For Comment/ Demande de commentaires
TTR
Texte en temps réel
SIP
Session Initiation Protocol (pas de terme en français)
URI
Uniform Resource Identifier/ Identifiant uniforme de ressource
USB
Universal Serial Bus/ bus série universel
VoIP
Voice over IP/ Voix sur IP
W3C
World Wide Web Consortium (pas de terme en français)
WCAG
Web Content Accessibility Guidelines (of W3C/ Règles pour l’accessibilité des contenus Webdd>
XML
eXtensible Markup Language/ Langage de balisage extensible
XUL
XML User interface Language (pas de terme en français)
ISO
International Organization for Standardization/ Organisation internationale de normalisation
ITU-T
International Telecommunication Union - Telecommunication standardization sector/ Union internationale des télécommunications - Secteur de la normalisation des télécommunications
LED
Light Emitting Device/ Diode électroluminescente
QVGA
Quarter Video Graphics Array (pas de terme en français)
UAAG
User Agent Accessibility Guidelines (of W3C)/ Directives pour l'accessibilité des agents utilisateurs (du W3C)
VGA
Video Graphics Array (pas de terme en français)
WAI
Web Accessibility Initiative/ L'Initiative d'Accès au Web
WLAN
Wireless Local Access Network (pas de terme en français)

Annexe - Conseils pratiques sur la création d’une documentation non-Web accessible

Dans les WCAG, les « critères de succès » sont tous agnostiques sur le plan technologique. Les exigences relatives aux documents non-Web sont basées sur les exigences de niveau AA de la norme WCAG 2.1, ce qui signifie que tous les critères de niveau A et AA pertinents pour les documents doivent être respectés.

Les W3C publient des techniques suffisantespour répondre aux critères de succès du WCAG, y compris des techniques pour les formats de document autres que Web, tels que PDF. L'utilisation d'une technique donnée est considérée « suffisante » pour répondre aux critères pertinents pour la technique, mais vous pouvez également répondre aux critères d'autres manières.

Services partagés Canada a créé un ensemble de guides pour la production de documents accessibles dans Microsoft Office:

Divers organismes et fournisseurs de logiciels offrent du matériel supplémentaire proposant des instructions en vue de rendre les documents accessibles:

REMARQUE : Le fait de suivre les conseils prodigués dans les liens susmentionnés ne garantit pas la conformité aux normes WCAG 2.1. Les liens sont fournis à titre indicatif seulement.

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/handicaps-cognitifs/index.html b/fr/handicaps-cognitifs/index.html index 922ecfee0..3196a62e9 100644 --- a/fr/handicaps-cognitifs/index.html +++ b/fr/handicaps-cognitifs/index.html @@ -1,4 +1,4 @@ -Handicaps cognitifs - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Handicaps cognitifs

Les déficiences cognitives prennent de nombreuses formes, notamment des troubles de la mémoire à court et à long terme et des différences de perception. Les troubles du langage, notamment la dyslexie et les déficiences temporaires associées à ceux qui tentent d’apprendre de nouvelles langues, sont également des problèmes cognitifs courants.

On trouve une vaste gamme de déficience cognitive, telle que l’affaiblissement de la mémoire à court et à long terme et la différence perceptuelle. Les troubles du langage, y compris la dyslexie et les troubles temporaires associés à l’apprentissage de nouvelles langues, sont également des problèmes cognitifs courants. Habituellement, une combinaison de technologie informatique adaptative est utilisée pas les personnes en situation de handicaps cognitifs.

Les troubles cognitifs peuvent survenir seuls ou résulter de diverses conditions ou blessures telles que les lésions cérébrales traumatiques. Ils peuvent également coexister avec d’autres types de handicaps.

Des handicaps intellectuels

Définition :

La déficience intellectuelle se caractérise par des limitations importantes à la fois dans le fonctionnement intellectuel (raisonnement, apprentissage, résolution de problèmes) et dans le comportement adaptatif, qui couvre une gamme de compétences sociales et pratiques quotidiennes.

Une personne a une déficience intellectuelle si elle répond à trois critères selon le « American Association of Intellectual and Developmental Disabilities » :

  • Leur QI est inférieur à 70 à 75
  • Il existe des limites importantes dans deux domaines adaptatifs ou plus (compétences nécessaires pour vivre, travailler et jouer dans la communauté, comme la communication ou les soins personnels)
  • La condition se manifeste avant l’âge de 18 ans
Caractéristiques :

Les personnes ayant une déficience intellectuelle peuvent :

  • S’asseoir, ramper ou marcher plus tard que les autres enfants
  • Apprendre à parler plus tard, ou avoir des difficultés à comprendre et à parler
  • Avoir du mal à se souvenir des choses
  • Avoir du mal à comprendre les règles et les signaux sociaux
  • Avoir du mal à voir les résultats de leurs actions
  • Avoir du mal à résoudre des problèmes et à prendre des décisions

Lecture et dyslexie

Définition :

La dyslexie est une déficience d’apprentissage qui nuit à la capacité d’une personne à lire. Le handicap peut résulter d’une différence congénitale, d’une blessure, d’un retard de développement, d’un handicap neurologique ou physique. Les professionnels identifient et diagnostiquent des troubles spécifiques de la lecture, tels que la dyslexie chez les enfants et les adolescents. Souvent, le diagnostic d’un trouble de l’apprentissage comprend des éléments d’un trouble de la lecture.

Les personnes atteintes de dyslexie à l’âge adulte se développent généralement après une lésion cérébrale ou dans le contexte d’une démence. Des études récentes ont identifié un certain nombre de gènes qui peuvent prédisposer une personne à développer une dyslexie. La dyslexie peut être héréditaire dans certaines familles.

Caractéristiques :

Les déficiences de lecture peuvent inclure :

  • Une incapacité à percevoir un texte ou à traiter le sens des mots, des phrases et des idées
  • Lisent généralement à des niveaux inférieurs à ceux attendus malgré leur intelligence normale
  • Difficultés dans le traitement phonologique (la manipulation des sons), l’orthographe et / ou une réponse visuelle-verbale rapide

Mathématiques et calcul

Définition :
Les handicaps mathématiques et informatiques ont un impact sur la capacité d’une personne à apprendre et à communiquer les mathématiques. La dyscalculie implique une incapacité à comprendre l’arithmétique et la façon de calculer. Ce handicap peut être compliqué par la dysgraphie, qui peut inclure une incapacité à dessiner ou à copier des figures et des graphiques, et par l’anxiété. La dyscalculie peut être congénitale ou résulte d’une blessure, d’une maladie ou du vieillissement.
Caractéristiques :

D’après le document « Qu’est-ce que la dyscalculie » de Understood et d’autres sources, les signes courants de la dyscalculie comprennent des difficultés à :

  • Saisir la signification des quantités ou des concepts comme le plus grand par rapport au plus petit
  • Problèmes de mots qui exigent des compétences en mathématiques
  • Comprendre que le chiffre 4 est le même que le mot quatre, et que les deux signifient quatre objets
  • Concepts mathématiques de base, tels que l’addition, la soustraction, la multiplication et la division
  • Se souvenir des faits mathématiques à l’école, comme les tables de multiplication
  • Opérations mathématiques, telles que le portage, l’emprunt et le regroupement
  • Le temps et l’argent, comme estimer le temps, compter l’argent et rendre la monnaie
  • Raisonnement spatial, comme évaluer la vitesse ou la distance
  • Séquences de chiffres, comme les numéros de téléphone et les adresses

Trouble d’hyperactivité avec déficit de l’attention

Définition :
Le trouble déficitaire de l’attention avec hyperactivité (TDAH) est un trouble du développement neurologique qui affecte aussi bien les enfants que les adultes. Les symptômes apparaissent généralement vers l’âge de 7 ans. Bien que le TDAH ne disparaisse pas, les gens apprennent à s’adapter. Le TDAH se caractérise par des difficultés d’attention, de l’impulsivité et de l’hyperactivité qui peuvent interférer avec le fonctionnement quotidien et les relations.
Caractéristiques :

Les principaux symptômes du TDAH sont :

  • Inattention : difficultés à se concentrer, oublis, distraction et désorganisation
  • Impulsivité : agir sans réfléchir, interrompre les autres et avoir du mal à attendre son tour
  • Hyperactivité : bougeotte, agitation, bavardage excessif et incapacité à rester assis

Troubles du spectre de l'autisme

Définition :

Selon l’Organisation mondiale de la santé : Le trouble du spectre de l'autisme (TSA) fait référence à une gamme de conditions caractérisées par un certain degré de comportement social, de communication et de langage altéré, et une gamme étroite d’intérêts et d’activités qui sont à la fois uniques à l’individu et réalisés de manière répétitive.

Les TSA apparaissent dès l’enfance et ont tendance à persister à l’adolescence et à l’âge adulte. Les personnes atteintes de TSA présentent souvent d’autres conditions concomitantes, telles que l’épilepsie, la dépression, l’anxiété et le trouble déficitaire de l’attention avec hyperactivité (TDAH). Le niveau de fonctionnement intellectuel chez les personnes atteintes de TSA est extrêmement variable, s’étendant d’altération profonde à des niveaux supérieurs.

Caractéristiques :

Les personnes atteintes de TSA peuvent présenter des traits suivants :

  • Difficulté à interagir socialement : établir et maintenir des relations, comprendre les signaux sociaux et comprendre ou parler de ses sentiments
  • Difficultés de communication : utiliser et comprendre le langage, établir un contact visuel, donner des réponses sans rapport aux questions et répéter des mots ou des phrases à plusieurs reprises
  • Difficulté à supporter le changement, par exemple être contrarié par des changements mineurs
  • Intérêts étroits, tels que des intérêts obsessionnels
  • Comportement répétitif, comme battre des mains ou aligner des objets
  • Mouvements moteurs inhabituels, tels que battre des mains et bercer son corps
  • Battre des mains, bercer son corps ou tourner en rond
  • Sensibilités sensorielles : réactions inhabituelles au son, à l’odeur, au goût, à l’apparence ou à la sensation des choses

Trouble d’apprentissage non verbal (TANV)

Définition :
Selon le « University of Michigan, Michigan Medicine resource, Your Child Development and Behavior Resources, Non-verbal Learning Disability » : Le trouble d’apprentissage non verbal (TANV) ressemble beaucoup au syndrome d’Asperger (SA), dans lequel les personnes atteintes de ce syndrome ont une intelligence et un développement du langage normaux, mais ont des difficultés avec les compétences sociales, les apports sensoriels et les transitions. Le SA et le TANV sont généralement considérés comme décrivant le même type de trouble, mais avec une différence de SA décrivant des symptômes plus graves.
Caractéristiques :

Certains des signes de TANV incluent :

  • Grandes capacités de vocabulaire, d’expression verbale et de compréhension de la lecture
  • Excellente mémoire des détails
  • Attention aux détails, mais absence de vision d’ensemble
  • Raisonnement abstrait et résolution de problèmes médiocres
  • Difficulté à lire des cartes, à interpréter des graphiques, à résoudre des énigmes et à gérer le temps
  • Difficulté à planifier, organiser et gérer les tâches
  • Maladresse physique, mauvaise coordination
  • Mauvaises aptitudes sociales
  • Difficulté à comprendre les signaux sociaux, le langage corporel, le sarcasme et l’humour
  • Difficulté à s’adapter aux changements
  • Anxiété, dépression, faible estime de soi

Obstacles pour les personnes souffrant de troubles cognitifs

De l’Initiative de l’accessibilité du Web de W3C et d’autres sources :

Défis et solutions pour la lecture et la dyslexie

Perçoit les mots comme flottants et non alignés :

Perçoit les mots différemment des autres, par exemple en confondant les lettres p, b, d, et q :

Nécessite du temps supplémentaire pour lire et traiter le contenu :

A la charge de déchiffrer le contenu à partir de la manière dont il est présenté :

Avoir des difficultés à résoudre les problèmes présentés par les fonctionnalités de sécurité telles que CAPTCHA :

Avoir des difficultés à traiter le contenu par des moyens visuels :

Difficultés d’orthographe :

Défis et solutions en mathématiques et en calcul

Incapacité à distinguer la droite de la gauche dans les images graphiques :

Incapacité à effectuer des calculs :

Technologies d’assistance et Stratégies adaptatives pour les Déficiences cognitives

Voici quelques produits couramment utilisés :

Voici des liens à des tutoriels :

Pour la communication :

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Handicaps cognitifs

Les déficiences cognitives prennent de nombreuses formes, notamment des troubles de la mémoire à court et à long terme et des différences de perception. Les troubles du langage, notamment la dyslexie et les déficiences temporaires associées à ceux qui tentent d’apprendre de nouvelles langues, sont également des problèmes cognitifs courants.

On trouve une vaste gamme de déficience cognitive, telle que l’affaiblissement de la mémoire à court et à long terme et la différence perceptuelle. Les troubles du langage, y compris la dyslexie et les troubles temporaires associés à l’apprentissage de nouvelles langues, sont également des problèmes cognitifs courants. Habituellement, une combinaison de technologie informatique adaptative est utilisée pas les personnes en situation de handicaps cognitifs.

Les troubles cognitifs peuvent survenir seuls ou résulter de diverses conditions ou blessures telles que les lésions cérébrales traumatiques. Ils peuvent également coexister avec d’autres types de handicaps.

Des handicaps intellectuels

Définition :

La déficience intellectuelle se caractérise par des limitations importantes à la fois dans le fonctionnement intellectuel (raisonnement, apprentissage, résolution de problèmes) et dans le comportement adaptatif, qui couvre une gamme de compétences sociales et pratiques quotidiennes.

Une personne a une déficience intellectuelle si elle répond à trois critères selon le « American Association of Intellectual and Developmental Disabilities » :

  • Leur QI est inférieur à 70 à 75
  • Il existe des limites importantes dans deux domaines adaptatifs ou plus (compétences nécessaires pour vivre, travailler et jouer dans la communauté, comme la communication ou les soins personnels)
  • La condition se manifeste avant l’âge de 18 ans
Caractéristiques :

Les personnes ayant une déficience intellectuelle peuvent :

  • S’asseoir, ramper ou marcher plus tard que les autres enfants
  • Apprendre à parler plus tard, ou avoir des difficultés à comprendre et à parler
  • Avoir du mal à se souvenir des choses
  • Avoir du mal à comprendre les règles et les signaux sociaux
  • Avoir du mal à voir les résultats de leurs actions
  • Avoir du mal à résoudre des problèmes et à prendre des décisions

Lecture et dyslexie

Définition :

La dyslexie est une déficience d’apprentissage qui nuit à la capacité d’une personne à lire. Le handicap peut résulter d’une différence congénitale, d’une blessure, d’un retard de développement, d’un handicap neurologique ou physique. Les professionnels identifient et diagnostiquent des troubles spécifiques de la lecture, tels que la dyslexie chez les enfants et les adolescents. Souvent, le diagnostic d’un trouble de l’apprentissage comprend des éléments d’un trouble de la lecture.

Les personnes atteintes de dyslexie à l’âge adulte se développent généralement après une lésion cérébrale ou dans le contexte d’une démence. Des études récentes ont identifié un certain nombre de gènes qui peuvent prédisposer une personne à développer une dyslexie. La dyslexie peut être héréditaire dans certaines familles.

Caractéristiques :

Les déficiences de lecture peuvent inclure :

  • Une incapacité à percevoir un texte ou à traiter le sens des mots, des phrases et des idées
  • Lisent généralement à des niveaux inférieurs à ceux attendus malgré leur intelligence normale
  • Difficultés dans le traitement phonologique (la manipulation des sons), l’orthographe et / ou une réponse visuelle-verbale rapide

Mathématiques et calcul

Définition :
Les handicaps mathématiques et informatiques ont un impact sur la capacité d’une personne à apprendre et à communiquer les mathématiques. La dyscalculie implique une incapacité à comprendre l’arithmétique et la façon de calculer. Ce handicap peut être compliqué par la dysgraphie, qui peut inclure une incapacité à dessiner ou à copier des figures et des graphiques, et par l’anxiété. La dyscalculie peut être congénitale ou résulte d’une blessure, d’une maladie ou du vieillissement.
Caractéristiques :

D’après le document « Qu’est-ce que la dyscalculie » de Understood et d’autres sources, les signes courants de la dyscalculie comprennent des difficultés à :

  • Saisir la signification des quantités ou des concepts comme le plus grand par rapport au plus petit
  • Problèmes de mots qui exigent des compétences en mathématiques
  • Comprendre que le chiffre 4 est le même que le mot quatre, et que les deux signifient quatre objets
  • Concepts mathématiques de base, tels que l’addition, la soustraction, la multiplication et la division
  • Se souvenir des faits mathématiques à l’école, comme les tables de multiplication
  • Opérations mathématiques, telles que le portage, l’emprunt et le regroupement
  • Le temps et l’argent, comme estimer le temps, compter l’argent et rendre la monnaie
  • Raisonnement spatial, comme évaluer la vitesse ou la distance
  • Séquences de chiffres, comme les numéros de téléphone et les adresses

Trouble d’hyperactivité avec déficit de l’attention

Définition :
Le trouble déficitaire de l’attention avec hyperactivité (TDAH) est un trouble du développement neurologique qui affecte aussi bien les enfants que les adultes. Les symptômes apparaissent généralement vers l’âge de 7 ans. Bien que le TDAH ne disparaisse pas, les gens apprennent à s’adapter. Le TDAH se caractérise par des difficultés d’attention, de l’impulsivité et de l’hyperactivité qui peuvent interférer avec le fonctionnement quotidien et les relations.
Caractéristiques :

Les principaux symptômes du TDAH sont :

  • Inattention : difficultés à se concentrer, oublis, distraction et désorganisation
  • Impulsivité : agir sans réfléchir, interrompre les autres et avoir du mal à attendre son tour
  • Hyperactivité : bougeotte, agitation, bavardage excessif et incapacité à rester assis

Troubles du spectre de l'autisme

Définition :

Selon l’Organisation mondiale de la santé : Le trouble du spectre de l'autisme (TSA) fait référence à une gamme de conditions caractérisées par un certain degré de comportement social, de communication et de langage altéré, et une gamme étroite d’intérêts et d’activités qui sont à la fois uniques à l’individu et réalisés de manière répétitive.

Les TSA apparaissent dès l’enfance et ont tendance à persister à l’adolescence et à l’âge adulte. Les personnes atteintes de TSA présentent souvent d’autres conditions concomitantes, telles que l’épilepsie, la dépression, l’anxiété et le trouble déficitaire de l’attention avec hyperactivité (TDAH). Le niveau de fonctionnement intellectuel chez les personnes atteintes de TSA est extrêmement variable, s’étendant d’altération profonde à des niveaux supérieurs.

Caractéristiques :

Les personnes atteintes de TSA peuvent présenter des traits suivants :

  • Difficulté à interagir socialement : établir et maintenir des relations, comprendre les signaux sociaux et comprendre ou parler de ses sentiments
  • Difficultés de communication : utiliser et comprendre le langage, établir un contact visuel, donner des réponses sans rapport aux questions et répéter des mots ou des phrases à plusieurs reprises
  • Difficulté à supporter le changement, par exemple être contrarié par des changements mineurs
  • Intérêts étroits, tels que des intérêts obsessionnels
  • Comportement répétitif, comme battre des mains ou aligner des objets
  • Mouvements moteurs inhabituels, tels que battre des mains et bercer son corps
  • Battre des mains, bercer son corps ou tourner en rond
  • Sensibilités sensorielles : réactions inhabituelles au son, à l’odeur, au goût, à l’apparence ou à la sensation des choses

Trouble d’apprentissage non verbal (TANV)

Définition :
Selon le « University of Michigan, Michigan Medicine resource, Your Child Development and Behavior Resources, Non-verbal Learning Disability » : Le trouble d’apprentissage non verbal (TANV) ressemble beaucoup au syndrome d’Asperger (SA), dans lequel les personnes atteintes de ce syndrome ont une intelligence et un développement du langage normaux, mais ont des difficultés avec les compétences sociales, les apports sensoriels et les transitions. Le SA et le TANV sont généralement considérés comme décrivant le même type de trouble, mais avec une différence de SA décrivant des symptômes plus graves.
Caractéristiques :

Certains des signes de TANV incluent :

  • Grandes capacités de vocabulaire, d’expression verbale et de compréhension de la lecture
  • Excellente mémoire des détails
  • Attention aux détails, mais absence de vision d’ensemble
  • Raisonnement abstrait et résolution de problèmes médiocres
  • Difficulté à lire des cartes, à interpréter des graphiques, à résoudre des énigmes et à gérer le temps
  • Difficulté à planifier, organiser et gérer les tâches
  • Maladresse physique, mauvaise coordination
  • Mauvaises aptitudes sociales
  • Difficulté à comprendre les signaux sociaux, le langage corporel, le sarcasme et l’humour
  • Difficulté à s’adapter aux changements
  • Anxiété, dépression, faible estime de soi

Obstacles pour les personnes souffrant de troubles cognitifs

De l’Initiative de l’accessibilité du Web de W3C et d’autres sources :

Défis et solutions pour la lecture et la dyslexie

Perçoit les mots comme flottants et non alignés :

Perçoit les mots différemment des autres, par exemple en confondant les lettres p, b, d, et q :

Nécessite du temps supplémentaire pour lire et traiter le contenu :

A la charge de déchiffrer le contenu à partir de la manière dont il est présenté :

Avoir des difficultés à résoudre les problèmes présentés par les fonctionnalités de sécurité telles que CAPTCHA :

Avoir des difficultés à traiter le contenu par des moyens visuels :

Difficultés d’orthographe :

Défis et solutions en mathématiques et en calcul

Incapacité à distinguer la droite de la gauche dans les images graphiques :

Incapacité à effectuer des calculs :

Technologies d’assistance et Stratégies adaptatives pour les Déficiences cognitives

Voici quelques produits couramment utilisés :

Voici des liens à des tutoriels :

Pour la communication :

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/index.html b/fr/index.html index 3a2a8ee4b..9efdb83bf 100644 --- a/fr/index.html +++ b/fr/index.html @@ -9,4 +9,4 @@ w.gtag('js', new Date()); w.gtag('config', 'G-SM9MSHWDVN'); } - })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Boîte à outils de l'accessibilité numérique

Bienvenue sur la Boîte à outils de l'accessibilité numérique. Nous offrons une variété de matériel d'apprentissage et de ressources pour vous aider à apprendre et à mettre en œuvre l'accessibilité dans vos projets numériques.

Découvrez votre boîte à outils

Accessibilité numérique au gouvernement du Canada

Apprenez davantage sur les normes d'accessibilité des technologies de l’information et des communications (TIC), y compris la norme EN 301 549, qui inclut les WCAG 2.1 niveau A et AA, lors de l'achat de biens ou de services ou de la conception d'un projet, ainsi que sur les rôles et les équipes liés au gouvernement du Canada.

Apprentissage et perfectionnement

Découvrez une collection de produits d'apprentissage pour améliorer votre compréhension de l'accessibilité. Que vous soyez développeur, concepteur ou passionné, explorez nos liens vers des cours, des tutoriels et des outils. Rejoignez-nous pour créer un monde numérique plus inclusif.

Comment faire

Conseils et étapes essentielles pour rendre accessibles tous vos produits et contenus numériques, tels que les documents, les réunions, etc.

Principes de base de l’accessibilité

Découvrez les principes qui guident l'accessibilité des produits et services numériques. Ces principes éliminent les obstacles pour les personnes en situation de handicap et facilitent l’utilisation pour tous.

Ressources et outils

Vous trouverez ici différents guides, ressources et outils créés par des fonctionnaires fédéraux pour faire progresser l'accessibilité numérique.

Dernières mises à jour

Explorez notre contenu le plus récent.

À propos la Boîte à outils de l'accessibilité numérique

En savoir plus sur ce projet et sur la boîte à outils de l'accessibilité numérique.

Contactez-nous

Vous souhaitez en savoir plus ? Prenez contact avec notre équipe.

Mandats

Le cadre de référence définit l’objet et la portée du projet de la Boîte à outils de l'accessibilité numérique. Il comprend des informations sur la structures du projet, les rôles clés, les membres, le fonctionnement, etc.

Projet de la Boîte à outils de l'accessibilité numérique

A propos du projet, qui nous sommes et quel est notre but.

Recherche sur notre audience

L’objectif principal de la création de ces persona était de mieux comprendre notre public cible. En développant une meilleure compréhension de nos utilisateurs, nous serons en mesure de construire une architecture de site réactive pour tout le contenu existant et futur hébergé sur le site Web de la boite à outils d’accessibilité numérique.

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Boîte à outils de l'accessibilité numérique

Bienvenue sur la Boîte à outils de l'accessibilité numérique. Nous offrons une variété de matériel d'apprentissage et de ressources pour vous aider à apprendre et à mettre en œuvre l'accessibilité dans vos projets numériques.

Découvrez votre boîte à outils

Accessibilité numérique au gouvernement du Canada

Apprenez davantage sur les normes d'accessibilité des technologies de l’information et des communications (TIC), y compris la norme EN 301 549, qui inclut les WCAG 2.1 niveau A et AA, lors de l'achat de biens ou de services ou de la conception d'un projet, ainsi que sur les rôles et les équipes liés au gouvernement du Canada.

Apprentissage et perfectionnement

Découvrez une collection de produits d'apprentissage pour améliorer votre compréhension de l'accessibilité. Que vous soyez développeur, concepteur ou passionné, explorez nos liens vers des cours, des tutoriels et des outils. Rejoignez-nous pour créer un monde numérique plus inclusif.

Comment faire

Conseils et étapes essentielles pour rendre accessibles tous vos produits et contenus numériques, tels que les documents, les réunions, etc.

Principes de base de l’accessibilité

Découvrez les principes qui guident l'accessibilité des produits et services numériques. Ces principes éliminent les obstacles pour les personnes en situation de handicap et facilitent l’utilisation pour tous.

Ressources et outils

Vous trouverez ici différents guides, ressources et outils créés par des fonctionnaires fédéraux pour faire progresser l'accessibilité numérique.

Dernières mises à jour

Explorez notre contenu le plus récent.

À propos la Boîte à outils de l'accessibilité numérique

En savoir plus sur ce projet et sur la boîte à outils de l'accessibilité numérique.

Contactez-nous

Vous souhaitez en savoir plus ? Prenez contact avec notre équipe.

Mandats

Le cadre de référence définit l’objet et la portée du projet de la Boîte à outils de l'accessibilité numérique. Il comprend des informations sur la structures du projet, les rôles clés, les membres, le fonctionnement, etc.

Projet de la Boîte à outils de l'accessibilité numérique

A propos du projet, qui nous sommes et quel est notre but.

Recherche sur notre audience

L’objectif principal de la création de ces persona était de mieux comprendre notre public cible. En développant une meilleure compréhension de nos utilisateurs, nous serons en mesure de construire une architecture de site réactive pour tout le contenu existant et futur hébergé sur le site Web de la boite à outils d’accessibilité numérique.

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/introduction-aux-exigences-d-accessibilite-pour-l-audio-video/index.html b/fr/introduction-aux-exigences-d-accessibilite-pour-l-audio-video/index.html index 2548bb25b..809963f9d 100644 --- a/fr/introduction-aux-exigences-d-accessibilite-pour-l-audio-video/index.html +++ b/fr/introduction-aux-exigences-d-accessibilite-pour-l-audio-video/index.html @@ -1,4 +1,4 @@ -Introduction aux exigences d’accessibilité pour l’audio-vidéo - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Introduction aux exigences d’accessibilité pour l’audio-vidéo

Ce document est une excellente introduction sur la manière de rendre la vidéo accessible à un public de conseillers en communication se situant entre l'auteur Web et l'expert en contenu.

Introduction

L’objectif de ce guide est de vous apprendre comment faire en sorte que tous les produits d’apprentissage audio-vidéo soient accessibles à tous les apprenants. Les Règles pour l’accessibilité des contenus Web (WCAG) 2.1 et d’autres directives d’accessibilité font référence aux enregistrements audio-vidéo, en direct ou préenregistrés, en tant que médias temporels.

Voici des exemples de médias temporels :

Nous utilisons souvent l’audio et la vidéo pour présenter des informations, donner les cours et faire la démonstration de systèmes. En n’incluant pas les informations appropriées lors du développement d’un objet d’apprentissage multimédia temporel, nous excluons de nombreux apprenants ou, au minimum, nous leur rendons difficile l’accès à la formation dont ils ont besoin pour faire leur travail.

Exigences générales

L’accessibilité d’un média temporel dépend en grande partie de la prise en compte des quatre facteurs suivants : transcription, sous-titrage, description audio et accès au clavier**.** Des résumés pour chacun des facteurs sont présentés ici, tandis que des lignes directrices, des listes de contrôle et des échantillons suivent plus loin dans le document.

Résumé de la transcription

Les transcriptions sont l’équivalent textuel d’un fichier audio ou vidéo. Elles permettent aux personnes qui ne peuvent voir ou entendre le contenu pour les raisons ci-dessous d’accéder à de l’information à l’aide de médias audio ou visuels. Il convient de s’assurer que toutes les transcriptions comprennent ce qui suit :

Directives pour la transcription

Liste de contrôle la transcription

Résumé du sous-titrage

Les vidéos avec du son nécessitent un sous-titrage synchronisé (où le texte s’aligne sur l’action ou les actions à l’écran ou les mots prononcés dans l’audio). La plupart des "sous-titres codés" peuvent être cachés ou affichés par les personnes qui regardent la vidéo. Il peut également s'agir de "sous-titres ouverts" qui sont toujours affichés et ne peuvent pas être désactivés.

Il est recommandé de placer des sous-titres en haut des vidéos ASL et LSQ.

Tout ce qui est dit ou entendu dans la vidéo doit être inclus dans le sous-titrage. Il est important que les sous-titres codés soient :

Les équipes de conception ou un entrepreneur peuvent fournir le texte de la légende.

Directives pour le sous-titrage

Liste de contrôle pour le sous-titrage

Sommaire de la description sonore

La description sonore permet à tout utilisateur souffrant d’un handicap visuel ou cognitif de recevoir une expérience très détaillée et descriptive de ce qui se passe à l’écran. Pendant les pauses existantes dans le dialogue, la description sonore fournit des informations sur les actions, les personnages, les changements de scène et le texte à l’écran qui sont importants et qui ne sont pas décrits ou parlés dans la bande sonore principale.

Cela peut être fait en utilisant :

Directives pour la description sonore

Liste de contrôle pour la description sonore

Accès au clavier

Toutes les commandes vidéo doivent être accessibles, et on doit pouvoir y naviguer à l’aide du clavier. Il est de la responsabilité de l’équipe de microédition de s’assurer que les lecteurs vidéo sont accessibles, notamment :

L'accès au clavier est testé par le développeur, les équipes de conception ou un entrepreneur.

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Introduction aux exigences d’accessibilité pour l’audio-vidéo

Ce document est une excellente introduction sur la manière de rendre la vidéo accessible à un public de conseillers en communication se situant entre l'auteur Web et l'expert en contenu.

Introduction

L’objectif de ce guide est de vous apprendre comment faire en sorte que tous les produits d’apprentissage audio-vidéo soient accessibles à tous les apprenants. Les Règles pour l’accessibilité des contenus Web (WCAG) 2.1 et d’autres directives d’accessibilité font référence aux enregistrements audio-vidéo, en direct ou préenregistrés, en tant que médias temporels.

Voici des exemples de médias temporels :

Nous utilisons souvent l’audio et la vidéo pour présenter des informations, donner les cours et faire la démonstration de systèmes. En n’incluant pas les informations appropriées lors du développement d’un objet d’apprentissage multimédia temporel, nous excluons de nombreux apprenants ou, au minimum, nous leur rendons difficile l’accès à la formation dont ils ont besoin pour faire leur travail.

Exigences générales

L’accessibilité d’un média temporel dépend en grande partie de la prise en compte des quatre facteurs suivants : transcription, sous-titrage, description audio et accès au clavier**.** Des résumés pour chacun des facteurs sont présentés ici, tandis que des lignes directrices, des listes de contrôle et des échantillons suivent plus loin dans le document.

Résumé de la transcription

Les transcriptions sont l’équivalent textuel d’un fichier audio ou vidéo. Elles permettent aux personnes qui ne peuvent voir ou entendre le contenu pour les raisons ci-dessous d’accéder à de l’information à l’aide de médias audio ou visuels. Il convient de s’assurer que toutes les transcriptions comprennent ce qui suit :

Directives pour la transcription

Liste de contrôle la transcription

Résumé du sous-titrage

Les vidéos avec du son nécessitent un sous-titrage synchronisé (où le texte s’aligne sur l’action ou les actions à l’écran ou les mots prononcés dans l’audio). La plupart des "sous-titres codés" peuvent être cachés ou affichés par les personnes qui regardent la vidéo. Il peut également s'agir de "sous-titres ouverts" qui sont toujours affichés et ne peuvent pas être désactivés.

Il est recommandé de placer des sous-titres en haut des vidéos ASL et LSQ.

Tout ce qui est dit ou entendu dans la vidéo doit être inclus dans le sous-titrage. Il est important que les sous-titres codés soient :

Les équipes de conception ou un entrepreneur peuvent fournir le texte de la légende.

Directives pour le sous-titrage

Liste de contrôle pour le sous-titrage

Sommaire de la description sonore

La description sonore permet à tout utilisateur souffrant d’un handicap visuel ou cognitif de recevoir une expérience très détaillée et descriptive de ce qui se passe à l’écran. Pendant les pauses existantes dans le dialogue, la description sonore fournit des informations sur les actions, les personnages, les changements de scène et le texte à l’écran qui sont importants et qui ne sont pas décrits ou parlés dans la bande sonore principale.

Cela peut être fait en utilisant :

Directives pour la description sonore

Liste de contrôle pour la description sonore

Accès au clavier

Toutes les commandes vidéo doivent être accessibles, et on doit pouvoir y naviguer à l’aide du clavier. Il est de la responsabilité de l’équipe de microédition de s’assurer que les lecteurs vidéo sont accessibles, notamment :

L'accès au clavier est testé par le développeur, les équipes de conception ou un entrepreneur.

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/la-structure-des-regles-pour-l-accessibilite-des-contenus-web-wcag-2-1/index.html b/fr/la-structure-des-regles-pour-l-accessibilite-des-contenus-web-wcag-2-1/index.html index d6a467e59..28456e57b 100644 --- a/fr/la-structure-des-regles-pour-l-accessibilite-des-contenus-web-wcag-2-1/index.html +++ b/fr/la-structure-des-regles-pour-l-accessibilite-des-contenus-web-wcag-2-1/index.html @@ -1,4 +1,4 @@ -La structure des règles pour l'accessibilité des contenus web (WCAG) 2.1 - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

La structure des règles pour l'accessibilité des contenus web (WCAG) 2.1

Le respect de ces lignes directrices rendra le contenu plus accessible à un plus grand nombre de personnes handicapées, y compris les aménagements pour la cécité et la basse vision, la surdité et la perte d'audition, les mouvements limités, les troubles de la parole, la photosensibilité et les combinaisons de ceux-ci, ainsi que certains aménagements pour les troubles de l'apprentissage et les limitations cognitives ; mais il ne répondra pas à tous les besoins des utilisateurs souffrant de ces handicaps.

Principe 1 – Perceptible

Règle 1.1 – Équivalents textuels

Règle 1.2 – Média temporel

Règle 1.3 – Adaptable

Règle 1.4 – Distinguable

Principe 2 – Utilisable

Règle 2.1 – Accessibilité au clavier

Règle 2.2 – Délai suffisant

Règle 2.3 – Crises et réactions physiques

Règle 2.4 – Navigable

Règle 2.5 – Modalités d'entrée

Principe 3 – Compréhensible

Règle 3.1 – Lisible

Règle 3.2 – Prévisible

Règle 3.3 – Assistance à la saisie

Principe 4 – Robuste

Règle 4.1 – Compatible

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

La structure des règles pour l'accessibilité des contenus web (WCAG) 2.1

Le respect de ces lignes directrices rendra le contenu plus accessible à un plus grand nombre de personnes handicapées, y compris les aménagements pour la cécité et la basse vision, la surdité et la perte d'audition, les mouvements limités, les troubles de la parole, la photosensibilité et les combinaisons de ceux-ci, ainsi que certains aménagements pour les troubles de l'apprentissage et les limitations cognitives ; mais il ne répondra pas à tous les besoins des utilisateurs souffrant de ces handicaps.

Principe 1 – Perceptible

Règle 1.1 – Équivalents textuels

Règle 1.2 – Média temporel

Règle 1.3 – Adaptable

Règle 1.4 – Distinguable

Principe 2 – Utilisable

Règle 2.1 – Accessibilité au clavier

Règle 2.2 – Délai suffisant

Règle 2.3 – Crises et réactions physiques

Règle 2.4 – Navigable

Règle 2.5 – Modalités d'entrée

Principe 3 – Compréhensible

Règle 3.1 – Lisible

Règle 3.2 – Prévisible

Règle 3.3 – Assistance à la saisie

Principe 4 – Robuste

Règle 4.1 – Compatible

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/le-groupe-de-travail-sur-l-acces-gta/index.html b/fr/le-groupe-de-travail-sur-l-acces-gta/index.html index 19eb965f5..92abf38ee 100644 --- a/fr/le-groupe-de-travail-sur-l-acces-gta/index.html +++ b/fr/le-groupe-de-travail-sur-l-acces-gta/index.html @@ -1,4 +1,4 @@ -Le Groupe de travail sur l'accès (GTA) - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Le Groupe de travail sur l'accès (GTA)

Le Groupe de travail sur l'accès (GTA) a été créé par le Comité consultatif sur l'Internet du Conseil du Trésor (comité principal) le 1er août 1997 afin d'engager des activités de collaboration entre le gouvernement, le secteur privé et les organisations communautaires qui ont intérêt à assurer un accès équitable à l'information et aux services, en particulier pour les personnes handicapées, mais sans s'y limiter, dans le but de contribuer à l'élaboration des politiques du gouvernement du Canada (GC).

Ce contenu n'est disponible qu'en anglais pour le moment. Nous travaillons actuellement à une traduction française du contenu. Veuillez rester à l'écoute.

Contenu à venir

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Le Groupe de travail sur l'accès (GTA)

Le Groupe de travail sur l'accès (GTA) a été créé par le Comité consultatif sur l'Internet du Conseil du Trésor (comité principal) le 1er août 1997 afin d'engager des activités de collaboration entre le gouvernement, le secteur privé et les organisations communautaires qui ont intérêt à assurer un accès équitable à l'information et aux services, en particulier pour les personnes handicapées, mais sans s'y limiter, dans le but de contribuer à l'élaboration des politiques du gouvernement du Canada (GC).

Ce contenu n'est disponible qu'en anglais pour le moment. Nous travaillons actuellement à une traduction française du contenu. Veuillez rester à l'écoute.

Contenu à venir

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/liens-utiles/index.html b/fr/liens-utiles/index.html index c5dbf635a..01ae1d1a6 100644 --- a/fr/liens-utiles/index.html +++ b/fr/liens-utiles/index.html @@ -1,4 +1,4 @@ -Liens utiles - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Liens utiles

Cette page contient une liste de liens utiles pour le bureau d'accessibilité informatique de l'ESDC.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne
TitreDescriptionCatégorie
Partie d'un toutNicolas Steenhout rédige au sujet de l’accessibilité.Apprentissage
Quels outils de vidéoconférence sont les plus accessibles?Dans cet article, Claudio Luis Vera explique ce qu’il faut garder à l’esprit lors du choix d’un outil de vidéoconférence pour que tous les membres de votre équipe puissent en profiter — notamment ceux avec des handicaps.Apprentissage
Solution de gabarits à déploiement centralisé (SGDC) (en anglais seulement)L’accessibilité est une pierre angulaire importante du développement iOS. Elle permet à tous d’utiliser vos applications, peu importe leurs handicaps. Heureusement, UIKit offre plusieurs API, qui permettent aux développeurs d’offrir un soutien aux technologies des systèmes au sein de leurs applications.Développement
Solution de gabarits à déploiement centralisé (SGDC)L’objectif de la SGDC consiste essentiellement à fournir la couche de présentation du thème de Canada.ca ou du thème d’Intranet.canada.ca aux actifs Web.Développement
Boîte à outils de l’expérience WebCette plateforme frontale primée permet de créer des sites Web qui sont accessibles, faciles d’emploi, interopérables, adaptés aux appareils mobiles et multilingues.Développement
Guide de style du contenu de Canada.caCe sont les règles à suivre pour créer du contenu Web qui peut être facilement trouvé, compris et utilisé. Elles reposent sur des principes et des techniques de rédaction qui permettent de rendre le contenu Web clair et adapté aux besoins de tous.Développement
Spécifications sur le contenu et l’architecture de l’information du site Canada.caLe système de conception de Canada.ca fournit des modèles mis à l’essai par l’utilisateur, des patrons et des principes de conception. Le système permet aux concepteurs et aux développeurs de créer une expérience en ligne plus conviviale, plus cohérente et plus digne de confiance pour les personnes qui accèdent aux services numériques du gouvernement du Canada.Développement
Guide de style A11Y (en anglais seulement)Cette application est un guide de style vivant ou une bibliothèque de modèles, générée à partir de styles documentés KSS… avec une touche d’accessibilité.Guide de style
Demander des dates aux utilisateurs (en anglais seulement)Suivez ce modèle chaque fois que vous avez besoin que les utilisateurs fournissent ou sélectionnent une date dans le cadre de votre service.Développement
Accessibilité des sites Web de Canada.ca (CSPS - T716)Ce cours décrit les normes et les lignes directrices fédérales en matière d’accessibilité des sites Web, en mettant l’accent sur les exigences, les rôles et les responsabilités touchant la conformité à la norme. Les participants apprendront à évaluer et à appliquer WCAG 2.0 de manière cohérente dans les pages Web de Canada.ca dans le cadre de l’Initiative de renouvellement du Web.Apprentissage
18F Accessibility Guide (en anglais seulement)Guide d’accessibilité élaboré par le gouvernement des États-Unis d’Amérique.Développement
Fiches nutritionnelles pour les composantes accessibles (en anglais seulement)Les fiches nutritionnelles A11Y est une tentative de digérer et de simplifier les attentes en matière d’accessibilité lorsqu’il s’agit de la création de composantes.Développement
Le projet A11Y (en anglais seulement)Le projet A11Y est un effort communautaire visant à faciliter l’accessibilité numérique.Guide de style
Manuel de l’accessibilité du Service numérique canadienLe Service numérique canadien s’engage à mettre en place des services accessibles et inclusifs. La mise en place de services accessibles signifie de répondre aux besoins du plus grand nombre de personnes possible.Apprentissage
International Association of Accessibility Professionals (en anglais seulement)Les professionnels de l’accessibilité du monde entier se réunissent pour définir, promouvoir et améliorer la profession de l’accessibilité par le biais du réseautage, de l’éducation et de la certification.Apprentissage
Guide pour l’organisation de réunions inclusivesLes réunions bien planifiées sont un outil de communication essentiel pour toute organisation. Les réunions en milieu de travail et dans les groupes de bénévoles et les groupes communautaires rassemblent régulièrement des personnes pour partager des informations, élaborer des stratégies, travailler vers des objectifs communs et célébrer les réussites.Apprentissage
Directive visant à rendre les technologies de l’information utilisables par tousCette ligne directrice soutient la direction du gouvernement du Canada pour s’assurer que les ministères, les agences et les organisations prennent en compte l’accessibilité lors de l’acquisition ou du développement d’équipement et de solutions de la technologie de l’information (TI) pour rendre la TI utilisable par tous.Politique
EU EN 301 549 (Gestion de l’accessibilité dans les marchés publics des TIC) (en anglais seulement)Les exigences en matière d’accessibilité qui conviennent à l’approvisionnement, par les organismes publics, de produits et services de technologies de l’information et des communications (TIC) en Europe.Politique
Liste des ressources, outils et services d’accessibilité générale Lien interneDécouvrez les services, les outils et les ressources qui permettent de créer des produits de communication et des activités accessibles.Liste
Rendre les communications accessibles au sein du gouvernement du CanadaL’accessibilité consiste à respecter les différences et à supprimer les obstacles afin que chacun puisse participer.Développement
Accessibilité de M365 (en anglais seulement)Liste des ressources et du matériel d’apprentissage sur l’accessibilité de Microsoft 365 (M365).Apprentissage
Portail de l’accessibilité (en anglais seulement)Nous pensons que l’égalité numérique est un droit de l’homme pour les sites Web, les applications mobiles et le contenu numérique. Toutefois, cela ne s’arrête pas là. Nous devons faire cela pour la qualité, l’innovation, la conformité, les relations, l’expérience utilisateur et plus encore.Apprentissage
Brève remarque sur aria-label, aria-labelledby et aria-describedby (en anglais seulement)Faites attention lorsque vous utilisez les caractéristiques aria-label, aria-labelledby et aria-describedby, parce qu’ils ne fonctionnent pas de manière cohérente avec tous les éléments HTML.Développement
YouTube : Apple : Accessibilité (en anglais seulement)De l’utilisation de votre iPhone sans voir l’écran, à l’adaptation des gestes à vos besoins physiques, découvrez comment les fonctionnalités d’accessibilité intégrées à vos appareils Apple peuvent vous aider à en faire plus.Apprentissage
Considérations relatives aux lecteurs d’écran lors du choix entre Google à IU My Drive et Microsoft OneDrive à IU (en anglais seulement)Le choix entre Google à IU My Drive et Microsoft OneDrive à IU n’est pas simple lorsqu’on considère l’accessibilité relative aux lecteurs d’écran. Les deux présentent des avantages et des inconvénients, qui peuvent varier en fonction de la combinaison du lecteur d’écran et du navigateur utilisé.Apprentissage
Le Web, la conception et l’accessibilité (en anglais seulement)Je suis Martin, un concepteur d’interface utilisateur et d’interaction, amateur de HTML et de CSS, et cofondateur de Frontend NE. Voici un peu plus d’informations à mon sujet et sur ce que je fais.Apprentissage
Guide d'accessibilité du contenu Web (en anglais seulement)La base fondamentale qui vous permettra de disposer de produits numériques réellement inclusifs et accessibles.Apprentissage
Accessibility Maze : un jeu amusant pour en savoir plus sur l'accessibilité Web (en anglais seulement)L'Université Ryerson a créé Accessibility Maze, un jeu amusant, pour aider les personnes débutantes en accessibilité Web à s’exercer et apprendre davantage sur les obstacles et les défis auxquels les personnes ayant un handicap sont généralement confrontées lorsqu'elles naviguent dans Internet. Le jeu fournit des leçons rapides sur la façon d'éviter ces obstacles ou de les corriger.Apprentissage
Méthodologie d’évaluation sur l’accessibilité des sites Web (niveau AA)Aider à mesurer les critères de succès de niveau A et AA des Règles pour l’accessibilité des contenus Web (WCAG) 2.1 (anglais seulement).Développement
Ressources d'accessibilité numérique pour les fonctionnairesRessources d'accessibilité numérique pour les fonctionnaires, par les fonctionnaires.Apprentissage
Cours d'accessibilitéCours, webinaires, vidéos éducatives, et plus encore, proposés en accessibilité web.Apprentissage
Soutien d'accessibilité (en anglais seulement)Vérifier si votre code fonctionnera avec les technologies d'assistance.Développement

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Liens utiles

Cette page contient une liste de liens utiles pour le bureau d'accessibilité informatique de l'ESDC.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne
TitreDescriptionCatégorie
Partie d'un toutNicolas Steenhout rédige au sujet de l’accessibilité.Apprentissage
Quels outils de vidéoconférence sont les plus accessibles?Dans cet article, Claudio Luis Vera explique ce qu’il faut garder à l’esprit lors du choix d’un outil de vidéoconférence pour que tous les membres de votre équipe puissent en profiter — notamment ceux avec des handicaps.Apprentissage
Solution de gabarits à déploiement centralisé (SGDC) (en anglais seulement)L’accessibilité est une pierre angulaire importante du développement iOS. Elle permet à tous d’utiliser vos applications, peu importe leurs handicaps. Heureusement, UIKit offre plusieurs API, qui permettent aux développeurs d’offrir un soutien aux technologies des systèmes au sein de leurs applications.Développement
Solution de gabarits à déploiement centralisé (SGDC)L’objectif de la SGDC consiste essentiellement à fournir la couche de présentation du thème de Canada.ca ou du thème d’Intranet.canada.ca aux actifs Web.Développement
Boîte à outils de l’expérience WebCette plateforme frontale primée permet de créer des sites Web qui sont accessibles, faciles d’emploi, interopérables, adaptés aux appareils mobiles et multilingues.Développement
Guide de style du contenu de Canada.caCe sont les règles à suivre pour créer du contenu Web qui peut être facilement trouvé, compris et utilisé. Elles reposent sur des principes et des techniques de rédaction qui permettent de rendre le contenu Web clair et adapté aux besoins de tous.Développement
Spécifications sur le contenu et l’architecture de l’information du site Canada.caLe système de conception de Canada.ca fournit des modèles mis à l’essai par l’utilisateur, des patrons et des principes de conception. Le système permet aux concepteurs et aux développeurs de créer une expérience en ligne plus conviviale, plus cohérente et plus digne de confiance pour les personnes qui accèdent aux services numériques du gouvernement du Canada.Développement
Guide de style A11Y (en anglais seulement)Cette application est un guide de style vivant ou une bibliothèque de modèles, générée à partir de styles documentés KSS… avec une touche d’accessibilité.Guide de style
Demander des dates aux utilisateurs (en anglais seulement)Suivez ce modèle chaque fois que vous avez besoin que les utilisateurs fournissent ou sélectionnent une date dans le cadre de votre service.Développement
Accessibilité des sites Web de Canada.ca (CSPS - T716)Ce cours décrit les normes et les lignes directrices fédérales en matière d’accessibilité des sites Web, en mettant l’accent sur les exigences, les rôles et les responsabilités touchant la conformité à la norme. Les participants apprendront à évaluer et à appliquer WCAG 2.0 de manière cohérente dans les pages Web de Canada.ca dans le cadre de l’Initiative de renouvellement du Web.Apprentissage
18F Accessibility Guide (en anglais seulement)Guide d’accessibilité élaboré par le gouvernement des États-Unis d’Amérique.Développement
Fiches nutritionnelles pour les composantes accessibles (en anglais seulement)Les fiches nutritionnelles A11Y est une tentative de digérer et de simplifier les attentes en matière d’accessibilité lorsqu’il s’agit de la création de composantes.Développement
Le projet A11Y (en anglais seulement)Le projet A11Y est un effort communautaire visant à faciliter l’accessibilité numérique.Guide de style
Manuel de l’accessibilité du Service numérique canadienLe Service numérique canadien s’engage à mettre en place des services accessibles et inclusifs. La mise en place de services accessibles signifie de répondre aux besoins du plus grand nombre de personnes possible.Apprentissage
International Association of Accessibility Professionals (en anglais seulement)Les professionnels de l’accessibilité du monde entier se réunissent pour définir, promouvoir et améliorer la profession de l’accessibilité par le biais du réseautage, de l’éducation et de la certification.Apprentissage
Guide pour l’organisation de réunions inclusivesLes réunions bien planifiées sont un outil de communication essentiel pour toute organisation. Les réunions en milieu de travail et dans les groupes de bénévoles et les groupes communautaires rassemblent régulièrement des personnes pour partager des informations, élaborer des stratégies, travailler vers des objectifs communs et célébrer les réussites.Apprentissage
Directive visant à rendre les technologies de l’information utilisables par tousCette ligne directrice soutient la direction du gouvernement du Canada pour s’assurer que les ministères, les agences et les organisations prennent en compte l’accessibilité lors de l’acquisition ou du développement d’équipement et de solutions de la technologie de l’information (TI) pour rendre la TI utilisable par tous.Politique
EU EN 301 549 (Gestion de l’accessibilité dans les marchés publics des TIC) (en anglais seulement)Les exigences en matière d’accessibilité qui conviennent à l’approvisionnement, par les organismes publics, de produits et services de technologies de l’information et des communications (TIC) en Europe.Politique
Liste des ressources, outils et services d’accessibilité générale Lien interneDécouvrez les services, les outils et les ressources qui permettent de créer des produits de communication et des activités accessibles.Liste
Rendre les communications accessibles au sein du gouvernement du CanadaL’accessibilité consiste à respecter les différences et à supprimer les obstacles afin que chacun puisse participer.Développement
Accessibilité de M365 (en anglais seulement)Liste des ressources et du matériel d’apprentissage sur l’accessibilité de Microsoft 365 (M365).Apprentissage
Portail de l’accessibilité (en anglais seulement)Nous pensons que l’égalité numérique est un droit de l’homme pour les sites Web, les applications mobiles et le contenu numérique. Toutefois, cela ne s’arrête pas là. Nous devons faire cela pour la qualité, l’innovation, la conformité, les relations, l’expérience utilisateur et plus encore.Apprentissage
Brève remarque sur aria-label, aria-labelledby et aria-describedby (en anglais seulement)Faites attention lorsque vous utilisez les caractéristiques aria-label, aria-labelledby et aria-describedby, parce qu’ils ne fonctionnent pas de manière cohérente avec tous les éléments HTML.Développement
YouTube : Apple : Accessibilité (en anglais seulement)De l’utilisation de votre iPhone sans voir l’écran, à l’adaptation des gestes à vos besoins physiques, découvrez comment les fonctionnalités d’accessibilité intégrées à vos appareils Apple peuvent vous aider à en faire plus.Apprentissage
Considérations relatives aux lecteurs d’écran lors du choix entre Google à IU My Drive et Microsoft OneDrive à IU (en anglais seulement)Le choix entre Google à IU My Drive et Microsoft OneDrive à IU n’est pas simple lorsqu’on considère l’accessibilité relative aux lecteurs d’écran. Les deux présentent des avantages et des inconvénients, qui peuvent varier en fonction de la combinaison du lecteur d’écran et du navigateur utilisé.Apprentissage
Le Web, la conception et l’accessibilité (en anglais seulement)Je suis Martin, un concepteur d’interface utilisateur et d’interaction, amateur de HTML et de CSS, et cofondateur de Frontend NE. Voici un peu plus d’informations à mon sujet et sur ce que je fais.Apprentissage
Guide d'accessibilité du contenu Web (en anglais seulement)La base fondamentale qui vous permettra de disposer de produits numériques réellement inclusifs et accessibles.Apprentissage
Accessibility Maze : un jeu amusant pour en savoir plus sur l'accessibilité Web (en anglais seulement)L'Université Ryerson a créé Accessibility Maze, un jeu amusant, pour aider les personnes débutantes en accessibilité Web à s’exercer et apprendre davantage sur les obstacles et les défis auxquels les personnes ayant un handicap sont généralement confrontées lorsqu'elles naviguent dans Internet. Le jeu fournit des leçons rapides sur la façon d'éviter ces obstacles ou de les corriger.Apprentissage
Méthodologie d’évaluation sur l’accessibilité des sites Web (niveau AA)Aider à mesurer les critères de succès de niveau A et AA des Règles pour l’accessibilité des contenus Web (WCAG) 2.1 (anglais seulement).Développement
Ressources d'accessibilité numérique pour les fonctionnairesRessources d'accessibilité numérique pour les fonctionnaires, par les fonctionnaires.Apprentissage
Cours d'accessibilitéCours, webinaires, vidéos éducatives, et plus encore, proposés en accessibilité web.Apprentissage
Soutien d'accessibilité (en anglais seulement)Vérifier si votre code fonctionnera avec les technologies d'assistance.Développement

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/liste-de-verification-de-l-accessibilite-des-documents-pdf/index.html b/fr/liste-de-verification-de-l-accessibilite-des-documents-pdf/index.html index 7f7066054..6fe8d565d 100644 --- a/fr/liste-de-verification-de-l-accessibilite-des-documents-pdf/index.html +++ b/fr/liste-de-verification-de-l-accessibilite-des-documents-pdf/index.html @@ -1,4 +1,4 @@ -Liste de vérification de l’accessibilité des documents PDF - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Liste de vérification de l’accessibilité des documents PDF

Vous trouverez ici différentes questions pour vous aider à savoir si votre document pdf est accessible ou non.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

Liste de vérification de l’accessibilité des documents PDF ( PDF, 355 KB)

Introduction

La liste de vérification de l’accessibilité des documents PDF vise à aider les développeurs de documents PDF d’Emploi et Développement social Canada (EDSC) à s’assurer que l’accessibilité est conforme aux normes Règles pour l’accessibilité des contenus Web 2.1. Veuillez noter que la liste de vérification ne contient que des critères WCAG liés aux erreurs les plus courantes relevées dans les documents PDF.

Nous avons dressé une liste d’outils et de ressources pour aider les développeurs à vérifier l’accessibilité de leurs documents, ainsi que la liste de vérification de l’accessibilité des documents PDF qui établit 27 critères de réussite pertinents pour les documents PDF.

Outils et ressources

-Foxit PhantomPDF Lien interne : Outil recommandé par EDSC pour créer des documents PDF accessibles. Les employés d’EDSC peuvent obtenir le logiciel en remplissant le formulaire Formulaire de demande d’affaires Foxit PDF Editor Lien interne et en ouvrant un billet auprès d’InfoService national Lien interne. -Outil Colour Contrast Analyzer Lien interne : Outil recommandé par EDSC pour vérifier le contraste des couleurs; les employés d’EDSC peuvent obtenir le logiciel en ouvrant un billet auprès d’InfoService national Lien interne.

Ressources permettant de rendre les documents PDF accessibles

Instructions pour la liste de vérification

Veuillez remplir la liste de vérification de l’accessibilité des documents PDF. Cela permet de s’assurer que les erreurs courantes en matière d’accessibilité sont corrigées.

Veuillez noter que les employés d’EDSC devront remplir cette liste de vérification avant de demander une vérification de l’accessibilité au Bureau de l’accessibilité des TI.

Information de contact

Pour toute autre question ou commentaire concernant la liste de vérification de l’accessibilité des documents PDF, ou pour demander une vérification de l’accessibilité, veuillez remplir un nouveau formulaire de demande.

Liste de vérification

Glossaire

Texte alternatif :
Texte associé à une image qui transmet la même information essentielle que l’image.
La technologie d’assistance :
Tout outil ou appareil léger, moyen ou de haute technologie qui aide les personnes handicapées à accomplir leurs tâches avec plus de facilité ou d’autonomie.
Signet :
Type de lien avec un texte représentatif qui facilite la navigation dans les documents.
Texte descriptif :
Texte qui décrit le contenu d’un champ de formulaire à un utilisateur du lecteur d’écran. Il s’agit également d’une « étiquette ».
Ordre de lecture :
Ceci est l’ordre dans lequel les technologies d’assistance, comme les lecteurs d’écran, présentent le contenu en format PDF. Les étiquettes dans l’arborescence des étiquettes déterminent cet ordre.
En-têtes et pieds de page fixes :
Information répétée au haut ou au bas des pages d’un document. Ils contiennent souvent des renseignements comme le numéro de page, le nom du document, etc.
Lecteur d’écran :
Logiciel utilisé pour permettre la lecture du contenu et la navigation à l’écran à l’aide d’une sortie vocale ou en braille. Utilisé principalement par les personnes aveugles ou malvoyantes.
Balises :
Représentation textuelle structurée du contenu PDF auquel ont accès les lecteurs d’écran pour lire le document à haute voix.

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Liste de vérification de l’accessibilité des documents PDF

Vous trouverez ici différentes questions pour vous aider à savoir si votre document pdf est accessible ou non.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

Liste de vérification de l’accessibilité des documents PDF ( PDF, 355 KB)

Introduction

La liste de vérification de l’accessibilité des documents PDF vise à aider les développeurs de documents PDF d’Emploi et Développement social Canada (EDSC) à s’assurer que l’accessibilité est conforme aux normes Règles pour l’accessibilité des contenus Web 2.1. Veuillez noter que la liste de vérification ne contient que des critères WCAG liés aux erreurs les plus courantes relevées dans les documents PDF.

Nous avons dressé une liste d’outils et de ressources pour aider les développeurs à vérifier l’accessibilité de leurs documents, ainsi que la liste de vérification de l’accessibilité des documents PDF qui établit 27 critères de réussite pertinents pour les documents PDF.

Outils et ressources

-Foxit PhantomPDF Lien interne : Outil recommandé par EDSC pour créer des documents PDF accessibles. Les employés d’EDSC peuvent obtenir le logiciel en remplissant le formulaire Formulaire de demande d’affaires Foxit PDF Editor Lien interne et en ouvrant un billet auprès d’InfoService national Lien interne. -Outil Colour Contrast Analyzer Lien interne : Outil recommandé par EDSC pour vérifier le contraste des couleurs; les employés d’EDSC peuvent obtenir le logiciel en ouvrant un billet auprès d’InfoService national Lien interne.

Ressources permettant de rendre les documents PDF accessibles

Instructions pour la liste de vérification

Veuillez remplir la liste de vérification de l’accessibilité des documents PDF. Cela permet de s’assurer que les erreurs courantes en matière d’accessibilité sont corrigées.

Veuillez noter que les employés d’EDSC devront remplir cette liste de vérification avant de demander une vérification de l’accessibilité au Bureau de l’accessibilité des TI.

Information de contact

Pour toute autre question ou commentaire concernant la liste de vérification de l’accessibilité des documents PDF, ou pour demander une vérification de l’accessibilité, veuillez remplir un nouveau formulaire de demande.

Liste de vérification

Glossaire

Texte alternatif :
Texte associé à une image qui transmet la même information essentielle que l’image.
La technologie d’assistance :
Tout outil ou appareil léger, moyen ou de haute technologie qui aide les personnes handicapées à accomplir leurs tâches avec plus de facilité ou d’autonomie.
Signet :
Type de lien avec un texte représentatif qui facilite la navigation dans les documents.
Texte descriptif :
Texte qui décrit le contenu d’un champ de formulaire à un utilisateur du lecteur d’écran. Il s’agit également d’une « étiquette ».
Ordre de lecture :
Ceci est l’ordre dans lequel les technologies d’assistance, comme les lecteurs d’écran, présentent le contenu en format PDF. Les étiquettes dans l’arborescence des étiquettes déterminent cet ordre.
En-têtes et pieds de page fixes :
Information répétée au haut ou au bas des pages d’un document. Ils contiennent souvent des renseignements comme le numéro de page, le nom du document, etc.
Lecteur d’écran :
Logiciel utilisé pour permettre la lecture du contenu et la navigation à l’écran à l’aide d’une sortie vocale ou en braille. Utilisé principalement par les personnes aveugles ou malvoyantes.
Balises :
Représentation textuelle structurée du contenu PDF auquel ont accès les lecteurs d’écran pour lire le document à haute voix.

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/liste-de-verification-de-la-conformite-des-documents-microsoft/index.html b/fr/liste-de-verification-de-la-conformite-des-documents-microsoft/index.html index e8fdfbc0a..aa8086587 100644 --- a/fr/liste-de-verification-de-la-conformite-des-documents-microsoft/index.html +++ b/fr/liste-de-verification-de-la-conformite-des-documents-microsoft/index.html @@ -1,4 +1,4 @@ -Liste de vérification de la conformité des documents Microsoft - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Liste de vérification de la conformité des documents Microsoft

Vous trouverez ici différentes questions qui vous aideront à savoir si votre document Word est accessible ou non.

Liste de vérification de la conformité des documents Microsoft ( Word, 62 ko)

Vous trouverez ci-dessous des questions qui vous indiqueront si votre document Microsoft Office est accessible. Les critères de réussite renvoient aux Règles pour l’accessibilité des contenus Web (WCAG) 2.1 : How to Meet WCAG - Quick Reference (en anglais seulement) et le Guide de rédaction du contenu du site Canada.ca.

Si une question ne s’applique pas à votre document, indiquez « S.O. » pour « Sans objet ». Par exemple, il n’y a pas de table des matières dans un document Excel.

Si vous répondez « Non » à l’une des questions suivantes, votre document N’EST PAS accessible.

A. Renseignements d’ordre général

B. Couleur

C. Liens

D. Images

E. Tableaux

F. Listes

G. En-têtes

H. Autres éléments

Ressources

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Liste de vérification de la conformité des documents Microsoft

Vous trouverez ici différentes questions qui vous aideront à savoir si votre document Word est accessible ou non.

Liste de vérification de la conformité des documents Microsoft ( Word, 62 ko)

Vous trouverez ci-dessous des questions qui vous indiqueront si votre document Microsoft Office est accessible. Les critères de réussite renvoient aux Règles pour l’accessibilité des contenus Web (WCAG) 2.1 : How to Meet WCAG - Quick Reference (en anglais seulement) et le Guide de rédaction du contenu du site Canada.ca.

Si une question ne s’applique pas à votre document, indiquez « S.O. » pour « Sans objet ». Par exemple, il n’y a pas de table des matières dans un document Excel.

Si vous répondez « Non » à l’une des questions suivantes, votre document N’EST PAS accessible.

A. Renseignements d’ordre général

B. Couleur

C. Liens

D. Images

E. Tableaux

F. Listes

G. En-têtes

H. Autres éléments

Ressources

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/liste-des-pages-tableau/index.html b/fr/liste-des-pages-tableau/index.html index e9316cfd3..c0fa1373c 100644 --- a/fr/liste-des-pages-tableau/index.html +++ b/fr/liste-des-pages-tableau/index.html @@ -9,4 +9,4 @@ w.gtag('js', new Date()); w.gtag('config', 'G-SM9MSHWDVN'); } - })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Liste des pages tableau

Liste de toutes les pages du site Web du Boîte à outils de l'accessibilité numérique.

Définitions des étiquettes

Définitions des étiquettes

Sujets

accessibilityFundamentals
Principes de base de l’accessibilité
howTos
Comment faire
resourcesAndTools
Ressources et outils
learningAndDevelopment
Apprentissage et perfectionnement
accessibilityInTheGovernmentOfCanada
Accessibilité numérique au gouvernement du Canada
aboutUs
À propos de nous

Thèmes

aboutDisabilities
Types de handicap les plus courants
globalAccessibilityStandards
Normes d’accessibilité mondiales
createDocument
Créer un document
createEmails
Créer un courriel
createForms
Créer un formulaire
createWebContent
Créer du contenu Web
designCourse
Concevoir un cours
designingAccessible
Principes de conception pour des services accessibles
accessibleVirtualEvents
Événements virtuels accessibles
testYourProducts
Testez vos produits
accessibilityAct
Loi sur l’accessibilité
procurement
Approvisionnement
accessibilityStandards
Normes d’accessibilité
communityDirectory
Répertoire de la communauté
aboutTheDigitalTheAccessibilityToolkitProject
À propos du projet
contactUs
Contactez-nous
accessibilityInYourRole
L'accessibilité dans votre rôle
mainAbout
Section à propos de nous sur la page d'accueil
office2016
Comment créer des documents accessibles dans Office 2016
microsoft365
Comment créer des documents accessibles dans Microsoft 365
Visible columns
TitreLien vers d'autres languesThèmesSujetsLien vers le fichier
Comment créer des documents accessibles dans Microsoft 365Version anglaise de Comment créer des documents accessibles dans Microsoft 365createDocumenthowTos/src/main/fr/comment-faire/microsoft-office/comment-creer-des-documents-accessibles-dans-microsoft-365.njk
Comment créer des documents accessibles dans Office 2016Version anglaise de Comment créer des documents accessibles dans Office 2016createDocumenthowTos/src/main/fr/comment-faire/microsoft-office/comment-creer-des-documents-accessibles-dans-office-2016.njk
Diffusions en directVersion anglaise de Diffusions en directcreateWebContenthowTos/src/pages/fr/diffusions-en-direct.md
Directives pour la transcriptionVersion anglaise de Directives pour la transcriptioncreateWebContenthowTos/src/pages/fr/directives-pour-la-transcription.md
EnregistrementsVersion anglaise de EnregistrementscreateWebContenthowTos/src/pages/fr/enregistrements.md
Introduction aux exigences d’accessibilité pour l’audio-vidéoVersion anglaise de Introduction aux exigences d’accessibilité pour l’audio-vidéocreateWebContenthowTos/src/pages/fr/introduction-aux-exigences-d-accessibilite-pour-l-audio-video.md
Langue du contenu audio/vidéoVersion anglaise de Langue du contenu audio/vidéocreateWebContenthowTos/src/pages/fr/langue-du-contenu-audio-video.md
Le Groupe de travail sur l'accès (GTA)Version anglaise de Le Groupe de travail sur l'accès (GTA)/src/pages/fr/le-groupe-de-travail-sur-l-acces-gta.md
Liste de contrôle des transcriptionsVersion anglaise de Liste de contrôle des transcriptionscreateWebContenthowTos/src/pages/fr/liste-de-controle-des-transcriptions.md
Liste de contrôle pour le sous-titrageVersion anglaise de Liste de contrôle pour le sous-titragecreateWebContenthowTos/src/pages/fr/liste-de-controle-pour-le-sous-titrage.md
Plateformes de réunions virtuelles et fonctionnalitésVersion anglaise de Plateformes de réunions virtuelles et fonctionnalités/src/pages/fr/plateformes-de-reunions-virtuelles-et-fonctionnalites.md
Rapport sur ce que nous avons entendu : Norme d’accessibilité des technologies de l’information et des communications (NATIC)Version anglaise de Rapport sur ce que nous avons entendu : Norme d’accessibilité des technologies de l’information et des communications (NATIC)accessibilityStandardsaccessibilityInTheGovernmentOfCanada/src/pages/fr/rapport-sur-ce-que-nous-avons-entendu-norme-d-accessibilite-des-technologies-de-l-information-et-des-communications-natic.md
Statistique Canada (StatCan)Version anglaise de Statistique Canada (StatCan)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/fr/statistique-canada-statcan.md
Séance de mobilisation ciblée : L’ébauche de la Norme d’accessibilité des technologies de l’information et des communications (TIC)Version anglaise de Séance de mobilisation ciblée : L’ébauche de la Norme d’accessibilité des technologies de l’information et des communications (TIC)accessibilityStandardsaccessibilityInTheGovernmentOfCanada/src/pages/fr/seance-de-mobilisation-ciblee-l-ebauche-de-la-norme-d-accessibilite-des-technologies-de-l-information-et-des-communications-tic.md
Apprentissage et perfectionnementVersion anglaise de Apprentissage et perfectionnementmain updatesMain/src/pages/fr/apprentissage-et-perfectionnement.md
Boîte à outils de l'accessibilité numériqueVersion anglaise de Boîte à outils de l'accessibilité numérique/src/main/fr/index.njk
Déficiences auditivesVersion anglaise de Déficiences auditivesaboutDisabilitiesaccessibilityFundamentals/src/pages/fr/deficiences-auditives.md
Déficiences visuellesVersion anglaise de Déficiences visuellesaboutDisabilitiesaccessibilityFundamentals/src/pages/fr/deficiences-visuelles.md
Emploi et Développement social Canada (EDSC)Version anglaise de Emploi et Développement social Canada (EDSC)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/fr/emploi-et-developpement-social-canada-edsc.md
Handicaps de mobilité, de flexibilité et de structure corporelleVersion anglaise de Handicaps de mobilité, de flexibilité et de structure corporelleaboutDisabilitiesaccessibilityFundamentals/src/pages/fr/handicaps-de-mobilite-de-flexibilite-et-de-structure-corporelle.md
Mise en correspondance entre l’article 508 révisé (Revised Section 508) et la norme EN 301 549 (2014, 2018, 2019 et 2021)Version anglaise de Mise en correspondance entre l’article 508 révisé (Revised Section 508) et la norme EN 301 549 (2014, 2018, 2019 et 2021)procurementaccessibilityInTheGovernmentOfCanada/src/pages/fr/mise-en-correspondance-entre-l-article-508-revise-revised-section-508-et-la-norme-en-301-549-2014-2018-2019-et-2021.md
Ressources additionnelles sur les réunions et événements accessiblesVersion anglaise de Ressources additionnelles sur les réunions et événements accessibles/src/pages/fr/ressources-additionnelles-sur-les-reunions-et-evenements-accessibles.md
Services CART et interprètes en langue des signes (SLI)Version anglaise de Services CART et interprètes en langue des signes (SLI)accessibleVirtualEventshowTos/src/pages/fr/services-cart-et-interpretes-en-langue-des-signes-sli.md
Améliorer l’accessibilité des formulairesVersion anglaise de Améliorer l’accessibilité des formulairescreateFormshowTos/src/pages/fr/ameliorer-l-accessibilite-des-formulaires.md
Bonnes pratiques pour les événements virtuels accessiblesVersion anglaise de Bonnes pratiques pour les événements virtuels accessiblesaccessibleVirtualEvents updatesMainhowTos/src/pages/fr/bonnes-pratiques-pour-les-evenements-virtuels-accessibles.md
Classeurs Excel accessibles dans Microsoft 365Version anglaise de Classeurs Excel accessibles dans Microsoft 365createDocument microsoft365howTos/src/pages/fr/ms-office/365/classeurs-excel-accessibles-dans-microsoft-365.md
Classeurs Excel accessibles dans Office 2016Version anglaise de Classeurs Excel accessibles dans Office 2016createDocument office2016howTos/src/pages/fr/ms-office/2016/classeurs-excel-accessibles-dans-office-2016.md
Conception universelle pour l’apprentissage (CUA)Version anglaise de Conception universelle pour l’apprentissage (CUA)designCoursehowTos/src/pages/fr/conception-universelle-pour-l-apprentissage-cua.md
Concevoir des images accessiblesVersion anglaise de Concevoir des images accessibles/src/pages/fr/concevoir-des-images-accessibles.md
Concevoir pour les utilisateurs avec un handicap physique ou moteurVersion anglaise de Concevoir pour les utilisateurs avec un handicap physique ou moteurdesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/concevoir-pour-les-utilisateurs-avec-un-handicap-physique-ou-moteur.md
Concevoir pour les utilisateurs dans le spectre de l'autismeVersion anglaise de Concevoir pour les utilisateurs dans le spectre de l'autismedesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/concevoir-pour-les-utilisateurs-dans-le-spectre-de-l-autisme.md
Concevoir pour les utilisateurs de revues d’écranVersion anglaise de Concevoir pour les utilisateurs de revues d’écrandesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/concevoir-pour-les-utilisateurs-de-revues-d-ecran.md
Concevoir pour les utilisateurs malvoyantsVersion anglaise de Concevoir pour les utilisateurs malvoyantsdesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/concevoir-pour-les-utilisateurs-malvoyants.md
Concevoir pour les utilisateurs sourds ou malentendantsVersion anglaise de Concevoir pour les utilisateurs sourds ou malentendantsdesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/concevoir-pour-les-utilisateurs-sourds-ou-malentendants.md
Conseils pour la conception de cours en ligneVersion anglaise de Conseils pour la conception de cours en lignedesignCoursehowTos/src/pages/fr/conseils-pour-la-conception-de-cours-en-ligne.md
Contactez-nousVersion anglaise de Contactez-nousaboutUs/src/pages/fr/contactez-nous.md
Dessins Visio accessibles dans Microsoft 365Version anglaise de Dessins Visio accessibles dans Microsoft 365createDocument microsoft365howTos/src/pages/fr/ms-office/365/dessins-visio-accessibles-dans-microsoft-365.md
Dessins Visio accessibles dans Office 2016Version anglaise de Dessins Visio accessibles dans Office 2016createDocument office2016howTos/src/pages/fr/ms-office/2016/dessins-visio-accessibles-dans-office-2016.md
Directives pour la description sonoreVersion anglaise de Directives pour la description sonorecreateWebContenthowTos/src/pages/fr/directives-pour-la-description-sonore.md
Documents PDF accessibles dans Microsoft 365Version anglaise de Documents PDF accessibles dans Microsoft 365createDocument microsoft365howTos/src/pages/fr/ms-office/365/documents-pdf-accessibles-dans-microsoft-365.md
Documents PDF accessibles dans Office 2016Version anglaise de Documents PDF accessibles dans Office 2016createDocument office2016howTos/src/pages/fr/ms-office/2016/documents-pdf-accessibles-dans-office-2016.md
Documents Word accessibles dans Microsoft 365Version anglaise de Documents Word accessibles dans Microsoft 365createDocument microsoft365howTos/src/pages/fr/ms-office/365/documents-word-accessibles-dans-microsoft-365.md
Documents Word accessibles dans Office 2016Version anglaise de Documents Word accessibles dans Office 2016createDocument office2016howTos/src/pages/fr/ms-office/2016/documents-word-accessibles-dans-office-2016.md
Handicaps cognitifsVersion anglaise de Handicaps cognitifsaboutDisabilitiesaccessibilityFundamentals/src/pages/fr/handicaps-cognitifs.md
La structure des règles pour l'accessibilité des contenus web (WCAG) 2.1Version anglaise de La structure des règles pour l'accessibilité des contenus web (WCAG) 2.1/src/pages/fr/la-structure-des-regles-pour-l-accessibilite-des-contenus-web-wcag-2-1.md
Liens utilesVersion anglaise de Liens utiles/src/pages/fr/liens-utiles.md
Liste de vérification de la conformité des documents MicrosoftVersion anglaise de Liste de vérification de la conformité des documents MicrosoftcreateDocumenthowTos/src/pages/fr/liste-de-verification-de-la-conformite-des-documents-microsoft.md
Liste de vérification de l’accessibilité des documents PDFVersion anglaise de Liste de vérification de l’accessibilité des documents PDFcreateDocumenthowTos/src/pages/fr/liste-de-verification-de-l-accessibilite-des-documents-pdf.md
Liste de vérification pour l'accessibilité WebVersion anglaise de Liste de vérification pour l'accessibilité WebtestYourProductshowTos/src/pages/fr/liste-de-verification-pour-l-accessibilite-web.md
MandatsVersion anglaise de MandatsaboutUs/src/pages/fr/mandats.md
Normes d’accessibilité mondialesVersion anglaise de Normes d’accessibilité mondialesaccessibilityFundamentals/src/main/fr/principes-de-base-de-laccessibilite/normes-daccessibilite-mondiales.njk
Personas handicapés pour la conception d'une expérience utilisateur inclusive (EU)Version anglaise de Personas handicapés pour la conception d'une expérience utilisateur inclusive (EU)designCoursehowTos/src/pages/fr/personas-handicapes-pour-la-conception-d-une-experience-utilisateur-inclusive-eu.md
Principes de conception pour des services accessiblesVersion anglaise de Principes de conception pour des services accessibleshowTos/src/main/fr/comment-faire/principes-de-conception-pour-des-services-accessibles.njk
Principes de conception pour les utilisateurs avec handicap cognitifVersion anglaise de Principes de conception pour les utilisateurs avec handicap cognitifdesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/principes-de-conception-pour-les-utilisateurs-avec-handicap-cognitif.md
Projet de la Boîte à outils de l'accessibilité numériqueVersion anglaise de Projet de la Boîte à outils de l'accessibilité numériqueaboutUs/src/pages/fr/projet-de-la-boite-a-outils-de-l-accessibilite-numerique.md
Présentations PowerPoint accessibles dans Microsoft 365Version anglaise de Présentations PowerPoint accessibles dans Microsoft 365createDocument microsoft365howTos/src/pages/fr/ms-office/365/presentations-powerpoint-accessibles-dans-microsoft-365.md
Présentations PowerPoint accessibles dans Office 2016Version anglaise de Présentations PowerPoint accessibles dans Office 2016createDocument office2016howTos/src/pages/fr/ms-office/2016/presentations-powerpoint-accessibles-dans-office-2016.md
Recherche sur notre audienceVersion anglaise de Recherche sur notre audienceaboutUs/src/pages/fr/recherche-sur-notre-audience.md
Rendre vos courriel accessiblesVersion anglaise de Rendre vos courriel accessibleshowTos updatesMain/src/pages/fr/rendre-vos-courriel-accessibles.md
Test d’accessibilité 101Version anglaise de Test d’accessibilité 101testYourProductshowTos/src/pages/fr/test-d-accessibilite-101.md
Texte alternatif et description longue - Bonnes pratiquesVersion anglaise de Texte alternatif et description longue - Bonnes pratiquescreateWebContenthowTos/src/pages/fr/texte-alternatif-et-description-longue-bonnes-pratiques.md
À faire et à ne pas faire pour développer des cours en ligneVersion anglaise de À faire et à ne pas faire pour développer des cours en lignedesignCoursehowTos/src/pages/fr/a-faire-et-a-ne-pas-faire-pour-developper-des-cours-en-ligne.md
Accessibilité numérique au gouvernement du CanadaVersion anglaise de Accessibilité numérique au gouvernement du Canadamain/src/main/fr/accessibilite-au-gouvernement-du-canada/index.njk
ApprovisionnementVersion anglaise de ApprovisionnementaccessibilityInTheGovernmentOfCanada/src/main/fr/accessibilite-au-gouvernement-du-canada/approvisionnement.njk
Comment faireVersion anglaise de Comment fairemain/src/main/fr/comment-faire/index.njk
Concevoir un coursVersion anglaise de Concevoir un courshowTos/src/main/fr/comment-faire/concevoir-un-cours.njk
Créer du contenu WebVersion anglaise de Créer du contenu WebhowTos/src/main/fr/comment-faire/creer-du-contenu-web.njk
Créer un documentVersion anglaise de Créer un documenthowTos/src/main/fr/comment-faire/creer-un-document.njk
Créer un formulaireVersion anglaise de Créer un formulairehowTos/src/main/fr/comment-faire/creer-un-formulaire.njk
Exigences en matière de technologies de l’information et des communications (TIC) accessiblesVersion anglaise de Exigences en matière de technologies de l’information et des communications (TIC) accessiblesprocurementaccessibilityInTheGovernmentOfCanada/src/pages/fr/exigences-en-matiere-de-technologies-de-l-information-et-des-communications-tic-accessibles.md
L'accessibilité dans votre rôleVersion anglaise de L'accessibilité dans votre rôle/src/main/fr/l-accessibilite-dans-votre-role.njk
Normes d'accessibilitéVersion anglaise de Normes d'accessibilitéaccessibilityInTheGovernmentOfCanada/src/main/fr/accessibilite-au-gouvernement-du-canada/normes-d-accessibilite.njk
OutilsVersion anglaise de Outils/src/main/fr/ressources-et-outils/outils.njk
Principes de base de l’accessibilitéVersion anglaise de Principes de base de l’accessibilitémain/src/main/fr/principes-de-base-de-laccessibilite/index.njk
RessourcesVersion anglaise de Ressources/src/main/fr/ressources-et-outils/ressources.njk
Ressources additionnellesVersion anglaise de Ressources additionnellesresourcesAndTools/src/pages/fr/ressources-additionnelles.md
Ressources et outilsVersion anglaise de Ressources et outilsmain/src/main/fr/ressources-et-outils/index.njk
Répertoire de la communautéVersion anglaise de Répertoire de la communautéaccessibilityInTheGovernmentOfCanada/src/main/fr/accessibilite-au-gouvernement-du-canada/repertoire-de-la-communaute.njk
Résumé technique de la norme EN 301 549 v3.2.1 (2021)Version anglaise de Résumé technique de la norme EN 301 549 v3.2.1 (2021)procurementaccessibilityInTheGovernmentOfCanada/src/pages/fr/resume-technique-de-la-norme-en-301-549-v3-2-1-2021.md
Testez vos produitsVersion anglaise de Testez vos produitshowTos updatesMain/src/main/fr/comment-faire/testez-vos-produits.njk
Types de handicap les plus courantsVersion anglaise de Types de handicap les plus courantsaccessibilityFundamentals/src/main/fr/principes-de-base-de-laccessibilite/types-de-handicap-les-plus-courants.njk
À propos de nousVersion anglaise de À propos de nous/src/main/fr/a-propos-de-nous/index.njk
École de la fonction publique du Canada (EFPC)Version anglaise de École de la fonction publique du Canada (EFPC)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/fr/ecole-de-la-fonction-publique-du-canada-efpc.md
Événements virtuels accessiblesVersion anglaise de Événements virtuels accessibleshowTos/src/main/fr/comment-faire/evenements-virtuels-accessibles.njk

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Liste des pages tableau

Liste de toutes les pages du site Web du Boîte à outils de l'accessibilité numérique.

Définitions des étiquettes

Définitions des étiquettes

Sujets

accessibilityFundamentals
Principes de base de l’accessibilité
howTos
Comment faire
resourcesAndTools
Ressources et outils
learningAndDevelopment
Apprentissage et perfectionnement
accessibilityInTheGovernmentOfCanada
Accessibilité numérique au gouvernement du Canada
aboutUs
À propos de nous

Thèmes

aboutDisabilities
Types de handicap les plus courants
globalAccessibilityStandards
Normes d’accessibilité mondiales
createDocument
Créer un document
createEmails
Créer un courriel
createForms
Créer un formulaire
createWebContent
Créer du contenu Web
designCourse
Concevoir un cours
designingAccessible
Principes de conception pour des services accessibles
accessibleVirtualEvents
Événements virtuels accessibles
testYourProducts
Testez vos produits
accessibilityAct
Loi sur l’accessibilité
procurement
Approvisionnement
accessibilityStandards
Normes d’accessibilité
communityDirectory
Répertoire de la communauté
aboutTheDigitalTheAccessibilityToolkitProject
À propos du projet
contactUs
Contactez-nous
accessibilityInYourRole
L'accessibilité dans votre rôle
mainAbout
Section à propos de nous sur la page d'accueil
office2016
Comment créer des documents accessibles dans Office 2016
microsoft365
Comment créer des documents accessibles dans Microsoft 365
Visible columns
TitreLien vers d'autres languesThèmesSujetsLien vers le fichier
Comment créer des documents accessibles dans Microsoft 365Version anglaise de Comment créer des documents accessibles dans Microsoft 365createDocumenthowTos/src/main/fr/comment-faire/microsoft-office/comment-creer-des-documents-accessibles-dans-microsoft-365.njk
Comment créer des documents accessibles dans Office 2016Version anglaise de Comment créer des documents accessibles dans Office 2016createDocumenthowTos/src/main/fr/comment-faire/microsoft-office/comment-creer-des-documents-accessibles-dans-office-2016.njk
Diffusions en directVersion anglaise de Diffusions en directcreateWebContenthowTos/src/pages/fr/diffusions-en-direct.md
Directives pour la transcriptionVersion anglaise de Directives pour la transcriptioncreateWebContenthowTos/src/pages/fr/directives-pour-la-transcription.md
EnregistrementsVersion anglaise de EnregistrementscreateWebContenthowTos/src/pages/fr/enregistrements.md
Langue du contenu audio/vidéoVersion anglaise de Langue du contenu audio/vidéocreateWebContenthowTos/src/pages/fr/langue-du-contenu-audio-video.md
Liste de contrôle des transcriptionsVersion anglaise de Liste de contrôle des transcriptionscreateWebContenthowTos/src/pages/fr/liste-de-controle-des-transcriptions.md
Liste de contrôle pour le sous-titrageVersion anglaise de Liste de contrôle pour le sous-titragecreateWebContenthowTos/src/pages/fr/liste-de-controle-pour-le-sous-titrage.md
Rapport sur ce que nous avons entendu : Norme d’accessibilité des technologies de l’information et des communications (NATIC)Version anglaise de Rapport sur ce que nous avons entendu : Norme d’accessibilité des technologies de l’information et des communications (NATIC)accessibilityStandardsaccessibilityInTheGovernmentOfCanada/src/pages/fr/rapport-sur-ce-que-nous-avons-entendu-norme-d-accessibilite-des-technologies-de-l-information-et-des-communications-natic.md
Séance de mobilisation ciblée : L’ébauche de la Norme d’accessibilité des technologies de l’information et des communications (TIC)Version anglaise de Séance de mobilisation ciblée : L’ébauche de la Norme d’accessibilité des technologies de l’information et des communications (TIC)accessibilityStandardsaccessibilityInTheGovernmentOfCanada/src/pages/fr/seance-de-mobilisation-ciblee-l-ebauche-de-la-norme-d-accessibilite-des-technologies-de-l-information-et-des-communications-tic.md
Apprentissage et perfectionnementVersion anglaise de Apprentissage et perfectionnementmain updatesMain/src/pages/fr/apprentissage-et-perfectionnement.md
Boîte à outils de l'accessibilité numériqueVersion anglaise de Boîte à outils de l'accessibilité numérique/src/main/fr/index.njk
Handicaps de mobilité, de flexibilité et de structure corporelleVersion anglaise de Handicaps de mobilité, de flexibilité et de structure corporelleaboutDisabilitiesaccessibilityFundamentals/src/pages/fr/handicaps-de-mobilite-de-flexibilite-et-de-structure-corporelle.md
Normes d’accessibilité mondialesVersion anglaise de Normes d’accessibilité mondialesaccessibilityFundamentals/src/main/fr/principes-de-base-de-laccessibilite/normes-daccessibilite-mondiales.njk
Principes de conception pour des services accessiblesVersion anglaise de Principes de conception pour des services accessibleshowTos/src/main/fr/comment-faire/principes-de-conception-pour-des-services-accessibles.njk
Améliorer l’accessibilité des formulairesVersion anglaise de Améliorer l’accessibilité des formulairescreateFormshowTos/src/pages/fr/ameliorer-l-accessibilite-des-formulaires.md
Classeurs Excel accessibles dans Microsoft 365Version anglaise de Classeurs Excel accessibles dans Microsoft 365createDocument microsoft365howTos/src/pages/fr/ms-office/365/classeurs-excel-accessibles-dans-microsoft-365.md
Classeurs Excel accessibles dans Office 2016Version anglaise de Classeurs Excel accessibles dans Office 2016createDocument office2016howTos/src/pages/fr/ms-office/2016/classeurs-excel-accessibles-dans-office-2016.md
Concevoir des images accessiblesVersion anglaise de Concevoir des images accessibles/src/pages/fr/concevoir-des-images-accessibles.md
Concevoir pour les utilisateurs avec un handicap physique ou moteurVersion anglaise de Concevoir pour les utilisateurs avec un handicap physique ou moteurdesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/concevoir-pour-les-utilisateurs-avec-un-handicap-physique-ou-moteur.md
Concevoir pour les utilisateurs dans le spectre de l'autismeVersion anglaise de Concevoir pour les utilisateurs dans le spectre de l'autismedesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/concevoir-pour-les-utilisateurs-dans-le-spectre-de-l-autisme.md
Concevoir pour les utilisateurs de revues d’écranVersion anglaise de Concevoir pour les utilisateurs de revues d’écrandesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/concevoir-pour-les-utilisateurs-de-revues-d-ecran.md
Concevoir pour les utilisateurs malvoyantsVersion anglaise de Concevoir pour les utilisateurs malvoyantsdesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/concevoir-pour-les-utilisateurs-malvoyants.md
Concevoir pour les utilisateurs sourds ou malentendantsVersion anglaise de Concevoir pour les utilisateurs sourds ou malentendantsdesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/concevoir-pour-les-utilisateurs-sourds-ou-malentendants.md
Conseils pour la conception de cours en ligneVersion anglaise de Conseils pour la conception de cours en lignedesignCoursehowTos/src/pages/fr/conseils-pour-la-conception-de-cours-en-ligne.md
Contactez-nousVersion anglaise de Contactez-nousaboutUs/src/pages/fr/contactez-nous.md
Dessins Visio accessibles dans Microsoft 365Version anglaise de Dessins Visio accessibles dans Microsoft 365createDocument microsoft365howTos/src/pages/fr/ms-office/365/dessins-visio-accessibles-dans-microsoft-365.md
Dessins Visio accessibles dans Office 2016Version anglaise de Dessins Visio accessibles dans Office 2016createDocument office2016howTos/src/pages/fr/ms-office/2016/dessins-visio-accessibles-dans-office-2016.md
Documents PDF accessibles dans Microsoft 365Version anglaise de Documents PDF accessibles dans Microsoft 365createDocument microsoft365howTos/src/pages/fr/ms-office/365/documents-pdf-accessibles-dans-microsoft-365.md
Documents PDF accessibles dans Office 2016Version anglaise de Documents PDF accessibles dans Office 2016createDocument office2016howTos/src/pages/fr/ms-office/2016/documents-pdf-accessibles-dans-office-2016.md
Documents Word accessibles dans Microsoft 365Version anglaise de Documents Word accessibles dans Microsoft 365createDocument microsoft365howTos/src/pages/fr/ms-office/365/documents-word-accessibles-dans-microsoft-365.md
Documents Word accessibles dans Office 2016Version anglaise de Documents Word accessibles dans Office 2016createDocument office2016howTos/src/pages/fr/ms-office/2016/documents-word-accessibles-dans-office-2016.md
Liste de vérification pour l'accessibilité WebVersion anglaise de Liste de vérification pour l'accessibilité WebtestYourProductshowTos/src/pages/fr/liste-de-verification-pour-l-accessibilite-web.md
MandatsVersion anglaise de MandatsaboutUs/src/pages/fr/mandats.md
Principes de conception pour les utilisateurs avec handicap cognitifVersion anglaise de Principes de conception pour les utilisateurs avec handicap cognitifdesigningAccessiblehowTos/src/pages/fr/principes-de-conception-pour-des-services-accessibles/principes-de-conception-pour-les-utilisateurs-avec-handicap-cognitif.md
Projet de la Boîte à outils de l'accessibilité numériqueVersion anglaise de Projet de la Boîte à outils de l'accessibilité numériqueaboutUs/src/pages/fr/projet-de-la-boite-a-outils-de-l-accessibilite-numerique.md
Présentations PowerPoint accessibles dans Microsoft 365Version anglaise de Présentations PowerPoint accessibles dans Microsoft 365createDocument microsoft365howTos/src/pages/fr/ms-office/365/presentations-powerpoint-accessibles-dans-microsoft-365.md
Présentations PowerPoint accessibles dans Office 2016Version anglaise de Présentations PowerPoint accessibles dans Office 2016createDocument office2016howTos/src/pages/fr/ms-office/2016/presentations-powerpoint-accessibles-dans-office-2016.md
À faire et à ne pas faire pour développer des cours en ligneVersion anglaise de À faire et à ne pas faire pour développer des cours en lignedesignCoursehowTos/src/pages/fr/a-faire-et-a-ne-pas-faire-pour-developper-des-cours-en-ligne.md
Accessibilité numérique au gouvernement du CanadaVersion anglaise de Accessibilité numérique au gouvernement du Canadamain/src/main/fr/accessibilite-au-gouvernement-du-canada/index.njk
ApprovisionnementVersion anglaise de ApprovisionnementaccessibilityInTheGovernmentOfCanada/src/main/fr/accessibilite-au-gouvernement-du-canada/approvisionnement.njk
Bonnes pratiques pour les événements virtuels accessiblesVersion anglaise de Bonnes pratiques pour les événements virtuels accessiblesaccessibleVirtualEvents updatesMainhowTos/src/pages/fr/bonnes-pratiques-pour-les-evenements-virtuels-accessibles.md
Comment faireVersion anglaise de Comment fairemain/src/main/fr/comment-faire/index.njk
Conception universelle pour l’apprentissage (CUA)Version anglaise de Conception universelle pour l’apprentissage (CUA)designCoursehowTos/src/pages/fr/conception-universelle-pour-l-apprentissage-cua.md
Concevoir un coursVersion anglaise de Concevoir un courshowTos/src/main/fr/comment-faire/concevoir-un-cours.njk
Créer du contenu WebVersion anglaise de Créer du contenu WebhowTos/src/main/fr/comment-faire/creer-du-contenu-web.njk
Créer un documentVersion anglaise de Créer un documenthowTos/src/main/fr/comment-faire/creer-un-document.njk
Créer un formulaireVersion anglaise de Créer un formulairehowTos/src/main/fr/comment-faire/creer-un-formulaire.njk
Directives pour la description sonoreVersion anglaise de Directives pour la description sonorecreateWebContenthowTos/src/pages/fr/directives-pour-la-description-sonore.md
Déficiences auditivesVersion anglaise de Déficiences auditivesaboutDisabilitiesaccessibilityFundamentals/src/pages/fr/deficiences-auditives.md
Déficiences visuellesVersion anglaise de Déficiences visuellesaboutDisabilitiesaccessibilityFundamentals/src/pages/fr/deficiences-visuelles.md
Emploi et Développement social Canada (EDSC)Version anglaise de Emploi et Développement social Canada (EDSC)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/fr/emploi-et-developpement-social-canada-edsc.md
Exigences en matière de technologies de l’information et des communications (TIC) accessiblesVersion anglaise de Exigences en matière de technologies de l’information et des communications (TIC) accessiblesprocurementaccessibilityInTheGovernmentOfCanada/src/pages/fr/exigences-en-matiere-de-technologies-de-l-information-et-des-communications-tic-accessibles.md
Handicaps cognitifsVersion anglaise de Handicaps cognitifsaboutDisabilitiesaccessibilityFundamentals/src/pages/fr/handicaps-cognitifs.md
Introduction aux exigences d’accessibilité pour l’audio-vidéoVersion anglaise de Introduction aux exigences d’accessibilité pour l’audio-vidéocreateWebContenthowTos/src/pages/fr/introduction-aux-exigences-d-accessibilite-pour-l-audio-video.md
L'accessibilité dans votre rôleVersion anglaise de L'accessibilité dans votre rôle/src/main/fr/l-accessibilite-dans-votre-role.njk
La structure des règles pour l'accessibilité des contenus web (WCAG) 2.1Version anglaise de La structure des règles pour l'accessibilité des contenus web (WCAG) 2.1/src/pages/fr/la-structure-des-regles-pour-l-accessibilite-des-contenus-web-wcag-2-1.md
Le Groupe de travail sur l'accès (GTA)Version anglaise de Le Groupe de travail sur l'accès (GTA)/src/pages/fr/le-groupe-de-travail-sur-l-acces-gta.md
Liens utilesVersion anglaise de Liens utiles/src/pages/fr/liens-utiles.md
Liste de vérification de la conformité des documents MicrosoftVersion anglaise de Liste de vérification de la conformité des documents MicrosoftcreateDocumenthowTos/src/pages/fr/liste-de-verification-de-la-conformite-des-documents-microsoft.md
Liste de vérification de l’accessibilité des documents PDFVersion anglaise de Liste de vérification de l’accessibilité des documents PDFcreateDocumenthowTos/src/pages/fr/liste-de-verification-de-l-accessibilite-des-documents-pdf.md
Mise en correspondance entre l’article 508 révisé (Revised Section 508) et la norme EN 301 549 (2014, 2018, 2019 et 2021)Version anglaise de Mise en correspondance entre l’article 508 révisé (Revised Section 508) et la norme EN 301 549 (2014, 2018, 2019 et 2021)procurementaccessibilityInTheGovernmentOfCanada/src/pages/fr/mise-en-correspondance-entre-l-article-508-revise-revised-section-508-et-la-norme-en-301-549-2014-2018-2019-et-2021.md
Normes d'accessibilitéVersion anglaise de Normes d'accessibilitéaccessibilityInTheGovernmentOfCanada/src/main/fr/accessibilite-au-gouvernement-du-canada/normes-d-accessibilite.njk
OutilsVersion anglaise de Outils/src/main/fr/ressources-et-outils/outils.njk
Personas handicapés pour la conception d'une expérience utilisateur inclusive (EU)Version anglaise de Personas handicapés pour la conception d'une expérience utilisateur inclusive (EU)designCoursehowTos/src/pages/fr/personas-handicapes-pour-la-conception-d-une-experience-utilisateur-inclusive-eu.md
Plateformes de réunions virtuelles et fonctionnalitésVersion anglaise de Plateformes de réunions virtuelles et fonctionnalités/src/pages/fr/plateformes-de-reunions-virtuelles-et-fonctionnalites.md
Principes de base de l’accessibilitéVersion anglaise de Principes de base de l’accessibilitémain/src/main/fr/principes-de-base-de-laccessibilite/index.njk
Recherche sur notre audienceVersion anglaise de Recherche sur notre audienceaboutUs/src/pages/fr/recherche-sur-notre-audience.md
Rendre vos courriel accessiblesVersion anglaise de Rendre vos courriel accessibleshowTos updatesMain/src/pages/fr/rendre-vos-courriel-accessibles.md
RessourcesVersion anglaise de Ressources/src/main/fr/ressources-et-outils/ressources.njk
Ressources additionnellesVersion anglaise de Ressources additionnellesresourcesAndTools/src/pages/fr/ressources-additionnelles.md
Ressources additionnelles sur les réunions et événements accessiblesVersion anglaise de Ressources additionnelles sur les réunions et événements accessibles/src/pages/fr/ressources-additionnelles-sur-les-reunions-et-evenements-accessibles.md
Ressources et outilsVersion anglaise de Ressources et outilsmain/src/main/fr/ressources-et-outils/index.njk
Répertoire de la communautéVersion anglaise de Répertoire de la communautéaccessibilityInTheGovernmentOfCanada/src/main/fr/accessibilite-au-gouvernement-du-canada/repertoire-de-la-communaute.njk
Résumé technique de la norme EN 301 549 v3.2.1 (2021)Version anglaise de Résumé technique de la norme EN 301 549 v3.2.1 (2021)procurementaccessibilityInTheGovernmentOfCanada/src/pages/fr/resume-technique-de-la-norme-en-301-549-v3-2-1-2021.md
Services CART et interprètes en langue des signes (SLI)Version anglaise de Services CART et interprètes en langue des signes (SLI)accessibleVirtualEventshowTos/src/pages/fr/services-cart-et-interpretes-en-langue-des-signes-sli.md
Statistique Canada (StatCan)Version anglaise de Statistique Canada (StatCan)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/fr/statistique-canada-statcan.md
Test d’accessibilité 101Version anglaise de Test d’accessibilité 101testYourProductshowTos/src/pages/fr/test-d-accessibilite-101.md
Testez vos produitsVersion anglaise de Testez vos produitshowTos updatesMain/src/main/fr/comment-faire/testez-vos-produits.njk
Texte alternatif et description longue - Bonnes pratiquesVersion anglaise de Texte alternatif et description longue - Bonnes pratiquescreateWebContenthowTos/src/pages/fr/texte-alternatif-et-description-longue-bonnes-pratiques.md
Types de handicap les plus courantsVersion anglaise de Types de handicap les plus courantsaccessibilityFundamentals/src/main/fr/principes-de-base-de-laccessibilite/types-de-handicap-les-plus-courants.njk
À propos de nousVersion anglaise de À propos de nous/src/main/fr/a-propos-de-nous/index.njk
École de la fonction publique du Canada (EFPC)Version anglaise de École de la fonction publique du Canada (EFPC)communityDirectoryaccessibilityInTheGovernmentOfCanada/src/pages/fr/ecole-de-la-fonction-publique-du-canada-efpc.md
Événements virtuels accessiblesVersion anglaise de Événements virtuels accessibleshowTos/src/main/fr/comment-faire/evenements-virtuels-accessibles.njk

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/mise-en-correspondance-entre-l-article-508-revise-revised-section-508-et-la-norme-en-301-549-2014-2018-2019-et-2021/index.html b/fr/mise-en-correspondance-entre-l-article-508-revise-revised-section-508-et-la-norme-en-301-549-2014-2018-2019-et-2021/index.html index 7117764dc..e775f6a24 100644 --- a/fr/mise-en-correspondance-entre-l-article-508-revise-revised-section-508-et-la-norme-en-301-549-2014-2018-2019-et-2021/index.html +++ b/fr/mise-en-correspondance-entre-l-article-508-revise-revised-section-508-et-la-norme-en-301-549-2014-2018-2019-et-2021/index.html @@ -1,4 +1,4 @@ -Mise en correspondance entre l’article 508 révisé (Revised Section 508) et la norme EN 301 549 (2014, 2018, 2019 et 2021) - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Mise en correspondance entre l’article 508 révisé (Revised Section 508) et la norme EN 301 549 (2014, 2018, 2019 et 2021)

Comme les normes EN 301 549 (en anglais seulement) continuent, d’évoluer et de publier des mises à jour, le présent document montre la progression des normes EN 301 549 depuis 2014, jusqu’aux mises à jour de 2018, 2019 et 2021. Ces renseignements sont importants, car le GC se dirige vers l’adoption de la norme EN 301 549 (2021)) comme norme d’accessibilité pour les TIC. Le GC, dans le cadre du processus d’invitation à soumissionner, peut demander aux fournisseurs de fournir des rapports de conformité en matière d’accessibilité basés sur le modèle d’accessibilité volontaire des produits Voluntary Product Accessibility Template - (VPAT). Chaque VPAT est fondé sur une norme technique précise – l’article 508 révisé, la norme EN 301 549 ou les Web Content Accessibility Guidelines (WCAG) (en anglais seulement). Les fournisseurs, les responsables techniques et les autorités contractantes doivent comprendre les différences entre ces normes pour s’assurer que les exigences d’accessibilité sont abordées comme il se doit.

Sur cette page

Avis de droit d’auteur

Ce document reproduit les exigences pertinentes en matière d’accessibilité des TIC du EN 301 549 norme européenne harmonisée « Exigences en accessibilité pour les produits et services en TIC », disponible en anglais seulement, (© utilisé sous la licence de l’Institut Européen de Normalisation des Télécommunications 2014, 2018, 2019 et 2021. © Comité Européen de Normalisation 2014, 2018, 2019 et 2021. © Comité Européen de Normalisation Électrotechnique 2014, 2018, 2019, 2021. Tous droits réservés.)

Avertissement

Ce document a été créé en février 2020 et mis à jour en octobre 2022 par le programme d’accessibilité, d’adaptation et de technologie informatique adaptée (AATIA) appartenant au ministère des Services partagés Canada (SPC). Au mieux de notre connaissance, il était exact en date d’octobre 2022. SPC ne garantit pas qu'une autorité compétente quelconque se fiera à ce travail. Si vous avez des questions au sujet de ce document, veuillez envoyer un courriel au programme d’AATIA.

Public visé

Le public visé comprend les responsables techniques et les autorités contractantes au sein de SPC et du gouvernement du Canada (GC), ainsi que les fournisseurs qui offrent des produits et des services de technologie de l’information et des communications (TIC).

Contexte

Ce document traite des normes techniques pour l’accessibilité des TIC. Les normes les plus courantes sont les Règles pour l’accessibilité des contenus Web (Web Content Accessibility Guidelines - WCAG), l’article 508 révisé (Revised Section 508) et la norme européenne harmonisée EN 301 549 pour l’accessibilité des TIC.

L'article 508 révisé (2017) fournit la norme technique permettant au gouvernement américain de s’approvisionner en produits et services accessibles. Cette norme est, à dessein, étroitement harmonisée avec la norme EN 301 549 (2014) - qui a tiré ses exigences en grande partie des normes de l’article 508 initial et des WCAG 2.0. Par conséquent, ces normes sont très similaires mais contiennent des différences essentielles. La norme EN 301 549 a été mise à jour quatre fois depuis la publication de l’article 508 révisé, ce qui a introduit d’autres différences entre les normes.

But

Le but du présent document est de cerner les similarités et les différences entre l’article 508 révisé et les normes EN 301 549.

Comme les normes EN 301 549 continuent d’évoluer et de publier des mises à jour, le présent document montre la progression des normes EN 301 549 depuis 2014, jusqu’aux mises à jour de 2018, 2019 et 2021. Ces renseignements sont importants, car le GC se dirige vers l’adoption de la norme EN 301 549 (2021)) comme norme d’accessibilité pour les TIC. Le GC, dans le cadre du processus d’invitation à soumissionner, peut demander aux fournisseurs de fournir des rapports de conformité en matière d’accessibilité basés sur le modèle d’accessibilité volontaire des produits (Voluntary Product Accessibility Template - VPAT). Chaque VPAT est fondé sur une norme technique précise – l’article 508 révisé, la norme EN 301 549 ou les WCAG. Les fournisseurs, les responsables techniques et les autorités contractantes doivent comprendre les différences entre ces normes pour s’assurer que les exigences d’accessibilité sont abordées comme il se doit.

Résumé des différences

Des WCAG à l’article révisé 508 / la norme EN 301 549

Les WCAG, bien qu’elles soient neutres sur le plan technologique, sont habituellement applicables aux sites Web et aux applications Web. Pour ces produits, spécifier WCAG 2.0 niveau AA ou 2.1 niveau AA comme norme technique peut être suffisant. Cependant, les autres normes comprennent des exigences supplémentaires qui peuvent s’appliquer aux applications Web qui fournissent l’une ou l’autre des caractéristiques suivantes : caractéristiques d’accessibilité documentées, outils-auteurs, communication bidirectionnelle, vidéo et conversion de l’information entre formats électroniques. Les autres normes comprennent également des exigences relatives au soutien et à la documentation, qui peuvent s’appliquer aux achats de sites Web ou d’applications Web.

Par l’intermédiaire du groupe de travail WCAG2ICT, les exigences des WCAG ont été adaptées pour répondre plus précisément aux exigences d’autres types de TIC, notamment les logiciels et les documents non Web. Ces adaptations ont été intégrées dans l’article 508 révisé et dans la norme EN 301 549, de sorte que la spécification de ces normes, plutôt que des WCAG, donnera lieu à des exigences d’accessibilité plus claires pour les produits de TIC non Web.

Bien que l’article 508 révisé et la norme EN 301 549 incluent les exigences à niveaux des WCAG, ces normes ont une portée plus large. Pour l’équipement de TIC et les services de TIC, les WCAG n’aborderont pas comme il se doit les exigences d’accessibilité. Si la fonctionnalité du produit ou du service risque de ne pas être entièrement abordée par les WCAG, les approvisionnements du GC devraient spécifier la norme EN 301 549.

De l’article 508 révisé à la norme EN 301 549 (2014)

Ces normes sont étroitement harmonisées. Certaines exigences varient pour ce qui est de la spécificité, la norme EN 301 549 adoptants habituellement une approche plus générale. Les exigences de l’article 508 révisé pourraient faire référence à des normes américaines précises, tandis que la norme EN 301 549 inclut les spécifications pertinentes dans le document ou fait référence à des normes internationales. Certaines exigences générales de l’article 508 révisé ne sont abordées que dans le chapitre sur les logiciels de la norme EN 301 549, de sorte qu’il puisse être nécessaire d’inclure les exigences relatives aux logiciels même pour les dispositifs matériels dotés d’écrans.

De la norme EN 301 549 (2014) à la norme EN 301 549 (2018)

Principalement, les chapitres se rapportant aux WCAG (9, 10 et 11) diffèrent entre ces versions, ainsi que plusieurs mises à jour explicatives, reformulations stylistiques, changements de numérotation et changements fonctionnels. La version 2014 inclut tous les critères de succès des WCAG 2.0 niveau A et AA, tandis que la version 2018 est mise à jour pour faire directement référence à tous les critères de succès des WCAG 2.1 niveau A et AA. (Bien que les versions 2018 et 2019 ne reproduisent pas le texte des WCAG, nous avons inclus les nouvelles exigences avec le texte dans ce document par souci de clarté). La numérotation des chapitres se rapportant aux WCAG dans la version 2018 suit directement les critères de succès des WCAG 2.1. Par exemple, la clause 9.2.3.1 de la norme EN 301 549 fait référence au critère de succès 2.3.1 des WCAG.

De la norme EN 301 549 (2018) à la norme EN 301 549 (2019)

La majorité des changements sont des reformulations stylistiques et des notes explicatives supplémentaires. Il y a 14 nouvelles exigences, portant principalement sur l’utilisation avec une audition limitée. Quelques exigences de la version 2018 ont été divisées ou regroupées. Les exigences relatives à l’accès physique aux TIC ont été retravaillées pour indiquer « 8.3 TIC fixes ». La numérotation est autrement cohérente entre les versions.

De la norme EN 301 549 (2019) à la norme EN 301 549 (2021)

Le document EN 301 549 V3.2.1 (2021) a été élaboré à partir de la norme EN 301 549 V2.1.2 (2018). Il n’y a pas de nouvelles exigences. Le tableau des modifications de suivi de l’annexe F a été ajouté pour les futures versions. Quelques clarifications à 7.1.1 concernant le sous-titrage, mais la numérotation est autrement cohérente entre les versions. La numérotation des chapitres 9, 10 et 11 relatifs aux WCAG dans la version 2021 suit directement les critères de succès des WCAG 2.1. Par exemple, la clause 9.2.3.1 de la norme EN 301 549 (2021) fait référence au critère de succès 2.3.1 des WCAG. Comme indiqué dans les notes de bas de page, certains éléments renvoient à des clauses qui ne sont pas incluses dans le présent document. Ils ne sont inclus que s’il s'agit d’une nouvelle exigence et qu’ils renvoient uniquement aux lignes directrices des WCAG.

Sources

Tableaux comparatifs

Glossaire

Reformulation stylistique :
le texte du critère modifie ce qui est dit, mais ne modifie pas ce que le critère demande, ni n’ajoute de nouveau contenu ou de nouvelles stipulations au critère existant.
Changement fonctionnel :
le texte du critère modifie considérablement ce que le critère demande, par exemple : le mot « devrait » (dénotant une recommandation) est remplacé par le mot « doit » (dénotant une exigence).
Mise à jour explicative :
le texte comporte des contenus ou des stipulations qui clarifient le but du critère sans en changer carrément l’objectif, par exemple en précisant la source d'un document.
Changement de numérotation :
la numérotation des critères est mise à jour en raison de l’intégration de la numérotation des WCAG dans le document ou d’un changement de l’ordre dans lequel ils apparaissent dans le document pour une meilleure fluidité et une meilleure compréhension.
Nouvelle exigence :
un critère qui n’existe pas dans une version précédente du document EN 301 549. Plusieurs nouveaux critères ont été ajoutés dans la version 2019 qui ne figurent ni dans la version 2014 ni dans la version 2018.

Les changements entre les versions de l’EN 301 549 sont ainsi soulignés :

  1. Pour les changements dans les hyperliens, les changements sont reflétés en gras, à l’aide du style de texte bleu fort souligné.
  2. Pour les changements dans le texte, les changements sont reflétés en gras, à l’aide du style de texte fort.
  3. Pour les changements dans le titre de la clause, les changements sont reflétés en gras, à l’aide du style de texte bleu fort.
Sélectionner pour voir les changements

Liste des tableaux

Liste des tableaux

Chapitre 2 – Exigences relatives à la portée

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

E207.2 Conformité des WCAG

Les composants de l’interface utilisateur ainsi que le contenu des plateformes et des applications doivent être conformes aux critères de succès de niveau A et de niveau AA et aux exigences de conformité spécifiées pour les pages Web dans les WCAG 2.0.

EXCEPTIONS :

  1. Les logiciels qui sont des technologies d’assistance et qui prennent en charge les services d’accessibilité de la plateforme n’ont pas à être conformes à la clause E207.2.
  2. Les logiciels non Web n’ont pas à être conformes aux quatre critères de succès suivants dans les WCAG 2.0 : 2.4.1 Contourner des blocs; 2.4.5 Accès multiples; 3.2.3 Navigation cohérente; et 3.2.4 Identification cohérente.
  3. Les logiciels non Web n’ont pas à être conformes à l’exigence de conformité 3 Processus complets des WCAG 2.0.

Les chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.0 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).

EN 301 549 Série vidéo

Reformulation stylistiqueLes chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).Changement fonctionnelLes chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).Les chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11)

Chapitre 3 – Critères de rendement fonctionnel

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

302.1 Sans vision

Lorsqu’un mode de fonctionnement visuel est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas la vision des utilisateurs.

4.2.1 Utilisation sans vision

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas la vision.

REMARQUE : Les interfaces utilisateur audio et tactiles peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.1 Utilisation sans vision

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas la vision.

REMARQUE 1 : Une page Web ou une application ayant une structure sémantique bien formée peut permettre aux utilisateurs sans vision de naviguer dans une interface utilisateur visuelle et d’interagir avec celle-ci.

REMARQUE 2 : Les interfaces utilisateur audio et tactiles peuvent contribuer au respect de cette clause.

Mise à jour explicative

4.2.1 Utilisation sans vision

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent au moins un mode de fonctionnement qui ne requiert pas la vision. Ceci est essentiel pour les utilisateurs sans vision et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Une page Web ou une application ayant une structure sémantique bien formée peut permettre aux utilisateurs sans vision de naviguer dans une interface utilisateur visuelle et d’interagir avec celle-ci.

REMARQUE 2 : Les interfaces utilisateur audio et tactiles peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.1 Utilisation sans vision

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent au moins un mode de fonctionnement qui ne requiert pas la vision. Ceci est essentiel pour les utilisateurs sans vision et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Une page Web ou une application ayant une structure sémantique bien formée peut permettre aux utilisateurs sans vision de naviguer dans une interface utilisateur visuelle et d’interagir avec celle-ci.

REMARQUE 2 : Les interfaces utilisateur audio et tactiles peuvent contribuer au respect de cette clause.

302.2 Avec vision limitée

Lorsqu’un mode de fonctionnement visuel est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui permet aux utilisateurs d’utiliser leur vision limitée.

4.2.2 Utilisation avec vision limitée

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec des fonctions leur permettant de mieux utiliser leur vision limitée.

REMARQUE 1 : Le grossissement, la réduction du champ de vision requis et le contrôle du contraste, de la luminosité et de l’intensité peuvent contribuer au respect de cette clause.

REMARQUE 2 : Lorsque des caractéristiques importantes de l’interface utilisateur dépendent de la perception de la profondeur, la fourniture de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une vision limitée peuvent également bénéficier d’un accès non visuel (voir la clause 4.2.1)

Reformulation stylistique

Mise à jour explicative

4.2.2 Utilisation avec vision limitée

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec des fonctions leur permettant de mieux utiliser leur vision limitée.

REMARQUE 1 : Le grossissement, la réduction du champ de vision requis et le contrôle du contraste, de la luminosité et de l’intensité peuvent contribuer au respect de cette clause.

REMARQUE 2 : Lorsque des caractéristiques importantes de l’interface utilisateur dépendent de la perception de la profondeur, la fourniture de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une vision limitée peuvent également bénéficier d’un accès non visuel (voir la clause 4.2.1)

4.2.2 Utilisation avec vision limitée

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent des fonctions permettant aux utilisateurs de mieux utiliser leur vision limitée. Ceci est essentiel pour les utilisateurs ayant une vision limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Le grossissement, la réduction du champ de vision requis et le contrôle du contraste, de la luminosité et de l’intensité peuvent contribuer au respect de cette clause.

REMARQUE 2 : Lorsque des caractéristiques importantes de l’interface utilisateur dépendent de la perception de la profondeur, la fourniture de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une vision limitée peuvent également bénéficier d’un accès non visuel (voir la clause 4.2.1)

Reformulation stylistique

Mise à jour explicative

4.2.2 Utilisation avec vision limitée

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent des fonctions permettant aux utilisateurs de mieux utiliser leur vision limitée. Ceci est essentiel pour les utilisateurs ayant une vision limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Le grossissement, la réduction du champ de vision requis et le contrôle du contraste, de la luminosité et de l’intensité peuvent contribuer au respect de cette clause.

REMARQUE 2 : Lorsque des caractéristiques importantes de l’interface utilisateur dépendent de la perception de la profondeur, fournir des méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une vision limitée peuvent également bénéficier d’un accès non visuel (voir la clause 4.2.1)

302.3 Sans perception des couleurs

Lorsqu’un mode de fonctionnement visuel est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui n’exige pas la perception des couleurs par les utilisateurs.

4.2.3 Utilisation sans perception des couleurs

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec un mode de fonctionnement visuel qui n’exige pas la perception des couleurs par les utilisateurs.

REMARQUE : Lorsque des caractéristiques importantes de l’interface utilisateur sont codées par couleur, l’ajout de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.3 Utilisation sans perception des couleurs

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec un mode de fonctionnement visuel qui n’exige pas la perception des couleurs par les utilisateurs.

REMARQUE : Lorsque des caractéristiques importantes de l’interface utilisateur sont codées par couleur, l’ajout de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

4.2.3 Utilisation sans perception des couleurs

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent un mode de fonctionnement visuel qui n’exige pas la perception des couleurs par les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une perception limitée des couleurs et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : Lorsque des caractéristiques importantes de l’interface utilisateur sont codées par couleur, l’ajout de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.3 Utilisation sans perception des couleurs

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent un mode de fonctionnement visuel qui n’exige pas la perception des couleurs par les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une perception limitée des couleurs et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : Lorsque des caractéristiques importantes de l’interface utilisateur sont codées par couleur, l’ajout de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

302.4 Sans audition

Lorsqu’un mode de fonctionnement sonore est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas l’audition des utilisateurs.

4.2.4 Utilisation sans audition

Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas l’audition.

REMARQUE : Les interfaces utilisateur visuelles et tactiles peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.4 Utilisation sans audition

Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas l’audition.

REMARQUE : Les interfaces utilisateur visuelles et tactiles peuvent contribuer au respect de cette clause.

4.2.4 Utilisation sans audition

Lorsque les TIC prévoient un mode de fonctionnement sonore, les TIC fournissent au moins un mode de fonctionnement qui ne requiert pas l’audition. Ceci est essentiel pour les utilisateurs sans audition et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : Les interfaces utilisateur visuelles et tactiles, y compris celles fondées sur la langue des signes, peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.4 Utilisation sans audition

Lorsque les TIC prévoient un mode de fonctionnement sonore, les TIC fournissent au moins un mode de fonctionnement qui ne requiert pas l’audition. Ceci est essentiel pour les utilisateurs sans audition et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : Les interfaces utilisateur visuelles et tactiles, y compris celles fondées sur la langue des signes, peuvent contribuer au respect de cette clause.

302.5 Avec audition limitée

Lorsqu’un mode de fonctionnement sonore est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui permet aux utilisateurs d’utiliser leur audition limitée.

4.2.5 Utilisation avec audition limitée

Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin des TIC avec des fonctions audio améliorées.

REMARQUE 1 : L’amélioration de la clarté audio, la réduction du bruit de fond, l’augmentation de la plage de volume et l’augmentation du volume dans la plage de fréquences supérieures peuvent contribuer au respect de cette clause.

REMARQUE 2 : Les utilisateurs ayant une audition limitée peuvent également bénéficier d’un accès non auditif (voir la clause 4.2.4).

Reformulation stylistique

Mise à jour explicative

4.2.5 Utilisation avec audition limitée

Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin des TIC avec des fonctions audio améliorées.

REMARQUE 1 : L’amélioration de la clarté audio, la réduction du bruit de fond, l’augmentation de la plage de volume et l’augmentation du volume dans la plage de fréquences supérieures peuvent contribuer au respect de cette clause.

REMARQUE 2 : Les utilisateurs ayant une audition limitée peuvent également bénéficier d’un accès non auditif (voir la clause 4.2.4).

4.2.5 Utilisation avec audition limitée

Lorsque les TIC prévoient un mode de fonctionnement sonore, les TIC fournissent des fonctions audios améliorées. Ceci est essentiel pour les utilisateurs ayant une audition limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : L’amélioration de la clarté audio, la réduction du bruit de fond, l’offre d’une option monaurale commune, le réglage d’équilibre des deux canaux audio, l’augmentation de la plage de volume et l’augmentation du volume dans la plage de fréquences supérieures peuvent contribuer au respect de cette clause.

REMARQUE 2 : Permettre l'utilisation d’aides de suppléance à l’audition, comme des casques avec annulation du bruit (connectés par câble, Bluetooth ou WLAN) peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une audition limitée peuvent également bénéficier d’un accès non auditif (voir la clause 4.2.4).

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

4.2.5 Utilisation avec audition limitée

Lorsque les TIC prévoient un mode de fonctionnement sonore, les TIC fournissent des fonctions audios améliorées. Ceci est essentiel pour les utilisateurs ayant une audition limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : L’amélioration de la clarté audio, la réduction du bruit de fond, l’offre d’une option monaurale commune, le réglage d’équilibre des deux canaux audio, l’augmentation de la plage de volume et l’augmentation du volume dans la plage de fréquences supérieures peuvent contribuer au respect de cette clause.

REMARQUE 2 : Permettre l'utilisation d’aides de suppléance à l’audition, comme des casques avec annulation du bruit (connectés par câble, Bluetooth ou WLAN) peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une audition limitée peuvent également bénéficier d’un accès non auditif (voir la clause 4.2.4).

302.6 Sans capacité vocale

Lorsque la contribution vocale est utilisée pour la saisie, le contrôle ou le fonctionnement, les TIC doivent fournir au moins un mode de fonctionnement qui n’exige pas la contribution vocale des utilisateurs.

4.2.6 Utilisation sans capacité vocale

Lorsque les TIC nécessitent la contribution vocale des utilisateurs, certains utilisateurs auront besoin des TIC pour fournir au moins un mode de fonctionnement qui n’exige pas d’entrée vocale.

REMARQUE 1 : Cette clause couvre les solutions de rechange à l’utilisation des sons générés oralement, y compris la parole, les sifflements, les clics, etc.

REMARQUE 2 : Le clavier, le stylo ou les interfaces utilisateur tactiles peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.6 Utilisation sans capacité vocale

Lorsque les TIC nécessitent la contribution vocale des utilisateurs, certains utilisateurs auront besoin des TIC pour fournir au moins un mode de fonctionnement qui n’exige pas d’entrée vocale.

REMARQUE 1 : Cette clause couvre les solutions de rechange à l’utilisation des sons générés oralement, y compris la parole, les sifflements, les clics, etc.

REMARQUE 2 : Le clavier, le stylo ou les interfaces utilisateur tactiles peuvent contribuer au respect de cette clause.

4.2.6 Utilisation sans capacité vocale ou avec une capacité vocale limitée

Lorsque les TIC nécessitent la contribution vocale des utilisateurs, les TIC fournissent au moins un mode de fonctionnement qui n’exige pas d’entrée vocale. Ceci est essentiel pour les utilisateurs sans capacité vocale ou ayant une capacité vocale limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : La sortie vocale comprend la parole et les autres sons générés oralement, comme les sifflements et les clics.

REMARQUE 2 : Le clavier, le stylo ou les interfaces utilisateur tactiles peuvent contribuer au respect de cette clause.

Changement fonctionnel

Reformulation stylistique

Mise à jour explicative

4.2.6 Utilisation sans capacité vocale ou avec une capacité vocale limitée

Lorsque les TIC nécessitent la contribution vocale des utilisateurs, les TIC fournissent au moins un mode de fonctionnement qui n’exige pas d’entrée vocale. Ceci est essentiel pour les utilisateurs sans capacité vocale ou ayant une capacité vocale limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : La sortie vocale comprend la parole et les autres sons générés oralement, comme les sifflements et les clics.

REMARQUE 2 : Le clavier, le stylo ou les interfaces utilisateur tactiles peuvent contribuer au respect de cette clause.

302.7 Avec une capacité de manipulation limitée

Lorsqu’un mode de fonctionnement manuel est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui n’exige pas un contrôle de la motricité fine ou des actions manuelles simultanées des utilisateurs.1

4.2.7 Utilisation avec une capacité de manipulation ou de force limitée

Lorsque les TIC nécessitent des actions manuelles, certains utilisateurs auront besoin de TIC avec des caractéristiques qui permettent aux utilisateurs d’utiliser les TIC par d’autres actions ne nécessitant aucune manipulation ou force de la main.

REMARQUE 1 : Parmi les exemples d’opérations que les utilisateurs peuvent ne pas être en mesure d’effectuer, mentionnons celles qui nécessitent un contrôle de la motricité fine, des gestes dépendant de la trajectoire, un pincement, une torsion du poignet, une prise ferme ou des actions manuelles simultanées.

REMARQUE 2 : L’utilisation d’une seule main, la saisie séquentielle des touches et les interfaces utilisateur vocales peuvent contribuer au respect de cette clause.

REMARQUE 3 : Certains utilisateurs ont une force de la main limitée et peuvent ne pas être en mesure d’atteindre le niveau de force nécessaire pour effectuer une opération. D’autres solutions d’interface utilisateur qui ne nécessitent pas de force manuelle peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.7 Utilisation avec une capacité de manipulation ou de force limitée

Lorsque les TIC nécessitent des actions manuelles, certains utilisateurs auront besoin de TIC avec des caractéristiques qui permettent aux utilisateurs d’utiliser les TIC par d’autres actions ne nécessitant aucune manipulation ou force de la main.

REMARQUE 1 : Parmi les exemples d’opérations que les utilisateurs peuvent ne pas être en mesure d’effectuer, mentionnons celles qui nécessitent un contrôle de la motricité fine, des gestes dépendant de la trajectoire, un pincement, une torsion du poignet, une prise ferme ou des actions manuelles simultanées.

REMARQUE 2 : L’utilisation d’une seule main, la saisie séquentielle des touches et les interfaces utilisateur vocales peuvent contribuer au respect de cette clause.

REMARQUE 3 : Certains utilisateurs ont une force de la main limitée et peuvent ne pas être en mesure d’atteindre le niveau de force nécessaire pour effectuer une opération. D’autres solutions d’interface utilisateur qui ne nécessitent pas de force manuelle peuvent contribuer au respect de cette clause.

4.2.7 Utilisation avec une capacité de manipulation ou de force limitée

Lorsque les TIC nécessitent des actions manuelles, les TIC fournissent des caractéristiques qui permettent aux utilisateurs d’utiliser les TIC par d’autres actions ne nécessitant aucune manipulation, action simultanée ou force de la main. Ceci est essentiel pour les utilisateurs ayant une capacité de manipulation ou de force limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Parmi les exemples d’opérations que les utilisateurs peuvent ne pas être en mesure d’effectuer, mentionnons celles qui nécessitent un contrôle de la motricité fine, des gestes dépendant de la trajectoire, un pincement, une torsion du poignet, une prise ferme ou des actions manuelles simultanées.

REMARQUE 2 : L’utilisation d’une seule main, la saisie séquentielle des touches et les interfaces utilisateur vocales peuvent contribuer au respect de cette clause.

REMARQUE 3 : Certains utilisateurs ont une force de la main limitée et peuvent ne pas être en mesure d’atteindre le niveau de force nécessaire pour effectuer une opération. D’autres solutions d’interface utilisateur qui ne nécessitent pas de force manuelle peuvent contribuer au respect de cette clause.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

4.2.7 Utilisation avec une capacité de manipulation ou de force limitée

Lorsque les TIC nécessitent des actions manuelles, les TIC fournissent des caractéristiques qui permettent aux utilisateurs d’utiliser les TIC par d’autres actions ne nécessitant aucune manipulation, action simultanée ou force de la main. Ceci est essentiel pour les utilisateurs ayant une capacité de manipulation ou de force limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Parmi les exemples d’opérations que les utilisateurs peuvent ne pas être en mesure d’effectuer, mentionnons celles qui nécessitent un contrôle de la motricité fine, des gestes dépendant de la trajectoire, un pincement, une torsion du poignet, une prise ferme ou des actions manuelles simultanées.

REMARQUE 2 : L’utilisation d’une seule main, la saisie séquentielle des touches et les interfaces utilisateur vocales peuvent contribuer au respect de cette clause.

REMARQUE 3 : Certains utilisateurs ont une force de la main limitée et peuvent ne pas être en mesure d’atteindre le niveau de force nécessaire pour effectuer une opération. D’autres solutions d’interface utilisateur qui ne nécessitent pas de force manuelle peuvent contribuer au respect de cette clause.

302.8 Avec une portée et une force limitée

Lorsqu’un mode de fonctionnement manuel est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui peut être manœuvrable moyennant une portée et une force limitée.2

4.2.8 Utilisation à portée limitée

Lorsque les produits des TIC sont autonomes ou installés, les éléments opérationnels doivent être à la portée de tous les utilisateurs.

REMARQUE : La prise en compte des besoins des utilisateurs de fauteuils roulants et de l’éventail de statures d’utilisateur dans la disposition des éléments opérationnels de l’interface utilisateur peut contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.8 Utilisation à portée limitée

Lorsque les produits des TIC sont autonomes ou installés, les éléments opérationnels doivent être à la portée de tous les utilisateurs.

REMARQUE : La prise en compte des besoins des utilisateurs de fauteuils roulants et de l’éventail de statures d’utilisateur dans la disposition des éléments opérationnels de l’interface utilisateur peut contribuer au respect de cette clause.

4.2.8 Utilisation à portée limitée

Lorsque les produits des TIC sont autonomes ou installés, tous les éléments requis pour les opérations doivent être à la portée de tous les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une portée limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : La prise en compte des besoins des utilisateurs de fauteuils roulants et de l’éventail de statures d’utilisateur dans la disposition des éléments opérationnels de l’interface utilisateur peut contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.8 Utilisation à portée limitée

Lorsque les produits des TIC sont autonomes ou installés, tous les éléments requis pour les opérations doivent être à la portée de tous les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une portée limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : La prise en compte des besoins des utilisateurs de fauteuils roulants et de l’éventail de statures d’utilisateur dans la disposition des éléments opérationnels de l’interface utilisateur peut contribuer au respect de cette clause.

302.9 Avec des capacités linguistiques, cognitives et d’apprentissage limitées

Les TIC doivent fournir des fonctions qui sont plus simples à utiliser par les utilisateurs ayant des capacités cognitives, linguistiques et d’apprentissage limitées.

4.2.10 Utilisation avec une cognition limitée

Certains utilisateurs auront besoin de TIC avec des fonctions qui simplifient l’utilisation.

REMARQUE 1 : Cette clause vise à inclure les besoins des personnes ayant des capacités cognitives, linguistiques et d’apprentissage limitées.

REMARQUE 2 : Les temporisations ajustables, l’indication et la suggestion d’erreurs, ainsi qu’un ordre de mise au point logique sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.10 Utilisation avec une cognition limitée

Certains utilisateurs auront besoin de TIC avec des fonctions qui simplifient l’utilisation.

REMARQUE 1 : Cette clause vise à inclure les besoins des personnes ayant des capacités cognitives, linguistiques et d’apprentissage limitées.

REMARQUE 2 : Les temporisations ajustables, l’indication et la suggestion d’erreurs, ainsi qu’un ordre de mise au point logique sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

4.2.10 Utilisation avec des capacités cognitives, linguistiques et d’apprentissage limitées

Les TIC fournissent des fonctions et/ou une présentation qui simplifient la compréhension, le fonctionnement et l’utilisation. Ceci est essentiel pour les utilisateurs ayant une cognition limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Cette clause vise à inclure les besoins des personnes ayant des capacités cognitives, linguistiques et d’apprentissage limitées.

REMARQUE 2 : Fournir une sortie audio du texte est un exemple de soutien aux personnes ayant des capacités de lecture limitées.

REMARQUE 3 : Fournir une assistance orthographique et la prédiction des mots du texte est un exemple de soutien aux personnes ayant des capacités d'écriture limitées.

REMARQUE 4 : L’interaction avec le contenu peut être facilitée, et moins sujette aux erreurs, en présentant les tâches par étapes faciles à suivre.

Changement fonctionnel

Reformulation stylistique

Mise à jour explicative

4.2.10 Utilisation avec des capacités cognitives, linguistiques et d’apprentissage limitées

Les TIC fournissent des fonctions et/ou une présentation qui simplifient la compréhension, le fonctionnement et l’utilisation. Ceci est essentiel pour les utilisateurs ayant une cognition limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Les temporisations ajustables, l’indication et la suggestion d’erreurs, ainsi qu’un ordre de mise au point logique sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

REMARQUE 2 : Fournir une sortie audio du texte est un exemple de soutien aux personnes ayant des capacités de lecture limitées.

REMARQUE 3 : Fournir une assistance orthographique et la prédiction des mots du texte est un exemple de soutien aux personnes ayant des capacités d'écriture limitées.

REMARQUE 4 : L’interaction avec le contenu peut être facilitée, et moins sujette aux erreurs, en présentant les tâches par étapes faciles à suivre.

Liste des tableaux

### Chapitre 4 – Matériel

402 Fonctions restreintes

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

402.1 Généralités

Les TIC ayant une fonction restreinte doivent pouvoir fonctionner sans que l’utilisateur ait à joindre ou à installer une technologie d’assistance autre que des casques d’écoute personnels ou d’autres coupleurs audios, et doivent être conformes à la clause 402.

5.1.2.2 Technologie d’assistance

Lorsque les TIC ont une fonction restreinte, cette fonction restreinte doit pouvoir fonctionner sans que l’utilisateur ait à joindre, connecter ou installer une technologie d’assistance et doit être conforme aux exigences génériques des clauses 5.1.3 à 5.1.7 selon le cas. Les casques d’écoute personnels et les boucles inductives ne doivent pas être considérés comme une technologie d’assistance aux fins de la présente clause.

Reformulation stylistique

Mise à jour explicative

5.1.2.2 Technologie d’assistance

Lorsque les TIC ont une fonction restreinte, cette fonction restreinte doit pouvoir fonctionner sans que l’utilisateur ait à joindre, connecter ou installer une technologie d’assistance et doit être conforme aux exigences génériques des clauses 5.1.3 à 5.1.6 selon le cas. Les casques d’écoute personnels et les boucles inductives ne doivent pas être considérés comme une technologie d’assistance aux fins de la présente clause.

Changement de numérotation

5.1.2.2 Technologie d’assistance

Lorsque les TIC ont une fonction restreinte, cette fonction restreinte doit pouvoir fonctionner sans que l’utilisateur ait à joindre, connecter ou installer une technologie d’assistance et doit être conforme aux exigences génériques des clauses 5.1.3 à 5.1.6 selon le cas. Les casques d’écoute personnels et les boucles inductives personnelles ne doivent pas être considérés comme une technologie d’assistance aux fins de la présente clause.

Reformulation stylistique

5.1.2.2 Technologie d’assistance

Lorsque les TIC ont une fonction restreinte, cette fonction restreinte doit pouvoir fonctionner sans que l’utilisateur ait à joindre, connecter ou installer une technologie d’assistance et doit être conforme aux exigences génériques des clauses 5.1.3 à 5.1.6 selon le cas. Les casques d’écoute personnels et les boucles inductives personnelles ne doivent pas être considérés comme une technologie d’assistance aux fins de la présente clause.

402.2 Sortie vocale activée

Les TIC ayant un écran d’affichage doivent être dotées d’une sortie vocale pour permettre aux utilisateurs atteints de déficience visuelle une utilisation complète et autonome.3

EXCEPTIONS :

  1. Les panneaux à messages variables conformes à la clause 402.5 n’ont pas à être dotés d’une sortie vocale.
  2. Une sortie vocale n’est pas requise lorsque les écrans d’affichage des TIC fournissent uniquement des indicateurs d’état et ces indicateurs sont conformes à la clause 409.
  3. Lorsque la sortie vocale ne peut pas être prise en charge en raison de contraintes de mémoire disponible ou de capacité du processeur, les TIC doivent être autorisées à se conformer à la clause 409 au lieu de 402.2.
  4. Les tonalités sonores doivent être autorisées à la place d’une sortie vocale lorsque le contenu des entrées utilisateurs n’est pas affiché tel qu’il a été saisi à des fins de sécurité, y compris, sans toutefois s’y limiter, les astérisques représentant des numéros d’identification personnels.
  5. Une sortie vocale n’est pas requise pour : l’emplacement de la machine, la date et l’heure de la transaction, le numéro de compte client et l’identificateur ou la plaque signalétique de la machine.
  6. Une sortie vocale n’est pas requise pour les annonces publicitaires et autres renseignements similaires, sauf si elles transmettent des renseignements pouvant être utilisés pour la transaction en cours.

5.1.3.1 Généralités

Lorsque des informations visuelles sont nécessaires pour permettre l’utilisation des fonctions des TIC restreintes aux technologies d’assistance pour la lecture d’écran, les TIC doivent prévoir au moins un mode de fonctionnement utilisant un accès non visuel pour permettre l’utilisation de ces fonctions.

REMARQUE 1 : L’accès non visuel peut se faire sous forme audio, y compris la parole, ou sous forme tactile.

REMARQUE 2 : Les informations visuelles nécessaires pour permettre l’utilisation de certaines fonctions peuvent inclure les instructions d’utilisation et l’orientation, les invites de transaction, la vérification des entrées utilisateur, les messages d’erreur et le contenu non textuel.

Reformulation stylistique

Mise à jour explicative

5.1.3.1 Généralités

Lorsque des informations visuelles sont nécessaires pour permettre l’utilisation des fonctions des TIC restreintes aux technologies d’assistance pour la lecture d’écran, les TIC doivent prévoir au moins un mode de fonctionnement utilisant un accès non visuel pour permettre l’utilisation de ces fonctions.

REMARQUE 1 : L’accès non visuel peut se faire sous forme audio, y compris la parole, ou sous forme tactile.

REMARQUE 2 : Les informations visuelles nécessaires pour permettre l’utilisation de certaines fonctions peuvent inclure les instructions d’utilisation et l’orientation, les invites de transaction, la vérification des entrées utilisateur, les messages d’erreur et le contenu non textuel.

5.1.3.1 Sortie audio des informations visuelles

Lorsque des informations visuelles sont nécessaires pour permettre l’utilisation des fonctions des TIC restreintes aux technologies d’assistance pour la lecture d’écran, les TIC doivent prévoir au moins un mode de fonctionnement utilisant un accès non visuel pour permettre l’utilisation de ces fonctions.

REMARQUE 1 : L’accès non visuel peut se faire sous forme audio, y compris la parole, ou sous forme tactile, comme le braille pour les utilisateurs sourds et aveugles.

REMARQUE 2 : Les informations visuelles nécessaires pour permettre l’utilisation de certaines fonctions peuvent inclure les instructions d’utilisation et l’orientation, les invites de transaction, la vérification des entrées utilisateur, les messages d’erreur et le contenu non textuel.

Mise à jour explicative

5.1.3.1 Sortie audio des informations visuelles

Lorsque des informations visuelles sont nécessaires pour permettre l’utilisation des fonctions des TIC restreintes aux technologies d’assistance pour la lecture d’écran, les TIC doivent prévoir au moins un mode de fonctionnement utilisant un accès non visuel pour permettre l’utilisation de ces fonctions.

REMARQUE 1 : L’accès non visuel peut se faire sous forme audio, y compris la parole, ou sous forme tactile, comme le braille pour les utilisateurs sourds et aveugles.

REMARQUE 2 : Les informations visuelles nécessaires pour permettre l’utilisation de certaines fonctions peuvent inclure les instructions d’utilisation et l’orientation, les invites de transaction, la vérification des entrées utilisateur, les messages d’erreur et le contenu non textuel.

402.2.1 Renseignements affichés à l’écran

Une sortie vocale doit être fournie pour tous les renseignements affichés à l’écran.

5.1.3.7 Sortie vocale pour l’information vidéo

Lorsqu’un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation de fonctions restreintes des TIC et que la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit présenter des informations équivalentes pour le contenu vidéo préenregistré.

REMARQUE : Cette sortie vocale peut prendre la forme d’une description audio ou d’une transcription auditive du contenu vidéo.

Reformulation stylistique

Mise à jour explicative

5.1.3.7 Sortie vocale pour l’information vidéo

Lorsqu’un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation de fonctions restreintes des TIC et que la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit présenter des informations équivalentes pour le contenu vidéo préenregistré.

REMARQUE : Cette sortie vocale peut prendre la forme d’une description audio ou d’une transcription auditive du contenu vidéo.

5.1.3.7 Sortie vocale pour l’information vidéo

Lorsqu’un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation de fonctions restreintes des TIC et que la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit présenter des informations équivalentes pour le contenu vidéo préenregistré.

REMARQUE : Cette sortie vocale peut prendre la forme d’une description audio ou d’une transcription auditive du contenu vidéo.

5.1.3.7 Sortie vocale pour l’information vidéo

Lorsqu’un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation de fonctions restreintes des TIC et que la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit présenter des informations équivalentes pour le contenu vidéo préenregistré.

REMARQUE : Cette sortie vocale peut prendre la forme d’une description audio ou d’une transcription auditive du contenu vidéo.

402.2.1 Renseignements affichés à l’écran

Une sortie vocale doit être fournie pour tous les renseignements affichés à l’écran.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

Reformulation stylistique

Mise à jour explicative

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

402.2.2 Sorties transactionnelles

Lorsque des sorties transactionnelles sont fournies, la sortie vocale doit fournir de manière audible tous les renseignements nécessaires pour vérifier une transaction.

5.1.3.16 Reçus, billets et sorties transactionnelles

Lorsque les TIC sont restreintes à l’accès visuel et qu’elles fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service, une sortie vocale doit être fournie, comprenant tous les renseignements nécessaires pour conclure ou vérifier la transaction.

Dans le cas des distributeurs automatiques de billets, les copies imprimées des itinéraires et des cartes n’ont pas à être audibles.

REMARQUE : La sortie vocale peut être fournie par n’importe quel élément de l’ensemble du système de TIC.

Reformulation stylistique

Mise à jour explicative

5.1.3.16 Reçus, billets et sorties transactionnelles

Lorsque les TIC sont restreintes à l’accès visuel et qu’elles fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service, une sortie vocale doit être fournie, comprenant tous les renseignements nécessaires pour conclure ou vérifier la transaction.

Dans le cas des distributeurs automatiques de billets, les copies imprimées des itinéraires et des cartes n’ont pas à être audibles.

REMARQUE : La sortie vocale peut être fournie par n’importe quel élément de l’ensemble du système de TIC.

5.1.3.16 Reçus, billets et sorties transactionnelles

Lorsque les TIC sont restreintes à l’accès visuel et qu’elles fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service, une sortie vocale doit être fournie, comprenant tous les renseignements nécessaires pour conclure ou vérifier la transaction.

Dans le cas des distributeurs automatiques de billets, les copies imprimées des itinéraires et des cartes n’ont pas à être audibles.

REMARQUE : La sortie vocale peut être fournie par n’importe quel élément de l’ensemble du système de TIC.

5.1.3.16 Reçus, billets et sorties transactionnelles

Lorsque les TIC sont restreintes à l’accès visuel et qu’elles fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service, une sortie vocale doit être fournie, comprenant tous les renseignements nécessaires pour conclure ou vérifier la transaction.

Dans le cas des distributeurs automatiques de billets, les copies imprimées des itinéraires et des cartes n’ont pas à être audibles.

REMARQUE : La sortie vocale peut être fournie par n’importe quel élément de l’ensemble du système de TIC.

402.2.3 Type de fonctionnement vocal et coordination

La sortie vocale doit être fournie au moyen d’un mécanisme facilement accessible à tous les utilisateurs, y compris, sans toutefois s’y limiter, un connecteur accrédité par l’industrie ou un combiné téléphonique. La sortie vocale doit être enregistrée ou être une voix humaine numérisée, ou synthétisée. La sortie vocale doit être coordonnée avec les renseignements affichés à l’écran.

5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les fonctions sonores doivent être utilisées :

  1. soit directement au moyen d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci;
  2. soit au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

REMARQUE 1 : Les mécanismes intégrés ou fournis peuvent comprendre, mais sans s’y limiter, un haut-parleur, un combiné ou casque intégré ou un autre périphérique accrédité par l’industrie.

REMARQUE 2 : Par connexion accréditée par l’industrie, on entend par exemple une connexion sans fil.

REMARQUE 3 : Certains utilisateurs pourraient tirer parti d’un équipement à boucle inductive.

Reformulation stylistique

Mise à jour explicative

5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les fonctions sonores doivent être utilisées :

  1. soit directement au moyen d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci;
  2. soit au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

REMARQUE 1 : Les mécanismes intégrés ou fournis peuvent comprendre, mais sans s’y limiter, un haut-parleur, un combiné ou casque intégré ou un autre périphérique accrédité par l’industrie.

REMARQUE 2 : Par connexion accréditée par l’industrie, on entend par exemple une connexion sans fil.

REMARQUE 3 : Certains utilisateurs pourraient tirer parti d’un équipement à boucle inductive.

5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les fonctions sonores doivent être utilisées :

  1. soit directement au moyen d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci;
  2. soit au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

REMARQUE 1 : Les mécanismes intégrés ou fournis peuvent comprendre, mais sans s’y limiter, un haut-parleur, un combiné ou casque intégré ou un autre périphérique accrédité par l’industrie.

REMARQUE 2 : Par connexion accréditée par l’industrie, on entend par exemple une connexion sans fil.

REMARQUE 3 : Certains utilisateurs pourraient tirer parti d’un équipement à boucle inductive.

5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les fonctions sonores doivent être utilisées :

  1. soit directement au moyen d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci;
  2. soit au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

REMARQUE 1 : Les mécanismes intégrés ou fournis peuvent comprendre, mais sans s’y limiter, un haut-parleur, un combiné ou casque intégré ou un autre périphérique accrédité par l’industrie.

REMARQUE 2 : Par connexion accréditée par l’industrie, on entend par exemple une connexion sans fil.

REMARQUE 3 : Certains utilisateurs pourraient tirer parti d’un équipement à boucle inductive.

402.2.3 Type de fonctionnement vocal et coordination

La sortie vocale doit être fournie au moyen d’un mécanisme facilement accessible à tous les utilisateurs, y compris, sans toutefois s’y limiter, un connecteur accrédité par l’industrie ou un combiné téléphonique. La sortie vocale doit être enregistrée ou être une voix humaine numérisée, ou synthétisée. La sortie vocale doit être coordonnée avec les renseignements affichés à l’écran.

5.1.3.3 Corrélation de sortie sonore

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que l’information est affichée à l’écran, les TIC doivent fournir des informations auditives qui permettent à l’utilisateur de corréler l’audio avec l’information affichée à l’écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

Reformulation stylistique

Mise à jour explicative

5.1.3.3 Corrélation de sortie sonore

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que l’information est affichée à l’écran, les TIC doivent fournir des informations auditives qui permettent à l’utilisateur de corréler l’audio avec l’information affichée à l’écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

5.1.3.3 Corrélation de sortie sonore

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que l’information est affichée à l’écran, les TIC doivent fournir des informations auditives qui permettent à l’utilisateur de corréler l’audio avec l’information affichée à l’écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

5.1.3.3 Corrélation de sortie sonore

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que l’information est affichée à l’écran, les TIC doivent fournir des informations auditives qui permettent à l’utilisateur de corréler l’audio avec l’information affichée à l’écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

402.2.4 Contrôle par l’utilisateur

La sortie vocale de toute fonction unique doit être automatiquement interrompue lorsqu’une transaction est sélectionnée. La sortie vocale doit pouvoir être répétée et mise en pause.

5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit pouvoir être interrompue et répétée à la demande de l’utilisateur, lorsque les exigences de sécurité le permettent.

REMARQUE 1 : Il est préférable de permettre à l’utilisateur de faire une pause plutôt que de simplement interrompre la sortie vocale.

REMARQUE 2 : Il est préférable de permettre à l’utilisateur de ne répéter que la partie la plus récente plutôt que de recommencer depuis le début.

Reformulation stylistique

Mise à jour explicative

5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit pouvoir être interrompue et répétée à la demande de l’utilisateur, lorsque les exigences de sécurité le permettent.

REMARQUE 1 : Il est préférable de permettre à l’utilisateur de faire une pause plutôt que de simplement interrompre la sortie vocale.

REMARQUE 2 : Il est préférable de permettre à l’utilisateur de ne répéter que la partie la plus récente plutôt que de recommencer depuis le début.

5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit pouvoir être interrompue et répétée à la demande de l’utilisateur, lorsque les exigences de sécurité le permettent.

REMARQUE 1 : Il est préférable de permettre à l’utilisateur de faire une pause plutôt que de simplement interrompre la sortie vocale.

REMARQUE 2 : Il est préférable de permettre à l’utilisateur de ne répéter que la partie la plus récente plutôt que de recommencer depuis le début.

5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit pouvoir être interrompue et répétée à la demande de l’utilisateur, lorsque les exigences de sécurité le permettent.

REMARQUE 1 : Il est préférable de permettre à l’utilisateur de faire une pause plutôt que de simplement interrompre la sortie vocale.

REMARQUE 2 : Il est préférable de permettre à l’utilisateur de ne répéter que la partie la plus récente plutôt que de recommencer depuis le début.

402.2.4 Contrôle par l’utilisateur

La sortie vocale de toute fonction unique doit être automatiquement interrompue lorsqu’une transaction est sélectionnée. La sortie vocale doit pouvoir être répétée et mise en pause.

5.1.3.5 Interruption automatique de la sortie vocale

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC doivent interrompre la sortie vocale actuelle lorsqu’une action de l’utilisateur se produit et lorsque la nouvelle sortie vocale débute.

REMARQUE : Lorsqu’il est essentiel que l’utilisateur entende l’intégralité du message, par exemple une instruction de sécurité ou un avertissement, les TIC peuvent devoir bloquer toute action de l’utilisateur afin que la parole ne soit pas interrompue.

Reformulation stylistique

Mise à jour explicative

5.1.3.5 Interruption automatique de la sortie vocale

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC doivent interrompre la sortie vocale actuelle lorsqu’une action de l’utilisateur se produit et lorsque la nouvelle sortie vocale débute.

REMARQUE : Lorsqu’il est essentiel que l’utilisateur entende l’intégralité du message, par exemple une instruction de sécurité ou un avertissement, les TIC peuvent devoir bloquer toute action de l’utilisateur afin que la parole ne soit pas interrompue.

5.1.3.5 Interruption automatique de la sortie vocale

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC doivent interrompre la sortie vocale actuelle lorsqu’une action de l’utilisateur se produit et lorsque la nouvelle sortie vocale débute.

REMARQUE : Lorsqu’il est essentiel que l’utilisateur entende l’intégralité du message, par exemple une instruction de sécurité ou un avertissement, les TIC peuvent devoir bloquer toute action de l’utilisateur afin que la parole ne soit pas interrompue.

5.1.3.5 Interruption automatique de la sortie vocale

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC doivent interrompre la sortie vocale actuelle lorsqu’une action de l’utilisateur se produit et lorsque la nouvelle sortie vocale débute.

REMARQUE : Lorsqu’il est essentiel que l’utilisateur entende l’intégralité du message, par exemple une instruction de sécurité ou un avertissement, les TIC peuvent devoir bloquer toute action de l’utilisateur afin que la parole ne soit pas interrompue.

402.2.5 Instructions en braille

Lorsque la sortie vocale est requise par la clause 402.2, des instructions en braille doivent être fournies pour lancer le mode de fonctionnement vocal. Les services en braille doivent être obtenus par contrat et être conformes à la norme 36 CFR partie 1191, annexe D, article 703.3.1.

EXCEPTION : Les dispositifs à usage personnel n’ont pas à être conformes à la clause 402.2.5.

8.5 Indication tactile du mode vocal

Lorsque les TIC sont conçues pour une utilisation partagée et qu’une sortie vocale est disponible, une indication tactile des moyens permettant de lancer le mode de fonctionnement vocal doit être fournie.

REMARQUE : L’indication tactile peut inclure des instructions en braille.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.5 Indication tactile du mode vocal

Lorsque les TIC sont conçues pour une utilisation partagée et qu’une sortie vocale est disponible, une indication tactile des moyens permettant de lancer le mode de fonctionnement vocal doit être fournie.

REMARQUE : L’indication tactile peut inclure des instructions en braille.

8.5 Indication tactile du mode vocal

Lorsque les TIC sont conçues pour une utilisation partagée et qu’une sortie vocale est disponible, une indication tactile des moyens permettant de lancer le mode de fonctionnement vocal doit être fournie.

REMARQUE : L’indication tactile peut inclure des instructions en braille.

8.5 Indication tactile du mode vocal

Lorsque les TIC sont conçues pour une utilisation partagée et qu’une sortie vocale est disponible, une indication tactile des moyens permettant de lancer le mode de fonctionnement vocal doit être fournie.

REMARQUE : L’indication tactile peut inclure des instructions en braille.

402.3.1 Écoute privée

Lorsque les TIC fournissent un mode d’écoute privée, elles doivent fournir un mode de fonctionnement pour contrôler le volume. Lorsque les TIC fournissent une sortie par un transducteur audio qui est normalement tenu à l’oreille, il faut fournir un moyen de couplage magnétique efficace aux technologies auditives.

5.1.3.11 Volume d’écoute privé

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, et ce, par le biais d’un mécanisme d’écoute privée, les TIC doivent prévoir au moins un mode de fonctionnement non visuel pour contrôler le volume.

Reformulation stylistique

Mise à jour explicative

5.1.3.11 Volume d’écoute privé

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, et ce, par le biais d’un mécanisme d’écoute privée, les TIC doivent prévoir au moins un mode de fonctionnement non visuel pour contrôler le volume.

5.1.3.11 Volume d’écoute privé

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, et ce, par le biais d’un mécanisme d’écoute privée, les TIC doivent prévoir au moins un mode de fonctionnement non visuel pour contrôler le volume.

5.1.3.11 Volume d’écoute privé

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, et ce, par le biais d’un mécanisme d’écoute privée, les TIC doivent prévoir au moins un mode de fonctionnement non visuel pour contrôler le volume.

402.3.1 Écoute privée

Lorsque les TIC fournissent un mode d’écoute privée, elles doivent fournir un mode de fonctionnement pour contrôler le volume. Lorsque les TIC fournissent une sortie par un transducteur audio qui est normalement tenu à l’oreille, il faut fournir un moyen de couplage magnétique efficace aux technologies auditives.

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille et qui porte le symbole « T » spécifié dans la norme ETS 300 381, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1.

REMARQUE : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

Reformulation stylistique

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille et qui porte le symbole « T » spécifié dans la norme ETS 300 381 de l’ETSI, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 de l’ETSI et doit porter le symbole « T » spécifié dans la norme ETS 300 381 de l’ETSI.

REMARQUE 1 : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

REMARQUE 2 : Le couplage magnétique est également appelé couplage inductif pour bobine en T.

Reformulation stylistique

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 [2] de l’ETSI et doit porter le symbole « T » spécifié dans la norme ETS 300 381 [1].de l’ETSI.

REMARQUE 1 : Les TIC répondant aux exigences de la norme TIA-1083-A [i.24] sont réputées conformes aux exigences de la présente clause.

REMARQUE 2 : Le couplage magnétique est également appelé couplage inductif pour bobine en T.

402.3.1 Écoute privée

Lorsque les TIC fournissent un mode d’écoute privée, elles doivent fournir un mode de fonctionnement pour contrôler le volume. Lorsque les TIC fournissent une sortie par un transducteur audio qui est normalement tenu à l’oreille, il faut fournir un moyen de couplage magnétique efficace aux technologies auditives.

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

Reformulation stylistique

Mise à jour explicative

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

Mise à jour explicative

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 [3] de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 [i.1] sont réputées conformes aux exigences de la présente clause.

402.3.2 Écoute non privée

Lorsque les TIC fournissent une écoute non privée, une commande de volume incrémentielle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA. Une fonction doit être fournie pour rétablir automatiquement le volume au niveau par défaut après chaque utilisation.

5.1.3.12 Volume de l’enceinte

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et qu’elle est fournie par des haut-parleurs sur les TIC, une commande de volume incrémentielle non visuelle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

REMARQUE : Pour les environnements bruyants, un niveau de 65 dBA peut ne pas être suffisant.

Reformulation stylistique

5.1.3.12 Volume de l’enceinte

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et qu’elle est fournie par des haut-parleurs sur les TIC, une commande de volume incrémentielle non visuelle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

REMARQUE : Pour les environnements bruyants, un niveau de 65 dBA peut ne pas être suffisant.

5.1.3.12 Volume de l’enceinte

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et qu’elle est fournie par des haut-parleurs sur les TIC, une commande de volume incrémentielle non visuelle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

REMARQUE : Pour les environnements bruyants, un niveau de 65 dBA peut ne pas être suffisant.

5.1.3.12 Volume de l’enceinte

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et qu’elle est fournie par des haut-parleurs sur les TIC, une commande de volume incrémentielle non visuelle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

REMARQUE : Pour les environnements bruyants, un niveau de 65 dBA peut ne pas être suffisant.

402.3.2 Écoute non privée

Lorsque les TIC fournissent une écoute non privée, une commande de volume incrémentielle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA. Une fonction doit être fournie pour rétablir automatiquement le volume au niveau par défaut après chaque utilisation.

5.1.3.13 Réinitialisation du volume

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, une fonction qui réinitialise le volume à un niveau inférieur ou égal à 65 dBA après chaque utilisation doit être fournie, sauf si les TIC sont destinées à un seul utilisateur.

REMARQUE : Une fonction permettant de désactiver la fonction de réinitialisation du volume peut être fournie afin de permettre de respecter l’exception de l’utilisateur unique.

Reformulation stylistique

Mise à jour explicative

5.1.3.13 Réinitialisation du volume

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, une fonction qui réinitialise le volume à un niveau inférieur ou égal à 65 dBA après chaque utilisation doit être fournie, sauf si les TIC sont destinées à un seul utilisateur.

REMARQUE : Une fonction permettant de désactiver la fonction de réinitialisation du volume peut être fournie afin de permettre de respecter l’exception de l’utilisateur unique.

5.1.3.13 Réinitialisation du volume

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, une fonction qui réinitialise le volume à un niveau inférieur ou égal à 65 dBA après chaque utilisation doit être fournie, sauf si les TIC sont destinées à un seul utilisateur.

REMARQUE : Une fonction permettant de désactiver la fonction de réinitialisation du volume peut être fournie afin de permettre de respecter l’exception de l’utilisateur unique.

5.1.3.13 Réinitialisation du volume

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, une fonction qui réinitialise le volume à un niveau inférieur ou égal à 65 dBA après chaque utilisation doit être fournie, sauf si les TIC sont destinées à un seul utilisateur.

REMARQUE 1 : Une fonction permettant de désactiver la fonction de réinitialisation du volume peut être fournie afin de permettre de respecter l’exception de l’utilisateur unique.

402.4 Caractères sur les écrans d’affichage

Au moins un mode de caractères affiché à l’écran doit être dans une police sans empattement. Lorsque les TIC ne prévoient pas de fonction d’agrandissement de l’écran, les caractères doivent avoir une hauteur minimale de 4,8 mm (3/16 po) en fonction de la lettre majuscule « I ». Les caractères doivent se distinguer de leur arrière-plan, soit au moyen de caractères de couleur claire sur fond sombre, soit de caractères de couleur sombre sur fond clair.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE 1 : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE 1 : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

402.5 Caractères sur les panneaux à messages variables

Les caractères sur les panneaux à messages variables doivent être conformes à l’article 703.7 Panneaux à messages variables de l’ICC A117.1-2009 (incorporé par renvoi, voir l’article 702.6.1).

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

Mise à jour explicative

Changement fonctionnel

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;

  • D et H sont exprimés dans les mêmes unités.

REMARQUE 1 : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

Liste des tableaux

403 Données biométriques

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

403.1 Généralités

Les données biométriques ne doivent pas être le seul moyen d'identification ou de contrôle de l'utilisateur.

EXCEPTION : Lorsqu’au moins deux options de données biométriques utilisant différentes caractéristiques biologiques sont fournies, les TIC doivent être autorisées à utiliser les données biométriques comme seul moyen d’identification de l’utilisateur ou de contrôle.

5.3 Données biométriques

Lorsque les TIC utilisent des caractéristiques biologiques, elles ne s’appuient pas sur l’utilisation d’une caractéristique biologique particulière comme seul moyen d’identification de l’utilisateur ou de contrôle des TIC.

REMARQUE 1 : D’autres moyens d’identification des utilisateurs ou de contrôle des TIC pourraient être non biométriques ou biométriques.

REMARQUE 2 : Les méthodes biométriques fondées sur des caractéristiques biologiques dissemblables augmentent la probabilité que les personnes handicapées possèdent au moins une des caractéristiques biologiques précisées. Les empreintes digitales, les motifs rétiniens des yeux, la voix et le visage sont des exemples de caractéristiques biologiques dissemblables.

Reformulation stylistique

Mise à jour explicative

5.3 Données biométriques

Lorsque les TIC utilisent des caractéristiques biologiques, elles ne s’appuient pas sur l’utilisation d’une caractéristique biologique particulière comme seul moyen d’identification de l’utilisateur ou de contrôle des TIC.

REMARQUE 1 : D’autres moyens d’identification des utilisateurs ou de contrôle des TIC pourraient être non biométriques ou biométriques.

REMARQUE 2 : Les méthodes biométriques fondées sur des caractéristiques biologiques dissemblables augmentent la probabilité que les personnes handicapées possèdent au moins une des caractéristiques biologiques précisées. Les empreintes digitales, les motifs rétiniens des yeux, la voix et le visage sont des exemples de caractéristiques biologiques dissemblables.

5.3 Données biométriques

Lorsque les TIC utilisent des caractéristiques biologiques, elles ne s’appuient pas sur l’utilisation d’une caractéristique biologique particulière comme seul moyen d’identification de l’utilisateur ou de contrôle des TIC.

REMARQUE 1 : D’autres moyens d’identification des utilisateurs ou de contrôle des TIC pourraient être non biométriques ou biométriques.

REMARQUE 2 : Les méthodes biométriques fondées sur des caractéristiques biologiques dissemblables augmentent la probabilité que les personnes handicapées possèdent au moins une des caractéristiques biologiques précisées. Les empreintes digitales, les motifs rétiniens des yeux, la voix et le visage sont des exemples de caractéristiques biologiques dissemblables.

5.3 Données

biométriques

Lorsque les TIC utilisent des caractéristiques biologiques, elles ne s’appuient pas sur l’utilisation d’une caractéristique biologique particulière comme seul moyen d’identification de l’utilisateur ou de contrôle des TIC.

REMARQUE 1 : D’autres moyens d’identification des utilisateurs ou de contrôle des TIC pourraient être non biométriques ou biométriques.

REMARQUE 2 : Les méthodes biométriques fondées sur des caractéristiques biologiques dissemblables augmentent la probabilité que les personnes handicapées possèdent au moins une des caractéristiques biologiques précisées.

Liste des tableaux

404 Préservation des renseignements fournis pour l’accessibilité

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

404.1 Généralités

Les TIC qui transmettent ou convertissent des renseignements ou des communications ne doivent pas supprimer les renseignements libres fournis aux fins d’accessibilité ou doivent les restaurer à la livraison.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

Reformulation stylistique

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

Liste des tableaux

405 Confidentialité

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021
405.1 Généralités
Le même degré de protection des données d’entrée et de sortie doit être fourni à tous les utilisateurs. Lorsque la sortie vocale requise par la clause 402.2 est activée, l’écran ne doit pas s’éteindre automatiquement.

5.1.3.9 Accès privé aux données personnelles

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que la sortie contient des données considérées comme étant privées conformément à la politique de confidentialité applicable, la sortie sonore correspondante ne peut être fournie que par le biais d’un mécanisme d’écoute privée qui peut être connecté sans nécessiter l’utilisation de la vision, ou par tout autre mécanisme explicitement choisi par l’utilisateur.

REMARQUE 1 : Cette exigence ne s’applique pas dans les cas où les données ne sont pas définies comme étant privées conformément à la politique de confidentialité applicable ou lorsqu’il n’existe aucune politique de confidentialité applicable.

REMARQUE 2 : La sortie non privée peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

Reformulation stylistique

Mise à jour explicative

5.1.3.9 Accès privé aux données personnelles

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que la sortie contient des données considérées comme étant privées conformément à la politique de confidentialité applicable, la sortie sonore correspondante ne peut être fournie que par le biais d’un mécanisme d’écoute privée qui peut être connecté sans nécessiter l’utilisation de la vision, ou par tout autre mécanisme explicitement choisi par l’utilisateur.

REMARQUE 1 : Cette exigence ne s’applique pas dans les cas où les données ne sont pas définies comme étant privées conformément à la politique de confidentialité applicable ou lorsqu’il n’existe aucune politique de confidentialité applicable.

REMARQUE 2 : La sortie non privée peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.9 Accès privé aux données personnelles

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que la sortie contient des données considérées comme étant privées conformément à la politique de confidentialité applicable, la sortie sonore correspondante ne peut être fournie que par le biais d’un mécanisme d’écoute privée qui peut être connecté sans nécessiter l’utilisation de la vision, ou par tout autre mécanisme explicitement choisi par l’utilisateur.

REMARQUE 1 : Cette exigence ne s’applique pas dans les cas où les données ne sont pas définies comme étant privées conformément à la politique de confidentialité applicable ou lorsqu’il n’existe aucune politique de confidentialité applicable.

REMARQUE 2 : La sortie non privée peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.9 Accès privé aux données personnelles

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que la sortie contient des données considérées comme étant privées conformément à la politique de confidentialité applicable, la sortie sonore correspondante ne peut être fournie que par le biais d’un mécanisme d’écoute privée qui peut être connecté sans nécessiter l’utilisation de la vision, ou par tout autre mécanisme explicitement choisi par l’utilisateur.

REMARQUE 1 : Cette exigence ne s’applique pas dans les cas où les données ne sont pas définies comme étant privées conformément à la politique de confidentialité applicable ou lorsqu’il n’existe aucune politique de confidentialité applicable.

REMARQUE 2 : La sortie non privée peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

405.1 Généralités

Le même degré de protection des données d’entrée et de sortie doit être fourni à tous les utilisateurs. Lorsque la sortie vocale requise par la clause 402.2 est activée, l’écran ne doit pas s’éteindre automatiquement.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

Reformulation stylistique

Mise à jour explicative

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

Liste des tableaux

406 Raccordements standard

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

406.1 Généralités

Lorsque des connexions de données utilisées pour l’entrée et la sortie sont fournies, au moins un de chaque type de connexion doit être conforme aux formats standard de l’industrie librement accessibles.

8.1.2 Raccordements standard

Lorsque les TIC fournissent des points de raccordement de dispositif d’entrée ou de sortie à l’utilisateur, elle comprend au moins un raccordement d’entrée ou de sortie conforme à un format standard de l’industrie librement accessible, directement ou au moyen d’adaptateurs offerts sur le marché.

REMARQUE 1 : L’exigence de raccordements standard vise à garantir la compatibilité avec les technologies d’assistance.

REMARQUE 2 : Le terme raccordement s’applique à la fois aux raccordements matériels et sans fil.

REMARQUE 3 : Les raccordements USB et Bluetooth sont des exemples de formats standard de l’industrie librement accessibles.

Reformulation stylistique

Mise à jour explicative

8.1.2 Raccordements standard

Lorsque les TIC fournissent des points de raccordement de dispositif d’entrée ou de sortie à l’utilisateur, elle comprend au moins un raccordement d’entrée ou de sortie conforme à un format standard de l’industrie librement accessible, directement ou au moyen d’adaptateurs offerts sur le marché.

REMARQUE 1 : L’exigence de raccordements standard vise à garantir la compatibilité avec les technologies d’assistance.

REMARQUE 2 : Le terme raccordement s’applique à la fois aux raccordements matériels et sans fil.

REMARQUE 3 : Les raccordements USB et Bluetooth sont des exemples de formats standard de l’industrie librement accessibles.

8.1.2 Raccordements standard

Lorsque les TIC fournissent des points de raccordement de dispositif d’entrée ou de sortie à l’utilisateur, elle comprend au moins un raccordement d’entrée ou de sortie conforme à un format standard de l’industrie librement accessible, directement ou au moyen d’adaptateurs offerts sur le marché.

REMARQUE 1 : L’exigence de raccordements standard vise à garantir la compatibilité avec les technologies d’assistance.

REMARQUE 2 : Le terme raccordement s’applique à la fois aux raccordements matériels et sans fil.

REMARQUE 3 : Les raccordements USB et Bluetooth sont des exemples de formats standard de l’industrie librement accessibles.

8.1.2 Raccordements standard

Lorsque les TIC fournissent des points de raccordement de dispositif d’entrée ou de sortie à l’utilisateur, elle comprend au moins un raccordement d’entrée ou de sortie conforme à un format standard de l’industrie librement accessible, directement ou au moyen d’adaptateurs offerts sur le marché.

REMARQUE 1 : L’exigence de raccordements standard vise à garantir la compatibilité avec les technologies d’assistance.

REMARQUE 2 : Le terme raccordement s’applique à la fois aux raccordements matériels et sans fil.

REMARQUE 3 : Les raccordements USB et Bluetooth sont des exemples de formats standard de l’industrie librement accessibles.

Liste des tableaux

407 Pièces manœuvrables

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

407.3.1 Perceptibles de manière tactile

Les commandes d’entrée doivent être manœuvrables et perceptibles de manière tactile sans activation.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

Reformulation stylistique

Mise à jour explicative

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

407.3.1 Perceptibles de manière tactile

Les commandes d’entrée doivent être manœuvrables et perceptibles de manière tactile sans activation.

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple

Reformulation stylistique

Mise à jour explicative

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple

Mise à jour explicative

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple

407.3.2 Touches alphabétiques

Lorsqu’elles sont fournies, les touches alphabétiques individuelles doivent être disposées selon le clavier QWERTY et les touches « F » et « J » doivent pouvoir se distinguer de manière tactile des autres touches.5

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

Reformulation stylistique

Mise à jour explicative

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

407.3.3 Touches numériques

Lorsqu’elles sont fournies, les touches numériques doivent être disposées selon le format du pavé numérique à 12 touches en ordre ascendant ou descendant. La touche du numéro cinq doit pouvoir se distinguer de manière tactile des autres touches. Lorsque les TIC fournissent un clavier avec superposition des touches alphabétiques sur les touches numériques, les liens entre les lettres et les chiffres doivent être conformes à la Recommandation E.161 de l’UIT-T (incorporée par renvoi, voir l’article 702.7.1).6

8.4.1 Touches numériques

Lorsqu’elles sont fournies, les touches numériques formant un pavé rectangulaire doivent permettre de distinguer le numéro cinq de manière tactile des autres touches du pavé numérique.

REMARQUE : La Recommandation E.161 de l’UIT-T décrit la disposition du clavier du téléphone à 12 touches et fournit des détails supplémentaires sur la forme des marqueurs tactiles.

Reformulation stylistique

Mise à jour explicative

8.4.1 Touches numériques

Lorsqu’elles sont fournies, les touches numériques formant un pavé rectangulaire doivent permettre de distinguer le numéro cinq de manière tactile des autres touches du pavé numérique.

REMARQUE : La Recommandation E.161 de l’UIT-T décrit la disposition du clavier du téléphone à 12 touches et fournit des détails supplémentaires sur la forme des marqueurs tactiles.

8.4.1 Touches numériques

Lorsqu’elles sont fournies, les touches numériques formant un pavé rectangulaire doivent permettre de distinguer le numéro cinq de manière tactile des autres touches du pavé numérique.

REMARQUE : La Recommandation E.161 de l’UIT-T décrit la disposition du clavier du téléphone à 12 touches et fournit des détails supplémentaires sur la forme des marqueurs tactiles.

8.4.1 Touches numériques

Lorsqu’elles sont fournies, les touches numériques formant un pavé rectangulaire doivent permettre de distinguer le numéro cinq de manière tactile des autres touches du pavé numérique.

REMARQUE : La Recommandation E.161 de l’UIT-T décrit la disposition du clavier du téléphone à 12 touches et fournit des détails supplémentaires sur la forme des marqueurs tactiles.

407.4 Répétition des touches

Lorsqu’un clavier doté d’une fonction de répétition des touches est fourni, le délai de répétition des touches doit être établi ou réglé à au moins 2 secondes.

5.7 Répétition des touches

Lorsque des TIC avec fonction de répétition des touches sont fournies et que la fonction de répétition des touches ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. b. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.
Reformulation stylistique

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.
Reformulation stylistique

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.

407.6 Fonctionnement

Au moins un mode de fonctionnement doit être manœuvrable d’une seule main et ne doit pas nécessiter un serrage, un pincement ou une torsion du poignet. La force requise pour activer les pièces manœuvrables doit être au maximum de 5 livres (22,2 N).

5.5.1 Moyens de fonctionnement

Lorsque les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

Reformulation stylistique

Mise à jour explicative

5.5.1 Moyens de fonctionnement

Lorsque les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

5.5.1 Moyens de fonctionnement

Lorsque les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

5.5.1 Moyens de fonctionnement

Lorsque les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

407.6 Fonctionnement

Au moins un mode de fonctionnement doit être manœuvrable d’une seule main et ne doit pas nécessiter un serrage, un pincement ou une torsion du poignet. La force requise pour activer les pièces manœuvrables doit être au maximum de 5 livres (22,2 N).

8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

Reformulation stylistique

Mise à jour explicative

8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

407.6 Fonctionnement

Au moins un mode de fonctionnement doit être manœuvrable d’une seule main et ne doit pas nécessiter un serrage, un pincement ou une torsion du poignet. La force requise pour activer les pièces manœuvrables doit être au maximum de 5 livres (22,2 N).

8.4.2.2 Force de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite une force supérieure à 22,2 N pour fonctionner, un autre moyen de fonctionnement nécessitant une force inférieure à 22,2 N doit être prévu.

Reformulation stylistique

Mise à jour explicative

8.4.2.2 Force de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite une force supérieure à 22,2 N pour fonctionner, un autre moyen de fonctionnement nécessitant une force inférieure à 22,2 N doit être prévu.

8.4.2.2 Force de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite une force supérieure à 22,2 N pour fonctionner, un autre moyen de fonctionnement nécessitant une force inférieure à 22,2 N doit être prévu.

REMARQUE : ISO 21542:2011 : Building Construction - Accessibility and Usability of the Built Environment recommande une valeur comprise entre 2,5 et 5 newtons.

Mise à jour explicative

8.4.2.2 Force de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite une force supérieure à 22,2 N pour fonctionner, un autre moyen de fonctionnement nécessitant une force inférieure à 22,2 N doit être prévu.

REMARQUE : ISO 21542:2011 [i.34]: Building Construction - Accessibility and Usability of the Built Environment recommande une valeur comprise entre 2,5 et 5 newtons.

407.7 Billets, cartes tarifaires et clés

Lorsque des billets, des cartes tarifaires ou des clés sont fournis, ils doivent avoir une orientation qui peut se distinguer de manière tactile, si l’orientation est importante pour une utilisation ultérieure du billet, de la carte tarifaire ou de la clé.

8.4.3 Clés, billets et cartes tarifaires

Lorsque les TIC fournissent des clés, des billets ou des cartes tarifaires, et que leur orientation est importante pour une utilisation ultérieure, elles doivent avoir une orientation qui est perceptible au toucher.

REMARQUE : La norme ETS 300 767 définit les indications tactiles appropriées pour les cartes plastiques.

Reformulation stylistique

Mise à jour explicative

8.4.3 Clés, billets et cartes tarifaires

Lorsque les TIC fournissent des clés, des billets ou des cartes tarifaires, et que leur orientation est importante pour une utilisation ultérieure, elles doivent avoir une orientation qui est perceptible au toucher.

REMARQUE : La norme ETS 300 767 de l’ETSI définit les indications tactiles appropriées pour les cartes plastiques.

Mise à jour explicative

8.4.3 Clés, billets et cartes tarifaires

Lorsque les TIC fournissent des clés, des billets ou des cartes tarifaires, et que leur orientation est importante pour une utilisation ultérieure, elles doivent avoir une orientation qui est perceptible au toucher.

REMARQUE : La norme ETS 300 767 de l’ETSI définit les indications tactiles appropriées pour les cartes plastiques.

8.4.3 Clés, billets et cartes tarifaires

Lorsque les TIC fournissent des clés, des billets ou des cartes tarifaires, et que leur orientation est importante pour une utilisation ultérieure, elles doivent avoir une orientation qui est perceptible au toucher.

REMARQUE : La norme ETS 300 767 [i.6] de l’ETSI définit les indications tactiles appropriées pour les cartes plastiques.

407.8.1.1 Plan vertical pour portée latérale

Lorsqu’une portée latérale est fournie, le plan de référence vertical doit avoir une longueur minimale de 1 220 mm (48 po).

8.3.2.2 Surface de plancher dégagé et espace au sol

Lorsque l’espace opérationnel fait partie intégrante des TIC, la surface de plancher dégagée devrait avoir les dimensions minimales suivantes.

Un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

Reformulation stylistique

Mise à jour explicative

8.3.2.2 Surface de plancher dégagé et espace au sol

Lorsque l’espace opérationnel fait partie intégrante des TIC, la surface de plancher dégagée devrait avoir les dimensions minimales suivantes.

Un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

8.3.4.2 Surface de plancher dégagé et espace au sol

Lorsque des TIC fixes intègrent un espace opérationnel, elles doivent prévoir une surface de plancher dégagée qui a les dimensions minimales suivantes. Un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.2 Surface de plancher dégagé et espace au sol

Lorsque des TIC fixes intègrent un espace opérationnel, elles doivent prévoir une surface de plancher dégagée qui a les dimensions minimales suivantes. Un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

407.8.1.2 Plan vertical pour portée avant

Lorsqu’une portée avant est fournie, le plan de référence vertical doit avoir une longueur minimale de 760 mm (30 po).

8.3.2.2 Surface de plancher dégagé et espace au sol

Lorsque l’espace opérationnel fait partie intégrante des TIC, la surface de plancher dégagée devrait avoir les dimensions minimales suivantes : un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

Reformulation stylistique

Mise à jour explicative

8.3.2.2 Surface de plancher dégagé et espace au sol

Lorsque l’espace opérationnel fait partie intégrante des TIC, la surface de plancher dégagée devrait avoir les dimensions minimales suivantes : un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

8.3.4.2 Surface de plancher dégagé et espace au sol

Lorsque des TIC fixes intègrent un espace opérationnel, elles doivent prévoir une surface de plancher dégagée qui a les dimensions minimales suivantes : un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.2 Surface de plancher dégagé et espace au sol

Lorsque des TIC fixes intègrent un espace opérationnel, elles doivent prévoir une surface de plancher dégagée qui a les dimensions minimales suivantes : un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

407.8.2.1 Portée latérale libre

Lorsque la pièce manœuvrable est située à 255 mm (10 po) ou moins au-delà du plan de référence vertical, la pièce manœuvrable doit avoir une hauteur maximale de 1 220 mm (48 po) et une hauteur minimale 380 mm (15 po) au-dessus du plancher.

8.3.3.2.1 Hauteur maximum de la portée latérale libre

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle, et que la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC qui est inférieur à 255 mm (10 po), la hauteur maximum de la portée latérale aux commandes essentielles devrait être inférieure ou égale à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.2.1 Hauteur maximum de la portée latérale libre

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle, et que la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC qui est inférieur à 255 mm (10 po), la hauteur maximum de la portée latérale aux commandes essentielles devrait être inférieure ou égale à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

8.3.3.1 Hauteur maximum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes et qui est inférieur à 255 mm (10 po), la hauteur maximum de la portée latérale d’au moins un de chaque type de pièces manœuvrables devrait être inférieure ou égale à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1 Hauteur maximum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes et qui est inférieur à 255 mm (10 po), la hauteur maximum de la portée latérale d’au moins un de chaque type de pièces manœuvrables devrait être inférieure ou égale à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

407.8.2.1 Portée latérale libre

Lorsque la pièce manœuvrable est située à 255 mm (10 po) ou moins au-delà du plan de référence vertical, la pièce manœuvrable doit avoir une hauteur maximale de 1 220 mm (48 po) et une hauteur minimale 380 mm (15 po) au-dessus du plancher.

8.3.3.2.2 Hauteur minimum de la portée latérale libre

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle, et que la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC qui est inférieur à 255 mm (10 po), la hauteur minimum de la portée latérale aux commandes essentielles devrait être inférieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.2.2 Hauteur minimum de la portée latérale libre

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle, et que la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC qui est inférieur à 255 mm (10 po), la hauteur minimum de la portée latérale aux commandes essentielles devrait être inférieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès.

8.3.3.2 Hauteur minimum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes qui est inférieur à 255 mm (10 po), la hauteur minimum de la portée latérale à au moins un de chaque type de pièces manœuvrables devrait être inférieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

8.3.3.2 Hauteur minimum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes et qui est inférieur à 255 mm (10 po), la hauteur minimum de la portée latérale à au moins un de chaque type de pièces manœuvrables devrait être inférieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès.

407.8.2.2 Portée latérale obstruée

Lorsque la pièce manœuvrable est située à plus de 255 mm (10 po), mais à moins de 610 mm (24 po), au-delà du plan de référence vertical, la pièce manœuvrable doit avoir une hauteur maximale de 1 170 mm (46 po) et une hauteur minimale de 380 mm (15 po) au-dessus du plancher. La pièce manœuvrable ne doit pas se trouver à plus de 610 mm (24 po) au-delà du plan de référence vertical.

8.3.3.2.3.1 Portée latérale obstruée (≤ 255 mm) (< 10 po)

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle et présente un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est inférieure ou égale à 255 mm (10 po), la hauteur maximum de la portée latérale aux commandes essentielles ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.2.3.1 Portée latérale obstruée (≤ 255 mm) (< 10 po)

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle et présente un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est inférieure ou égale à 255 mm (10 po), la hauteur maximum de la portée latérale aux commandes essentielles ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

8.3.3.3.1 Portée latérale obstruée (≤ 255 mm) (< 10 po)

Lorsque les TIC fixes présentent un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est inférieure ou égale à 255 mm (10 po), la hauteur maximum de la portée latérale à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.3.1 Portée latérale obstruée (≤ 255 mm) (< 10 po)

Lorsque les TIC fixes présentent un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est inférieure ou égale à 255 mm (10 po), la hauteur maximum de la portée latérale à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

407.8.2.2 Portée latérale obstruée

Lorsque la pièce manœuvrable est située à plus de 255 mm (10 po), mais à moins de 610 mm (24 po), au-delà du plan de référence vertical, la pièce manœuvrable doit avoir une hauteur maximale de 1 170 mm (46 po) et une hauteur minimale de 380 mm (15 po) au-dessus du plancher. La pièce manœuvrable ne doit pas se trouver à plus de 610 mm (24 po) au-delà du plan de référence vertical.

8.3.3.2.3.2 Portée latérale obstruée (≤ 610 mm) (< 24 po)

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle et présente un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est supérieure à 255 mm (10 po) et inférieure à 610 mm (24 po), la hauteur maximum de la portée latérale aux commandes essentielles ne doit pas être supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.2.3.2 Portée latérale obstruée (≤ 610 mm) (< 24 po)

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle et présente un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est supérieure à 255 mm (10 po) avec une profondeur maximale de 610 mm (24 po), la hauteur maximum de la portée latérale aux commandes essentielles ne doit pas être supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès.

Reformulation stylistique

8.3.3.3.2 Portée latérale obstruée (≤ 610 mm) (< 24 po)

Lorsque les TIC fixes présentent un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est supérieure à 255 mm (10 po) et inférieure à 610 mm (24 po), la hauteur maximum de la portée latérale à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

8.3.3.3.2 Portée latérale obstruée (≤ 610 mm) (< 24 po)

Lorsque les TIC fixes présentent un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est supérieure à 255 mm (10 po) et inférieure à 610 mm (24 po), la hauteur maximum de la portée latérale à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès.

407.8.3 Portée avant

Les pièces manœuvrables des TIC dotées d’une portée avant doivent être conformes à la clause 407.8.3.1 ou 407.8.3.2. Le plan de référence vertical doit être centré et croiser la pièce manœuvrable. Lorsqu’une portée avant permet d’atteindre au-dessus d’une partie des TIC, celle-ci doit être au maximum d’une hauteur de 865 mm (34 po).

8.3.3.1.1 Hauteur maximum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.1 Hauteur maximum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

8.3.2.1 Hauteur maximum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.2.1 Hauteur maximum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

407.8.3 Portée avant

Les pièces manœuvrables des TIC dotées d’une portée avant doivent être conformes à la clause 407.8.3.1 ou 407.8.3.2. Le plan de référence vertical doit être centré et croiser la pièce manœuvrable. Lorsqu’une portée avant permet d’atteindre au-dessus d’une partie des TIC, celle-ci doit être au maximum d’une hauteur de 865 mm (34 po).

8.3.3.1.2 Hauteur minimum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à moins de 380 mm (15 po) du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.2 Hauteur minimum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à moins de 380 mm (15 po) du plancher de l’espace d’accès.

8.3.2.2 Hauteur minimum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à moins de 380 mm (15 po) du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.2.2 Hauteur minimum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à moins de 380 mm (15 po) du plancher de l’espace d’accès.

407.8.3 Portée avant

Les pièces manœuvrables des TIC dotées d’une portée avant doivent être conformes à la clause 407.8.3.1 ou 407.8.3.2. Le plan de référence vertical doit être centré et croiser la pièce manœuvrable. Lorsqu’une portée avant permet d’atteindre au-dessus d’une partie des TIC, celle-ci doit être au maximum d’une hauteur de 865 mm (34 po).

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

407.8.3 Portée avant

Les pièces manœuvrables des TIC dotées d’une portée avant doivent être conformes à la clause 407.8.3.1 ou 407.8.3.2. Le plan de référence vertical doit être centré et croiser la pièce manœuvrable. Lorsqu’une portée avant permet d’atteindre au-dessus d’une partie des TIC, celle-ci doit être au maximum d’une hauteur de 865 mm (34 po).

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

407.8.3.1 Portée avant libre

Lorsque la pièce manœuvrable est située au bord avant de la saillie maximale dans la longueur du plan de référence vertical des TIC, la pièce manœuvrable doit avoir une hauteur maximale de 1 220 mm (48 po) et une hauteur minimale de 380 mm (15 po) pouces (380 mm) au-dessus du plancher.

8.3.3.1.1 Hauteur maximum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.1.1 Hauteur maximum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

8.3.2.1 Hauteur maximum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.2.1 Hauteur maximum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

407.8.3.1 Portée avant libre

Lorsque la pièce manœuvrable est située au bord avant de la saillie maximale dans la longueur du plan de référence vertical des TIC, la pièce manœuvrable doit avoir une hauteur maximale de 1 220 mm (48 po) et une hauteur minimale de 380 mm (15 po) au-dessus du plancher.

8.3.3.1.2 Hauteur minimum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à moins de 380 mm (15 po) du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.1.2 Hauteur minimum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à moins de 380 mm (15 po) du plancher de l’espace d’accès.

8.3.2.2 Hauteur minimum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à moins de 380 mm (15 po) du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.2.2 Hauteur minimum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à moins de 380 mm (15 po) du plancher de l’espace d’accès.

407.8.3.2 Portée avant obstruée

Lorsque la pièce manœuvrable est située au-delà du bord avant de la saillie maximale dans la longueur du plan de référence vertical des TIC, la pièce manœuvrable doit être conforme à la clause 407.8.3.2. La portée avant maximale autorisée pour une pièce manœuvrable doit être de 635 mm (25 po).

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

407.8.3.2 Portée avant obstruée

Lorsque la pièce manœuvrable est située au-delà du bord avant de la saillie maximale dans la longueur du plan de référence vertical des TIC, la pièce manœuvrable doit être conforme à la clause 407.8.3.2. La portée avant maximale autorisée pour une pièce manœuvrable doit être de 635 mm (25 po).

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

407.8.3.2.1 Hauteur de la pièce manœuvrable pour les TIC avec portée avant obstruée

La hauteur de la pièce manœuvrable doit être conforme au tableau 407.8.3.2.1.

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

407.8.3.2.1 Hauteur de la pièce manœuvrable pour les TIC avec portée avant obstruée

La hauteur de la pièce manœuvrable doit être conforme au tableau 407.8.3.2.1.

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

407.8.3.2.2 Espace pour les genoux et les pieds sous les TIC avec portée avant obstruée

L’espace pour les genoux et les pieds sous les TIC doit avoir une hauteur minimum de 685 mm (27 po), une profondeur maximum de 635 mm (25 po) et doit être dégagé de tout obstacle.

EXCEPTIONS :

  1. L’espace pour les pieds doit fournir une hauteur dégagée de 230 mm (9 po) au-dessus du plancher et une profondeur maximale dégagée de 150 mm (6 po) du plan de référence vertical vers le bord avant des TIC.
  2. Avec une profondeur maximale de 150 mm (6 po) du plan de référence vertical au bord avant des TIC, l’espace entre le minimum de 230 mm (9 po) et de 685 mm (27 po) au-dessus du plancher doit pouvoir être réduit à un taux de 25 mm (1 po) de profondeur pour chaque 150 mm (6 po) de hauteur.7

8.3.2.4 Largeur libre pour les genoux et les pieds

Lorsque l’espace sous un obstacle faisant partie intégrante des TIC fait partie de l’espace d’accès, la largeur libre devrait être d’au moins 760 mm (30 po).

Reformulation stylistique

Mise à jour explicative

8.3.2.4 Largeur libre pour les genoux et les pieds

Lorsque l’espace sous un obstacle faisant partie intégrante des TIC fait partie de l’espace d’accès, la largeur libre devrait être d’au moins 760 mm (30 po).

8.3.2.4 Largeur libre pour les genoux et les pieds

Lorsque l’espace sous un obstacle faisant partie intégrante des TIC fixes fait partie de l’espace d’accès, la largeur libre doit être d’au moins 760 mm (30 po).

Reformulation stylistique

Changement fonctionnel

8.3.2.4 Largeur libre pour les genoux et les pieds

Lorsque l’espace sous un obstacle faisant partie intégrante des TIC fixes fait partie de l’espace d’accès, la largeur libre doit être d’au moins 760 mm (30 po).

407.8.3.2.2 Espace pour les genoux et les pieds sous les TIC avec portée avant obstruée

L’espace pour les genoux et les pieds sous les TIC doit avoir une hauteur minimum de 685 mm (27 po), une profondeur maximum de 635 mm (25 po), une largeur de 760 mm (30 po) et doit être dégagé de tout obstacle.

EXCEPTIONS :

  1. L’espace pour les pieds doit fournir une hauteur dégagée de 230 mm (9 po) au-dessus du plancher et une profondeur maximale dégagée de 150 mm (6 po) du plan de référence vertical vers le bord avant des TIC.
  2. Avec une profondeur maximale de 150 mm (6 po) du plan de référence vertical au bord avant des TIC, l’espace entre le minimum de 230 mm (9 po) et de 685 mm (27 po) au-dessus du plancher doit pouvoir être réduit à un taux de 25 mm (1 po) de profondeur pour chaque 150 mm (6 po) de hauteur.7b

8.3.2.5 Espace libre pour les pieds

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle d’au moins 230 mm (9 po) au-dessus du plancher est considéré comme un espace libre pour les pieds et il devrait :

  1. avoir une largeur d’au plus 635 mm (25 po) sous tout l’obstacle;
  2. fournir un espace d’au moins 430 mm (17 po) de profondeur et 230 mm (9 po) au-dessus du plancher sous l’obstacle;
  3. être à une distance d’au plus 150 mm (6 po) de toute obstruction à 230 mm (9 po) au-dessus du plancher.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.5 Espace libre pour les pieds

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle d’au moins 230 mm (9 po) au-dessus du plancher est considéré comme un espace libre pour les pieds et il devrait :

  1. avoir une largeur d’au plus 635 mm (25 po) sous tout l’obstacle;
  2. procurer un espace d’au moins 430 mm (17 po) de profondeur et 230 mm (9 po) au-dessus du plancher sous l’obstacle;
  3. être à une distance d’au plus 150 mm (6 po) de toute obstruction à 230 mm (9 po) au-dessus du plancher.

8.3.2.5 Espace libre pour les pieds

Lorsqu’un obstacle fait partie intégrante des TIC fixes, un espace sous l’obstacle d’au moins 230 mm (9 po) au-dessus du plancher est considéré comme un espace libre pour les pieds et il doit :

  1. avoir une largeur d’au plus 635 mm (25 po) sous tout l’obstacle;
  2. procurer un espace d’au moins 430 mm (17 po) de profondeur et 230 mm (9 po) au-dessus du plancher sous l’obstacle;
  3. être à une distance d’au plus 150 mm (6 po) de toute obstruction à 230 mm (9 po) au-dessus du plancher.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

8.3.2.5 Espace libre pour les pieds

Lorsqu’un obstacle fait partie intégrante des TIC fixes, un espace sous l’obstacle d’au moins 230 mm (9 po) au-dessus du plancher est considéré comme un espace libre pour les pieds et il doit :

  1. avoir une largeur d’au plus 635 mm (25 po) sous tout l’obstacle;
  2. procurer un espace d’au moins 430 mm (17 po) de profondeur et 230 mm (9 po) au-dessus du plancher sous l’obstacle;
  3. être à une distance d’au plus 150 mm (6 po) de toute obstruction à 230 mm (9 po) au-dessus du plancher.

407.8.3.2.2 Espace pour les genoux et les pieds sous les TIC avec portée avant obstruée

L’espace pour les genoux et les pieds sous les TIC doit avoir une hauteur minimum de 685 mm (27 po), une profondeur maximum de 635 mm (25 po) et doit être dégagé de tout obstacle.

EXCEPTIONS :

  1. L’espace pour les pieds doit fournir une hauteur dégagée de 230 mm (9 po) au-dessus du plancher et une profondeur maximale dégagée de 150 mm (6 po) du plan de référence vertical vers le bord avant des TIC.
  2. Avec une profondeur maximale de 150 mm (6 po) du plan de référence vertical au bord avant des TIC, l’espace entre le minimum de 230 mm (9 po) et de 685 mm (27 po) au-dessus du plancher doit pouvoir être réduit à un taux de 25 mm (1 po) de profondeur pour chaque 150 mm (6 po) de hauteur.8

8.3.2.6 Espace libre pour les genoux

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (27 po) au-dessus du plancher est considéré comme un espace libre pour les genoux et il devrait :

  1. être à une distance pas plus de 635 mm (25 po) sous toute obstruction à 230 mm (9 po) de hauteur au-dessus du plancher;
  2. avoir une largeur d’au moins 280 mm (11 po) sous l’obstacle et une hauteur de 230 mm (9 po) au-dessus du plancher;
  3. avoir une largeur d’au moins 205 mm (8 po) sous l’obstacle et une hauteur de 685 mm (27 po) au-dessus du plancher;

se situer entre 230 mm (9 po) et 685 mm (27 po) au-dessus du plancher pour pouvoir être réduit à une profondeur de 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.6 Espace libre pour les genoux

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (27 po) au-dessus du plancher est considéré comme un espace libre pour les genoux et il devrait :

  1. être à une distance pas plus de 635 mm (25 po) sous toute obstruction à 230 mm (9 po) de hauteur au-dessus du plancher;
  2. avoir une largeur d’au moins 280 mm (11 po) sous l’obstacle et une hauteur de 230 mm (9 po) au-dessus du plancher;
  3. avoir une largeur d’au moins 205 mm (8 po) sous l’obstacle et une hauteur de 685 mm (27 po) au-dessus du plancher;
  4. pouvoir être réduit à une profondeur de 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.
Reformulation stylistique

8.3.2.6 Espace libre pour les genoux

Lorsqu’un obstacle fait partie intégrante des TIC fixes, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po)9 au-dessus du plancher est considéré comme un espace libre pour les genoux et il doit :

  1. être à une distance pas plus de 635 mm (25 po) sous toute obstruction à 230 mm (9 po) de hauteur au-dessus du plancher;
  2. avoir une largeur d’au moins 280 mm (11 po) sous l’obstacle et une hauteur de 230 mm (9 po) au-dessus du plancher;
  3. avoir une largeur d’au moins 205 mm (8 po) sous l’obstacle et une hauteur de 685 mm (27 po) au-dessus du plancher;
  4. pouvoir être réduit à une profondeur de 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.6 Espace libre pour les genoux

Lorsqu’un obstacle fait partie intégrante des TIC fixes, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po)10 au-dessus du plancher est considéré comme un espace libre pour les genoux et il doit :

  1. être à une distance pas plus de 635 mm (25 po) sous toute obstruction à 230 mm (9 po) de hauteur au-dessus du plancher;
  2. avoir une largeur d’au moins 280 mm (11 po) sous l’obstacle et une hauteur de 230 mm (9 po) au-dessus du plancher;
  3. avoir une largeur d’au moins 205 mm (8 po) sous l’obstacle et une hauteur de 685 mm (27 po) au-dessus du plancher;
  4. pouvoir être réduit à une profondeur de 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.

Liste des tableaux

408 Écran d’affichage

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

408.2 Visibilité

Lorsque des TIC fixes sont dotées d’un ou de plusieurs écrans d’affichage, au moins un de chaque type d’écran d’affichage doit être visible d’un point situé à 1 015 mm (40 po) au-dessus de l’espace au plancher à partir d’où l’écran d’affichage est visionné.

8.3.4 Visibilité

Lorsque l’espace opérationnel fait partie intégrante des TIC et qu’un écran d’affichage est fourni, l’information à l’écran doit être lisible à partir d’un point situé à 1 015 mm (40 po) au-dessus du centre du plancher de l’espace opérationnel (à la clause 8.3.2.2).

REMARQUE : Cette disposition vise à ce que l’information à l’écran soit lisible par des utilisateurs ayant une vision normale et des compétences linguistiques appropriées, lorsqu’ils sont assis dans un fauteuil roulant.

Reformulation stylistique

Mise à jour explicative

8.3.4 Visibilité

Lorsque l’espace opérationnel fait partie intégrante des TIC et qu’un écran d’affichage est fourni, l’information à l’écran doit être lisible à partir d’un point situé à 1 015 mm (40 po) au-dessus du centre du plancher de l’espace opérationnel (à la clause 8.3.2.2).

REMARQUE : Cette disposition vise à ce que l’information à l’écran soit lisible par des utilisateurs ayant une vision normale et des compétences linguistiques appropriées, lorsqu’ils sont assis dans un fauteuil roulant.

8.3.5 Visibilité

Lorsque les TIC fixes fournissent un ou plusieurs écrans d’affichage, au moins un de chaque type d’écran d'affichage doit être positionné de telle sorte que les renseignements à l'écran soient lisibles depuis un point situé à 1 015 mm (40 pouces) au-dessus du centre du plancher de l’espace opérationnel.

REMARQUE : Cette exigence vise à ce que l’information à l’écran soit lisible par des utilisateurs ayant une vision normale et des compétences linguistiques appropriées, lorsqu’ils sont assis dans un fauteuil roulant.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.5 Visibilité

Lorsque les TIC fixes fournissent un ou plusieurs écrans d’affichage, au moins un de chaque type d’écran d'affichage doit être positionné de telle sorte que les renseignements à l'écran soient lisibles depuis un point situé à 1 015 mm (40 pouces) au-dessus du centre du plancher de l’espace opérationnel.

REMARQUE : Cette exigence vise à ce que l’information à l’écran soit lisible par des utilisateurs ayant une vision normale et des compétences linguistiques appropriées, lorsqu’ils sont assis dans un fauteuil roulant.

Liste des tableaux

409 Indicateurs d’état

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

409.1 Généralités

Lorsqu’ils sont fournis, les indicateurs d’état doivent être perceptibles visuellement ainsi que de manière tactile ou auditive.

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

Reformulation stylistique

Mise à jour explicative

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

Mise à jour explicative

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

409.1 Généralités

Lorsqu’ils sont fournis, les indicateurs d’état doivent être perceptibles visuellement ainsi que de manière tactile ou auditive.

5.6.2 État visuel

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que la commande ne se présente pas visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement permettant de déterminer visuellement l’état de la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. Un indicateur visuel d’état sur un clavier est un exemple de détermination de l’état d’une commande.

Reformulation stylistique

Mise à jour explicative

5.6.2 État visuel

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que la commande ne se présente pas visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement permettant de déterminer visuellement l’état de la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. Un indicateur visuel d’état sur un clavier est un exemple de détermination de l’état d’une commande.

5.6.2 État visuel

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de la commande ne se présente pas visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement permettant de déterminer visuellement l’état de la commande.

Mise à jour explicative

5.6.2 État visuel

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de la commande ne se présente pas visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement permettant de déterminer visuellement l’état de la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. Un indicateur visuel d’état sur un clavier est un exemple de détermination de l’état d’une commande.

Liste des tableaux

410 Codage par couleurs

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

410.1 Généralités

Lorsqu’ils sont fournis, les codes de couleurs ne doivent pas être utilisés comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

8.1.3 Couleur

Lorsque les TIC sont dotées d’aspects matériels utilisant la couleur, la couleur n’est pas utilisée comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

Reformulation stylistique

8.1.3 Couleur

Lorsque les TIC sont dotées d’aspects matériels utilisant la couleur, la couleur n’est pas utilisée comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

8.1.3 Couleur

Lorsque les TIC sont dotées d’aspects matériels utilisant la couleur, la couleur n’est pas utilisée comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

8.1.3 Couleur

Lorsque les TIC sont dotées d’aspects matériels utilisant la couleur, la couleur n’est pas utilisée comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

Liste des tableaux

412 TIC avec communication vocale bidirectionnelle

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

412.2.1 Gain de volume pour les téléphones filaires

Un gain de volume conforme à la norme 47 CFR 68.317 doit être fourni sur les téléphones filaires analogiques et numériques.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

Reformulation stylistique

Mise à jour explicative

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

412.2.1 Gain de volume pour les téléphones filaires

Un gain de volume conforme à la norme 47 CFR 68.317 doit être fourni sur les téléphones filaires analogiques et numériques.11

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

412.2.2 Gain de volume pour les TIC non filaires

Une méthode d’augmentation du volume doit être fournie pour les TIC non filaires.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

412.2.2 Gain de volume pour les TIC non filaires

Une méthode d’augmentation du volume doit être fournie pour les TIC non filaires.12

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

412.3.1 Combinés sans fil

Les TIC sous forme de combinés sans fil doivent être conformes à la norme ANSI/IEEE C63.19-2011 (incorporée par renvoi, voir l’article 702.5.1).13

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

Reformulation stylistique

Mise à jour explicative

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

Mise à jour explicative

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

412.3.2 Combinés filaires

Les TIC sous forme de combinés filaires, y compris les combinés sans fil, doivent être conformes à la norme TIA-1083-B (incorporée par renvoi, voir l’article 702.9.1).14

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille et qui porte le symbole « T » spécifié dans la norme ETS 300 381, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1.

REMARQUE : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

Reformulation stylistique

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille et qui porte le symbole « T » spécifié dans la norme ETS 300 381 de l’ETSI, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 de l’ETSI et doit porter le symbole « T » spécifié dans la norme ETS 300 381 de l’ETSI.

REMARQUE 1 : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

REMARQUE 2 : Le couplage magnétique est également appelé couplage inductif pour bobine en T.

Reformulation stylistique

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 de l’ETSI et doit porter le symbole « T » spécifié dans la norme ETS 300 381 de l’ETSI.

REMARQUE 1 : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

REMARQUE 2 : Le couplage magnétique est également appelé couplage inductif pour bobine en T.

412.4 Codage numérique de la parole

Les TIC contenues dans des réseaux IP doivent transmettre et recevoir des messages vocaux codés de façon numérique de la manière spécifiée par la Recommandation G.722.2 de l’UTI-T (incorporée par référence, voir l’article 702.7.2) ou par la norme RFC 6716 de l’IETF (incorporée par renvoi, voir l’article 702.8.1).15

6.1 Largeur de bande sonore pour la parole (recommandation informative)

Lorsque les TIC permettent la communication vocale bidirectionnelle, pour offrir une bonne qualité sonore, elles devraient pouvoir coder et décoder la communication vocale bidirectionnelle selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

REMARQUE 1 : aux fins de l’interopérabilité, la Recommandation G.722 de l’UIT-T est largement utilisée.

REMARQUE 2 : lorsqu’il y a négociation de codecs, d’autres codecs normalisés tels que la Recommandation G.722.2 de l’UIT-T sont parfois utilisés afin d’éviter le transcodage.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.1 Largeur de bande sonore pour la parole

Lorsque les TIC permettent la communication vocale bidirectionnelle, pour offrir une bonne qualité sonore, elles doivent pouvoir coder et décoder la communication vocale bidirectionnelle selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

REMARQUE 1 : aux fins de l’interopérabilité, la Recommandation G.722 de l’UIT-T est largement utilisée.

REMARQUE 2 : lorsqu’il y a négociation de codecs, d’autres codecs normalisés tels que la Recommandation G.722.2 de l’UIT-T sont parfois utilisés afin d’éviter le transcodage.

Changement fonctionnel

6.1 Largeur de bande sonore pour la parole

Lorsque les TIC permettent la communication vocale bidirectionnelle, pour offrir une bonne qualité sonore, elles doivent pouvoir coder et décoder la communication vocale bidirectionnelle selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

REMARQUE 1 : aux fins de l’interopérabilité, la Recommandation G.722 de l’UIT-T est largement utilisée.

REMARQUE 2 : lorsqu’il y a négociation de codecs, d’autres codecs normalisés tels que la Recommandation G.722.2 de l’UIT-T sont parfois utilisés afin d’éviter le transcodage.

6.1 Largeur de bande sonore pour la parole

Lorsque les TIC permettent la communication vocale bidirectionnelle, pour offrir une bonne qualité sonore, elles doivent pouvoir coder et décoder la communication vocale bidirectionnelle selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

REMARQUE 1 : aux fins de l’interopérabilité, la Recommandation G.722 de l’UIT-T est largement utilisée.

REMARQUE 2 : lorsqu’il y a négociation de codecs, d’autres codecs normalisés tels que la Recommandation G.722.2 de l’UIT-T sont parfois utilisés afin d’éviter le transcodage.

412.5 Fonctionnalité texte en temps réel

[Réservé].16

Voir les exigences relatives au TTR dans EN 301 549 V1.1.1 (2014), chapitre 6, ci-dessous.Voir les exigences relatives au TTR dans EN 301 549 V2.1.2 (2018), chapitre 6, ci-dessous.Voir les exigences relatives au TTR dans EN 301 549 V3.1.1 (2019), chapitre 6, ci-dessous.Voir les exigences relatives au TTR dans EN 301 549 V3.2.1 (2021), chapitre 6, ci-dessous.

412.6 Identification de l’appelant

Lorsqu’elle est fournie, la fonction d’identification de l’appelant ou de télécommunications similaire doit être visible et audible.17

6.3 Identification de l’appelant

Lorsque les TIC sont dotées de la fonction d’identification de l’appelant ou sont d’une fonction de télécommunications similaire, la fonction d’identification de l’appelant ou de télécommunications similaire doit être offerte en mode textuel et dans au moins un autre mode.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.3 Identification de l’appelant

Lorsque les TIC sont dotées de la fonction d’identification de l’appelant ou sont d’une fonction de télécommunications similaire, la fonction d’identification de l’appelant ou de télécommunications similaire doit être offerte en mode textuel et dans au moins un autre mode.

6.3 Identification de l’appelant

Lorsque les TIC sont dotées de la fonction d’identification de l’appelant ou sont d’une fonction de télécommunications similaire, la fonction d’identification de l’appelant ou de télécommunications similaire doit être offerte en mode textuel

ainsi qu’être déterminable par un programme informatique, à moins que la fonction ne soit restreinte.

Changement fonctionnel

6.3 Identification de l’appelant

Lorsque les TIC sont dotées de la fonction d’identification de l’appelant ou sont d’une fonction de télécommunications similaire, la fonction d’identification de l’appelant ou de télécommunications similaire doit être offerte en mode textuel ainsi qu’être déterminable par un programme informatique, à moins que la fonction ne soit restreinte.

412.7 Communication vidéo

Lorsque les TIC sont dotées d’une fonctionnalité vidéo en temps réel, la qualité de la vidéo doit être suffisante pour prendre en charge la communication au moyen du langage des signes.18

6.5.1 Généralités (information)

La clause 6.5 (Communication vidéo) décrit les exigences fonctionnelles prenant en charge les utilisateurs qui communiquent en langage gestuel et en lecture labiale. À cette fin, une résolution de CIF (Common Intermediate Format), une vitesse de défilement d’au moins 20 images par seconde et un écart entre le son et la vidéo de 100 ms ou moins permettent d’obtenir une bonne exploitabilité.

Lorsque la résolution passe au format QCIF (Quarter Common Intermediate Format) et que la vitesse de défilement baisse à 12 images par seconde, la communication est encore possible avec certaines restrictions.

La baisse de résolution perturbe moins la perception du langage gestuel et de la lecture labiale que la baisse de la vitesse de défilement des images.

Le retard peut être un problème lié à la communication vidéo. Des valeurs d’écart inférieur à 0,4 s avec une augmentation allant jusqu’à 0,1 s sont préférables. Des valeurs d’écart supérieures à 0,8 s peuvent nuire à la conversation gestuelle. L’écart global dépend de plusieurs facteurs, dont le délai de transmission du réseau et de traitement vidéo. Voilà pourquoi il est impossible d’établir une exigence testable des valeurs minimales d’écart global.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.5.1 Généralités (information)

La clause 6.5 (Communication vidéo) décrit les exigences fonctionnelles prenant en charge les utilisateurs qui communiquent en langage gestuel et en lecture labiale. À cette fin, une résolution de CIF (Common Intermediate Format), une vitesse de défilement d’au moins 20 images par seconde et un écart entre le son et la vidéo de 100 ms ou moins permettent d’obtenir une bonne exploitabilité.

Lorsque la résolution passe au format QCIF (Quarter Common Intermediate Format) et que la vitesse de défilement baisse à 12 images par seconde, la communication est encore possible avec certaines restrictions.

La baisse de résolution perturbe moins la perception du langage gestuel et de la lecture labiale que la baisse de la vitesse de défilement des images.

Le retard peut être un problème lié à la communication vidéo. Des valeurs d’écart inférieur à 0,4 s avec une augmentation allant jusqu’à 0,1 s sont préférables. Des valeurs d’écart supérieures à 0,8 s peuvent nuire à la conversation gestuelle. L’écart global dépend de plusieurs facteurs, dont le délai de transmission du réseau et de traitement vidéo. Voilà pourquoi il est impossible d’établir une exigence testable des valeurs minimales d’écart global.

6.5.1 Généralités (information)

La clause 6.5 (Communication vidéo) décrit les exigences fonctionnelles prenant en charge les utilisateurs qui communiquent en langage gestuel et en lecture labiale. Pour ces utilisateurs, une résolution au moins QVGA (320 x 240), une vitesse de défilement d’au moins 20 images par seconde et un écart entre le son et la vidéo de 100 ms ou moins permettent d’obtenir une bonne exploitabilité.

L'augmentation de la résolution et de la vitesse de défilement des images améliore encore plus le langage des signes (en particulier l'épellation digitale) et la lecture labiale, la vitesse de défilement des images étant plus importante que la résolution.

Les écarts temporels entre l’audio et la vidéo (asynchronicité) peuvent avoir un impact important sur la lecture labiale - une vidéo en retard sur l’audio ayant un effet négatif plus important. La latence de bout en bout peut être un problème dans la communication vidéo (des signes). Des valeurs d’écart inférieur à 400 ms avec une augmentation allant jusqu’à 100 ms sont préférables. L’écart global dépend de plusieurs facteurs, dont le délai de transmission du réseau et de traitement vidéo. Voilà pourquoi il est impossible d’établir une exigence testable des valeurs minimales d’écart global. REMARQUE : La Recommandation UIT-T F.703 définit et donne les exigences relatives à la conversation totale qui a trait à l’intégration de l’audio, au TTR et à la vidéo dans une connexion d'utilisateur unique.

Changement fonctionnel

Mise à jour explicative

Reformulation stylistique

6.5.1 Généralités (information)

La clause 6.5 (Communication vidéo) décrit les exigences fonctionnelles prenant en charge les utilisateurs qui communiquent en langage gestuel et en lecture labiale. Pour ces utilisateurs, une résolution au moins QVGA (320 x 240), une vitesse de défilement d’au moins 20 images par seconde et un écart entre le son et la vidéo de 100 ms ou moins permettent d’obtenir une bonne exploitabilité.

L'augmentation de la résolution et de la vitesse de défilement des images améliore encore le langage des signes (en particulier l'épellation digitale) et la lecture labiale, la vitesse de défilement des images étant plus importante que la résolution.

Les écarts temporels entre l’audio et la vidéo (asynchronicité) peuvent avoir un impact important sur la lecture labiale - une vidéo en retard sur l’audio ayant un effet négatif plus important. La latence de bout en bout peut être un problème dans la communication vidéo (des signes). Des valeurs d’écart inférieur à 400 ms avec une augmentation allant jusqu’à 100 ms sont préférables. L’écart global dépend de plusieurs facteurs, dont le délai de transmission du réseau et de traitement vidéo. Voilà pourquoi il est impossible d’établir une exigence testable des valeurs minimales d’écart global.
REMARQUE : La Recommandation UIT-T F.703 définit et donne les exigences relatives à la conversation totale qui a trait à l’intégration de l’audio, au TTR et à la vidéo dans une connexion d'utilisateur unique.

412.7 Communication vidéo

Lorsque les TIC sont dotées d’une fonctionnalité vidéo en temps réel, la qualité de la vidéo doit être suffisante pour prendre en charge la communication au moyen du langage des signes.19

6.5.2 Résolution

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge au moins la résolution QCIF;
  2. doivent de préférence prendre en charge au moins la résolution CIF.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.5.2 Résolution

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge au moins la résolution QCIF;
  2. doivent de préférence prendre en charge au moins la résolution CIF.

6.5.2 Résolution

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge au moins la résolution QVGA;
  2. doivent de préférence prendre en charge au moins la résolution VGA.
Changement fonctionnel

6.5.2 Résolution

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge au moins la résolution QVGA;
  2. doivent de préférence prendre en charge au moins la résolution VGA.

412.7 Communication vidéo

Lorsque les TIC sont dotées d’une fonctionnalité vidéo en temps réel, la qualité de la vidéo doit être suffisante pour prendre en charge la communication au moyen du langage des signes.20

6.5.3 Vitesse de défilement des images

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge une vitesse de défilement d’au moins 12 images par seconde (IPS);
  2. doivent de préférence prendre en charge une vitesse de défilement d’au moins 20 images par seconde (IPS) avec ou sans langage gestuel dans le flux vidéo.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.5.3 Vitesse de défilement des images

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge une vitesse de défilement d’au moins 12 images par seconde (IPS);
  2. doivent de préférence prendre en charge une vitesse de défilement d’au moins 20 images par seconde (IPS) avec ou sans langage gestuel dans le flux vidéo.

6.5.3 Vitesse de défilement des images

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge une vitesse de défilement d’au moins 20 images par seconde (IPS);
  2. doivent de préférence prendre en charge une vitesse de défilement d’au moins 30 images par seconde (IPS) avec ou sans langage gestuel dans le flux vidéo.
Changement fonctionnel

6.5.3 Vitesse de défilement des images

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge une vitesse de défilement d’au moins 20 images par seconde (IPS);
  2. doivent de préférence prendre en charge une vitesse de défilement d’au moins 30 images par seconde (IPS) avec ou sans langage gestuel dans le flux vidéo.
Reformulation stylistique

412.7 Communication vidéo

Lorsque les TIC sont dotées d’une fonctionnalité vidéo en temps réel, la qualité de la vidéo doit être suffisante pour prendre en charge la communication au moyen du langage des signes.21

6.5.4 Synchronisation entre le son et la vidéo

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles devraient présenter à l’utilisateur un écart temporel maximal de 100 ms entre la parole et la vidéo.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.5.4 Synchronisation entre le son et la vidéo

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles devraient présenter à l’utilisateur un écart temporel maximal de 100 ms entre la parole et la vidéo.

6.5.4 Synchronisation entre le son et la vidéo

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles doivent présenter à l’utilisateur un écart temporel maximal de 100 ms entre la parole et la vidéo. REMARQUE : Des recherches récentes montrent que si l’audio mène la vidéo, l’intelligibilité en souffre beaucoup plus que dans le cas inverse.

Changement fonctionnel

Mise à jour explicative

6.5.4 Synchronisation entre le son et la vidéo

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles doivent présenter à l’utilisateur un écart temporel maximal de 100 ms entre la parole et la vidéo. REMARQUE : Des recherches récentes montrent que si l’audio mène la vidéo, l’intelligibilité en souffre beaucoup plus que dans le cas inverse.

Liste des tableaux

413 Technologies de traitement des sous-titres codés

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

413.1.1 Décodage et affichage des sous-titres codés

Les lecteurs et les écrans doivent décoder les sous-titres et prendre en charge l’affichage des sous-titres.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

Reformulation stylistique

Mise à jour explicative

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

Changement fonctionnel

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

REMARQUE 3 : La clause 7.1.1 fait référence à la capacité du lecteur d’afficher des sous-titres. Les clauses 9.1.2.2, 10.1.2.2 et 11.1.2.2 font référence à la fourniture de sous-titres pour le contenu (la vidéo).

Mise à jour explicative

413.1.2 Transmission des données de sous-titres codés

Les données des sous-titres doivent passer par le câblage et l’équipement auxiliaire.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

413.1.2 Transmission des données de sous-titres codés

Les données des sous-titres doivent passer par le câblage et l’équipement auxiliaire.

7.1.3 Préservation du sous-titrage

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

D’autres aspects d’affichage du texte (p. ex. le positionnement à l’écran, la couleur et le style du texte ainsi que la police de caractères) peuvent être significatifs selon les conventions régionales. La modification de ces aspects pourrait en changer le sens et devrait être évitée dans la mesure du possible.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

7.1.3 Préservation du sous-titrage

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

D’autres aspects d’affichage du texte (p. ex. le positionnement à l’écran, la couleur et le style du texte ainsi que la police de caractères) peuvent être significatifs selon les conventions régionales. La modification de ces aspects pourrait en changer le sens et devrait être évitée dans la mesure du possible.

7.1.3 Préservation du sous-titrage

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

D’autres aspects d’affichage du texte (p. ex. le positionnement à l’écran, la couleur et le style du texte ainsi que la police de caractères) peuvent être significatifs selon les conventions régionales. La modification de ces aspects pourrait en changer le sens et devrait être évitée dans la mesure du possible.

7.1.3 Préservation du sous-titrage

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

D’autres aspects d’affichage du texte (p. ex. le positionnement à l’écran, la couleur et le style du texte ainsi que la police de caractères) peuvent être significatifs selon les conventions régionales. La modification de ces aspects pourrait en changer le sens et devrait être évitée dans la mesure du possible.

Liste des tableaux

414 Technologies de traitement de la description audio

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

414.1.1 Syntoniseurs de télévision numérique

Les syntoniseurs de télévision numérique doivent prévoir un traitement de la description audio conforme à la partie 5 de la norme de télévision numérique ATSC A/53 (2014) (incorporée par renvoi, voir l’article 702.2.1). Les syntoniseurs de télévision numérique doivent traiter la description audio lorsqu’elle est codée comme un service audio associé aux malvoyants qui est fourni sous forme de combinaison complète de programmes contenant une description audio conformément à la norme ATSC A/53.22

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

414.1.2 Autres TIC

Les TIC autres que les syntoniseurs de télévision numérique doivent prévoir un traitement de la description audio.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

Reformulation stylistique

Mise à jour explicative

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

Liste des tableaux

415 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

415.1.1 Commandes pour les sous-titres

Lorsque les TIC sont dotées de pièces manœuvrables pour le réglage du volume, elles doivent aussi être dotées de pièces manœuvrables pour la sélection des sous-titres.23

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Reformulation stylistique

Mise à jour explicative

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

415.1.2 Commandes pour les descriptions audio

Lorsque les TIC sont dotées de pièces manœuvrables pour la sélection des programmes, elles doivent aussi être dotées de pièces manœuvrables pour la sélection de la description audio.24

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour contrôler les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Reformulation stylistique

Mise à jour explicative

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour contrôler les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour contrôler les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour contrôler les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Liste des tableaux

Chapitre 5 - Logiciels

501 Généralités

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

501.1 Portée

Les exigences du chapitre 5 s’appliquent aux logiciels lorsque l’exige le chapitre 2 de la norme 508 (Exigences relatives à la portée), le chapitre 2 des directives 255 (Exigences relatives à la portée), et lorsqu’il en est fait mention autrement dans tout autre chapitre de la norme 508 révisée ou des directives 255 révisées.

EXCEPTION : Lorsque des applications Web n’ont pas accès aux services d’accessibilité de la plateforme et n’incluent pas les composants qui ont accès aux services d’accessibilité de la plateforme, ils n’ont pas être conformes à la clause 502 ou 503, à condition qu’ils soient conformes aux critères de succès de niveau A et de niveau AA et aux exigences de conformité dans les WCAG 2.0 (incorporées par renvoi, voir l’article 702.10.1).

Les chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.0 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).

Mise à jour explicative

Reformulation stylistique

Les chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).Changement fonctionnelLes chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).Les chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).

Liste des tableaux

502 Interopérabilité avec technologie d’assistance

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

502.2.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Les logiciels de la plateforme doivent permettre à l’utilisateur de contrôler les caractéristiques de la plateforme qui sont définies dans la documentation de celle-ci comme étant des caractéristiques d’accessibilité.

11.4.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Lorsque le logiciel est une plateforme, il doit offrir des modes de fonctionnement suffisants permettant à l’utilisateur de contrôler les caractéristiques d’accessibilité de la plateforme documentées comme étant destinées aux utilisateurs.

Reformulation stylistique

11.6.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Lorsque le logiciel est une plateforme, il doit offrir des modes de fonctionnement suffisants permettant à l’utilisateur de contrôler les caractéristiques d’accessibilité de la plateforme documentées comme étant destinées aux utilisateurs.

Changement de numérotation

11.6.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Lorsque le logiciel est une plateforme, il doit offrir des modes de fonctionnement suffisants permettant à l’utilisateur de contrôler les caractéristiques d’accessibilité de la plateforme documentées comme étant destinées aux utilisateurs.

11.6.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Lorsque le logiciel est une plateforme, il doit offrir des modes de fonctionnement suffisants permettant à l’utilisateur de contrôler les caractéristiques d’accessibilité de la plateforme documentées comme étant destinées aux utilisateurs.

502.2.2 Aucune perturbation des caractéristiques d'accessibilité

Les logiciels ne doivent pas perturber les caractéristiques de la plateforme qui sont définies dans la documentation de celle-ci comme étant des caractéristiques d’accessibilité.

11.4.2 Aucune perturbation des caractéristiques d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, elle ne doit pas perturber les caractéristiques d’accessibilité documentées qui sont définies dans la documentation de la plateforme, sauf si l’utilisateur en fait la demande pendant le fonctionnement du logiciel.

Reformulation stylistique

Mise à jour explicative

11.6.2 Aucune perturbation des caractéristiques d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, elle ne doit pas perturber les caractéristiques d’accessibilité documentées qui sont définies dans la documentation de la plateforme, sauf si l’utilisateur en fait la demande pendant le fonctionnement du logiciel.

Changement de numérotation

11.6.2 Aucune perturbation des caractéristiques d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, elle ne doit pas perturber les caractéristiques d’accessibilité documentées qui sont définies dans la documentation de la plateforme, sauf si l’utilisateur en fait la demande pendant le fonctionnement du logiciel.

11.6.2 Aucune perturbation des caractéristiques d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, elle ne doit pas perturber les caractéristiques d’accessibilité documentées qui sont définies dans la documentation de la plateforme, sauf si l’utilisateur en fait la demande pendant le fonctionnement du logiciel.

502.3 Services d’accessibilité

Les logiciels et les outils logiciels de la plateforme fournis par le développeur de celle-ci doivent fournir un ensemble documenté de services d’accessibilité qui prennent en charge les applications exécutées sur la plateforme pour interagir avec la technologie d’assistance et doivent être conformes à la clause 502.3. Les applications qui sont également des plateformes doivent exposer les services d’accessibilité de la plateforme sous-jacents ou mettre en œuvre d’autres services d’accessibilité documentés.

11.3.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur

Les logiciels de plateforme doivent fournir un ensemble de services de plateforme documentés qui permettent aux logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme d’interagir avec la technologie d’assistance.

Le logiciel de la plateforme doit prendre en charge les exigences 11.3.2.5 à 11.3.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.3.2.5 à 11.3.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.3.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Elles définissent la fonctionnalité minimale des logiciels fournissant des interfaces utilisateur lors de l’utilisation des services de la plateforme.

REMARQUE 2 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 3 : Les services d’interface utilisateur qui fournissent par défaut un soutien à l’accessibilité sont considérés comme faisant partie des services fournis pour se conformer à cette clause (par exemple, le service de création d’un nouvel élément d’interface utilisateur fournit un rôle, un état, une limite, un nom et une description).

REMARQUE 4 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

REMARQUE 5 : Dans des environnements de programme informatique particuliers, les attributs techniques associés aux propriétés de l’interface utilisateur décrites dans les clauses 11.3.2.5 à 11.3.2.17 peuvent avoir des noms différents de ceux utilisés dans ces clauses.

Reformulation stylistique

Mise à jour explicative

11.5.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur

Les logiciels de plateforme doivent fournir un ensemble de services de plateforme documentés qui permettent aux logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme d’interagir avec la technologie d’assistance.

Le logiciel de la plateforme doit prendre en charge les exigences 11.5.2.5 à 11.5.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Elles définissent la fonctionnalité minimale des logiciels fournissant des interfaces utilisateur lors de l’utilisation des services de la plateforme.

REMARQUE 2 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 3 : Les services d’interface utilisateur qui fournissent par défaut un soutien à l’accessibilité sont considérés comme faisant partie des services fournis pour se conformer à cette clause (par exemple, le service de création d’un nouvel élément d’interface utilisateur fournit un rôle, un état, une limite, un nom et une description).

REMARQUE 4 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

REMARQUE 5 : Dans des environnements d’un programme informatique particuliers, les attributs techniques associés aux propriétés de l’interface utilisateur décrites dans les clauses 11.5.2.5 à 11.5.2.17 peuvent avoir des noms différents de ceux utilisés dans ces clauses.

Changement de numérotation

Reformulation stylistique

11.5.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur

Les logiciels de plateforme doivent fournir un ensemble de services de plateforme documentés qui permettent aux logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme d’interagir avec la technologie d’assistance.

Lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 est pris en charge au sein de l’environnement logiciel, le logiciel de la plateforme devrait prendre en charge cette exigence. Par exemple, les attributs de sélection de 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Elles définissent la fonctionnalité minimale des logiciels fournissant des interfaces utilisateur lors de l’utilisation des services de la plateforme.

REMARQUE 2 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 3 : Les services d’interface utilisateur qui fournissent par défaut un soutien à l’accessibilité sont considérés comme faisant partie des services fournis pour se conformer à cette clause (par exemple, le service de création d’un nouvel élément d’interface utilisateur fournit un rôle, un état, une limite, un nom et une description).

REMARQUE 4 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

REMARQUE 5 : Dans des environnements d’un programme informatique particuliers, les attributs techniques associés aux propriétés de l’interface utilisateur décrites dans les clauses 11.5.2.5 à 11.5.2.17 peuvent avoir des noms différents de ceux utilisés dans ces clauses.

Reformulation stylistique

11.5.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur

Les logiciels de plateforme doivent fournir un ensemble de services de plateforme documentés qui permettent aux logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme d’interagir avec la technologie d’assistance.

Lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 est pris en charge au sein de l’environnement logiciel, le logiciel de la plateforme devrait prendre en charge cette exigence. Par exemple, les attributs de sélection de la clause 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Elles définissent la fonctionnalité minimale des logiciels fournissant des interfaces utilisateur lors de l’utilisation des services de la plateforme.

REMARQUE 2 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 3 : Les services d’interface utilisateur qui fournissent par défaut un soutien à l’accessibilité sont considérés comme faisant partie des services fournis pour se conformer à cette clause (par exemple, le service de création d’un nouvel élément d’interface utilisateur fournit un rôle, un état, une limite, un nom et une description).

REMARQUE 4 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

REMARQUE 5 : Dans des environnements d’un programme informatique particuliers, les attributs techniques associés aux propriétés de l’interface utilisateur décrites dans les clauses 11.5.2.5 à 11.5.2.17 peuvent avoir des noms différents de ceux utilisés dans ces clauses.

502.3 Services d’accessibilité

Les logiciels et les outils logiciels de la plateforme fournis par le développeur de celle-ci doivent fournir un ensemble documenté de services d’accessibilité qui prennent en charge les applications exécutées sur la plateforme pour interagir avec la technologie d’assistance et doivent être conformes à la clause 502.3. Les applications qui sont également des plateformes doivent exposer les services d’accessibilité de la plateforme sous-jacents ou mettre en œuvre d’autres services d’accessibilité documentés.

11.3.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Le logiciel de la plateforme doit fournir un ensemble de services d’accessibilité documentés qui permettent à la technologie d’assistance d’interagir avec les logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme.

Le logiciel de plateforme doit prendre en charge les exigences 11.3.2.5 à 11.3.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.3.2.5 à 11.3.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.3.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Celles-ci définissent les fonctions minimales disponibles pour les technologies d’assistance lors de l’utilisation des services de plateforme.

REMARQUE 2 : La définition de plateforme dans 3.1 s’applique aux logiciels qui fournissent des services à d’autres logiciels, y compris, mais sans s’y limiter, les systèmes d’exploitation, les navigateurs Internet et les machines virtuelles.

REMARQUE 3 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 4 : Généralement, ces services appartiennent au même ensemble de services qui sont décrits dans la clause 11.3.2.1.

REMARQUE 5 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

Reformulation stylistique

Mise à jour explicative

11.5.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Le logiciel de la plateforme doit fournir un ensemble de services d’accessibilité documentés qui permettent à la technologie d’assistance d’interagir avec les logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme.

Le logiciel de plateforme doit prendre en charge les exigences 11.5.2.5 à 11.5.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Celles-ci définissent les fonctions minimales disponibles pour les technologies d’assistance lors de l’utilisation des services de plateforme.

REMARQUE 2 : La définition de plateforme dans la clause 3.1 s’applique aux logiciels qui fournissent des services à d’autres logiciels, y compris, mais sans s’y limiter, les systèmes d’exploitation, les navigateurs Web et les machines virtuelles.

REMARQUE 3 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 4 : Généralement, ces services appartiennent au même ensemble de services qui sont décrits dans la clause 11.5.2.1.

REMARQUE 5 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

Changement de numérotation

Reformulation stylistique

11.5.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Le logiciel de la plateforme doit fournir un ensemble de services d’accessibilité documentés qui permettent à la technologie d’assistance d’interagir avec les logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme.

Lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 est pris en charge au sein de l’environnement logiciel, le logiciel de la plateforme devrait prendre en charge cette exigence. Par exemple, les attributs de sélection de 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Celles-ci définissent les fonctions minimales disponibles pour les technologies d’assistance lors de l’utilisation des services de plateforme.

REMARQUE 2 : La définition de plateforme dans la clause 3.1 s’applique aux logiciels qui fournissent des services à d’autres logiciels, y compris, mais sans s’y limiter, les systèmes d’exploitation, les navigateurs Web et les machines virtuelles.

REMARQUE 3 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 4 : Généralement, ces services appartiennent au même ensemble de services qui sont décrits dans la clause 11.5.2.1.

REMARQUE 5 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

Reformulation stylistique

11.5.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Le logiciel de la plateforme doit fournir un ensemble de services d’accessibilité documentés qui permettent à la technologie d’assistance d’interagir avec les logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme.

Lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 est pris en charge au sein de l’environnement logiciel, le logiciel de la plateforme devrait prendre en charge cette exigence. Par exemple, les attributs de sélection de la clause 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Celles-ci définissent les fonctions minimales disponibles pour les technologies d’assistance lors de l’utilisation des services de plateforme.

REMARQUE 2 : La définition de plateforme dans la clause 3.1 s’applique aux logiciels qui fournissent des services à d’autres logiciels, y compris, mais sans s’y limiter, les systèmes d’exploitation, les navigateurs Web et les machines virtuelles.

REMARQUE 3 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 4 : Généralement, ces services appartiennent au même ensemble de services qui sont décrits dans la clause 11.5.2.1.

REMARQUE 5 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

502.3.1 Renseignements sur les objets

Le rôle, les états, les propriétés, les limites, le nom et la description des objets doivent être déterminables par un programme informatique.

11.3.2.5 Renseignements sur les objets

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, permettre au rôle, aux états, à la limite, au nom et à la description des éléments d’interface utilisateur d’être déterminés par un programme informatique au moyen de technologies d’assistance.

Reformulation stylistique

Mise à jour explicative

11.5.2.5 Renseignements sur les objets

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre au rôle, aux états, à la limite, au nom et à la description des éléments d’interface utilisateur d’être déterminés par un programme informatique au moyen de technologies d’assistance.

Changement de numérotation

11.5.2.5 Renseignements sur les objets

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre au rôle, aux états, à la limite, au nom et à la description des éléments d’interface utilisateur d’être déterminés par un programme informatique au moyen de technologies d’assistance.

11.5.2.5 Renseignements sur les objets

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre au rôle, aux états, à la limite, au nom et à la description des éléments d’interface utilisateur d’être déterminés par un programme informatique au moyen de technologies d’assistance.

502.3.2 Modification des renseignements sur les objets

Les états et les propriétés qui peuvent être définis par l’utilisateur doivent pouvoir être définis par un programme informatique, y compris par une technologie d’assistance.

11.3.2.16 Modifications d’états ou de propriétés

Lorsque les exigences de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.3.2.3, permettre aux technologies d’assistance de modifier par un programme informatique les états et propriétés des éléments d’interface utilisateur grâce auxquels l’utilisateur peut modifier ces articles.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.5.2.16 Modifications d’états ou de propriétés

Où les exigences de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique les états et propriétés des éléments d’interface utilisateur grâce auxquels l’utilisateur peut modifier ces articles.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Changement de numérotation

Reformulation stylistique

11.5.2.16 Modifications d’états ou de propriétés

Lorsque les exigences de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique les états et propriétés des éléments d’interface utilisateur grâce auxquels l’utilisateur peut modifier ces articles.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

11.5.2.16 Modifications d’états ou de propriétés

Lorsque les exigences de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique les états et propriétés des éléments d’interface utilisateur grâce auxquels l’utilisateur peut modifier ces articles.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

502.3.3 Ligne, colonne et en-têtes

Si un objet se trouve dans une table de données, les lignes et colonnes occupées, ainsi que les en-têtes associés à celles-ci, doivent être déterminables par un programme informatique.

11.3.2.6 Ligne, colonne et en-têtes

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, rendre la ligne et la colonne de chaque cellule d’un tableau de données, y compris les en-têtes de la ligne et de la colonne, le cas échéant, déterminables par un programme informatique au moyen de technologies d’assistance.

Reformulation stylistique

Mise à jour explicative

11.5.2.6 Ligne, colonne et en-têtes

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la ligne et la colonne de chaque cellule d’un tableau de données, y compris les en-têtes de la ligne et de la colonne, le cas échéant, déterminables par un programme informatique au moyen de technologies d’assistance.

Changement de numérotation

11.5.2.6 Ligne, colonne et en-têtes

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la ligne et la colonne de chaque cellule d’un tableau de données, y compris les en-têtes de la ligne et de la colonne, le cas échéant, déterminables par un programme informatique au moyen de technologies d’assistance.

11.5.2.6 Ligne, colonne et en-têtes

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la ligne et la colonne de chaque cellule d’un tableau de données, y compris les en-têtes de la ligne et de la colonne, le cas échéant, déterminables par un programme informatique au moyen de technologies d’assistance.

502.3.4 Valeurs

Toute valeur actuelle, ainsi que toute série ou plage de valeurs admissibles associée à un objet, doit être déterminable par un programme informatique.

11.3.2.7 Valeurs

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, rendre la valeur actuelle d’un élément d’interface utilisateur et toute valeur minimale ou maximale de la plage, si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, pouvant être déterminées par un programme informatique par des technologies d’assistance.

Reformulation stylistique

Mise à jour explicative

11.5.2.7 Valeurs

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la valeur actuelle d’un élément d’interface utilisateur et toute valeur minimale ou maximale de la plage, si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, pouvant être déterminées par un programme informatique par des technologies d’assistance.

Changement de numérotation

11.5.2.7 Valeurs

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la valeur actuelle d’un élément d’interface utilisateur et toute valeur minimale ou maximale de la plage, si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, pouvant être déterminées par un programme informatique par des technologies d’assistance.

11.5.2.7 Valeurs

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la valeur actuelle d’un élément d’interface utilisateur et toute valeur minimale ou maximale de la plage, si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, pouvant être déterminées par un programme informatique par des technologies d’assistance.

502.3.5 Modification des valeurs

Les valeurs pouvant être définies par l’utilisateur doivent pouvoir être établies par un programme informatique, y compris au moyen d’une technologie d’assistance.

11.3.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à 11.3.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recours aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.5.2.17 Modifications des valeurs et du texte

Où les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recours aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Changement de numérotation

Reformulation stylistique

11.5.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recours aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

11.5.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recours aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

502.3.6 Liens entre les étiquettes

Tout lien qu’entretient un composant en tant qu’étiquette pour un autre composant, ou en tant que composant étiqueté par un autre composant, doit être déterminable par un programme informatique.

11.3.2.8 Liens entre les étiquettes

Lorsque le logiciel fournit une interface utilisateur, il expose le lien qu’entretient un élément d’interface utilisateur en tant qu’étiquette pour un autre élément ou en tant qu’élément étiqueté par un autre élément, en utilisant les services décrits dans la clause 11.3.2.3, de sorte que ces informations puissent être déterminées par un programme informatique par des technologies d’assistance.

Reformulation stylistique

Mise à jour explicative

11.5.2.8 Liens entre les étiquettes

Lorsque le logiciel fournit une interface utilisateur, il expose le lien qu’entretient un élément d’interface utilisateur en tant qu’étiquette pour un autre élément ou en tant qu’élément étiqueté par un autre élément, en utilisant les services décrits dans la clause 11.5.2.3, de sorte que ces informations puissent être déterminées par un programme informatique par des technologies d’assistance.

Changement de numérotation

11.5.2.8 Liens entre les étiquettes

Lorsque le logiciel fournit une interface utilisateur, il expose le lien qu’entretient un élément d’interface utilisateur en tant qu’étiquette pour un autre élément ou en tant qu’élément étiqueté par un autre élément, en utilisant les services décrits dans la clause 11.5.2.3, de sorte que ces informations puissent être déterminées par un programme informatique par des technologies d’assistance.

11.5.2.8 Liens entre les étiquettes

Lorsque le logiciel fournit une interface utilisateur, il expose le lien qu’entretient un élément d’interface utilisateur en tant qu’étiquette pour un autre élément ou en tant qu’élément étiqueté par un autre élément, en utilisant les services décrits dans la clause 11.5.2.3, de sorte que ces informations puissent être déterminées par un programme informatique par des technologies d’assistance.

502.3.7 Relations hiérarchiques

Toute relation hiérarchique (parent-enfant) qu’entretient un composant en tant que conteneur d’un autre composant, ou en tant que composant contenu par un composant, doit être déterminable par un programme informatique.

11.3.2.9 Relations parents-enfants

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, la relation entre un élément d’interface utilisateur et tout élément parent ou enfant.

Reformulation stylistique

Mise à jour explicative

11.5.2.9 Relations parents-enfants

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, la relation entre un élément d’interface utilisateur et tout élément parent ou enfant.

Changement de numérotation

11.5.2.9 Relations parents-enfants

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, la relation entre un élément d’interface utilisateur et tout élément parent ou enfant.

11.5.2.9 Relations parents-enfants

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, la relation entre un élément d’interface utilisateur et tout élément parent ou enfant.

502.3.8 Texte

Le contenu des objets textuels, les attributs textuels et la limite du texte affiché à l’écran doivent être déterminables par un programme informatique.

11.3.2.10 Texte

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, le contenu textuel, les attributs textuels et la limite du texte rendu à l’écran.

Reformulation stylistique

Mise à jour explicative

11.5.2.10 Texte

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, le contenu textuel, les attributs textuels et la limite du texte rendu à l’écran.

Changement de numérotation

11.5.2.10 Texte

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, le contenu textuel, les attributs textuels et la limite du texte rendu à l’écran.

11.5.2.10 Texte

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, le contenu textuel, les attributs textuels et la limite du texte rendu à l’écran.

502.3.9 Modification du texte

Le texte pouvant être défini par l’utilisateur doit pouvoir être établi par un programme informatique, y compris au moyen d’une technologie d’assistance.

11.3.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à 11.3.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recourir aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.5.2.17 Modifications des valeurs et du texte

Où les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recourir aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Changement de numérotation

Reformulation stylistique

11.5.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recourir aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

11.5.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recourir aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

502.3.10 Liste des actions

Une liste de toutes les actions pouvant être exécutées sur un objet doit être déterminable par un programme informatique.

11.3.2.11 Liste des actions disponibles

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, une liste des actions disponibles qui peuvent être exécutées sur un élément d’interface utilisateur.

Reformulation stylistique

Mise à jour explicative

11.5.2.11 Liste des actions disponibles

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, une liste des actions disponibles qui peuvent être exécutées sur un élément d’interface utilisateur.

Changement de numérotation

11.5.2.11 Liste des actions disponibles

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, une liste des actions disponibles qui peuvent être exécutées sur un élément d’interface utilisateur.

11.5.2.11 Liste des actions disponibles

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, une liste des actions disponibles qui peuvent être exécutées sur un élément d’interface utilisateur.

502.3.11 Actions sur les objets

Les applications doivent permettre à la technologie d’assistance d’exécuter par un programme informatique les actions disponibles sur les objets.

11.3.2.12 Exécution des actions disponibles

Lorsque les exigences de sécurité le permettent, le logiciel qui fournit une interface utilisateur doit, en utilisant les services décrits à la clause 11.3.2.3, permettre l’exécution programmatique des actions exposées, au moyen des technologies d’assistance, conformément à la clause 11.3.2.11.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.5.2.12 Exécution des actions disponibles

Où les exigences de sécurité le permettent, le logiciel qui fournit une interface utilisateur doit, en utilisant les services décrits à la clause 11.5.2.3, permettre l’exécution programmatique des actions exposées, au moyen des technologies d’assistance, conformément à la clause 11.5.2.11.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Changement de numérotation

Reformulation stylistique

11.5.2.12 Exécution des actions disponibles

Lorsque les exigences de sécurité le permettent, le logiciel qui fournit une interface utilisateur doit, en utilisant les services décrits à la clause 11.5.2.3, permettre l’exécution programmatique des actions exposées, au moyen des technologies d’assistance, conformément à la clause 11.5.2.11.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

11.5.2.12 Exécution des actions disponibles

Lorsque les exigences de sécurité le permettent, le logiciel qui fournit une interface utilisateur doit, en utilisant les services décrits à la clause 11.5.2.3, permettre l’exécution programmatique des actions exposées, au moyen des technologies d’assistance, conformément à la clause 11.5.2.11.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Les technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

502.3.12 Curseur du focus

Les applications doivent exposer les informations et les mécanismes nécessaires pour faire le suivi du focus, du point d’insertion du texte et des attributs de sélection des composants de l’interface utilisateur.

11.3.2.13 Suivi du focus et des attributs de sélection

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, rendre l’information et les mécanismes nécessaires au suivi de le focus, du point d’insertion du texte et des attributs de sélection des éléments d’interface utilisateur, déterminables par un programme informatique par les technologies d’assistance.

Reformulation stylistique

Mise à jour explicative

11.5.2.13 Suivi du focus et des attributs de sélection

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre l’information et les mécanismes nécessaires au suivi du focus, du point d’insertion du texte et des attributs de sélection des éléments d’interface utilisateur, déterminables par un programme informatique par les technologies d’assistance.

Changement de numérotation

11.5.2.13 Suivi du focus et des attributs de sélection

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre l’information et les mécanismes nécessaires au suivi du focus, du point d’insertion du texte et des attributs de sélection des éléments d’interface utilisateur, déterminables par un programme informatique par les technologies d’assistance.

11.5.2.13 Suivi du focus et des attributs de sélection

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre l’information et les mécanismes nécessaires au suivi du focus, du point d’insertion du texte et des attributs de sélection des éléments d’interface utilisateur, déterminables par un programme informatique par les technologies d’assistance.

502.3.13 Modification du curseur du focus

Le focus, le point d’insertion du texte et les attributs de sélection qui peuvent être définis par l’utilisateur doivent pouvoir être définis par un programme informatique, y compris au moyen de l’utilisation d’une technologie d’assistance.

11.3.2.14 Modification du focus et des attributs de sélection

Lorsque les exigences de sécurité le permettent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.3.2.3, permettre aux technologies d’assistance de modifier par un programme informatique le focus, le point d’insertion de texte et les attributs de sélection des éléments d’interface utilisateur où l’utilisateur peut modifier ces éléments.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.5.2.14 Modification du focus et des attributs de sélection

Où les exigences de sécurité le permettent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique le focus, le point d’insertion de texte et les attributs de sélection des éléments d’interface utilisateur où l’utilisateur peut modifier ces éléments.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Changement de numérotation

Reformulation stylistique

11.5.2.14 Modification du focus et des attributs de sélection

Lorsque les exigences de sécurité le permettent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique le focus, le point d’insertion de texte et les attributs de sélection des éléments d’interface utilisateur où l’utilisateur peut modifier ces éléments.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

11.5.2.14 Modification du focus et des attributs de sélection

Lorsque les exigences de sécurité le permettent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique le focus, le point d’insertion de texte et les attributs de sélection des éléments d’interface utilisateur où l’utilisateur peut modifier ces éléments.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

502.3.14 Avis d’événements

La technologie d’assistance doit avoir accès aux avis d’événements liés aux interactions de l’utilisateur, y compris, sans toutefois s’y limiter, les changements aux états, à la valeur, au nom, à la description et à la limite du composant.

11.3.2.15 Avis de modification

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à 11.3.2.3, aviser les technologies d’assistance des changements apportés aux attributs des éléments d’interface utilisateur pouvant être déterminés par un programme informatique qui sont mentionnés dans les exigences 11.3.2.5 à 11.3.2.11 et 11.3.2.13.

Reformulation stylistique

Mise à jour explicative

11.5.2.15 Avis de modification

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, aviser les technologies d’assistance des changements apportés aux attributs des éléments d’interface utilisateur pouvant être déterminés par un programme informatique qui sont mentionnés dans les exigences 11.5.2.5 à 11.5.2.11 et 11.5.2.13.

Changement de numérotation

Reformulation stylistique

11.5.2.15 Avis de modification

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, aviser les technologies d’assistance des changements apportés aux attributs des éléments d’interface utilisateur pouvant être déterminés par un programme informatique qui sont mentionnés dans les exigences 11.5.2.5 à 11.5.2.11 et 11.5.2.13.

11.5.2.15 Avis de modification

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, aviser les technologies d’assistance des changements apportés aux attributs des éléments d’interface utilisateur pouvant être déterminés par un programme informatique qui sont mentionnés dans les exigences 11.5.2.5 à 11.5.2.11 et 11.5.2.13.

502.4 Caractéristiques d’accessibilité de la plateforme

Les plateformes et les logiciels de plateforme doivent être conformes aux exigences de la norme ANSI/HFES 200.2, Human Factors Engineering of Software User interfaces — Part 2: Accessibility (2008) (incorporée par renvoi, voir l’article 702.4.1) énumérées ci-dessous :

Voir A-G, ci-dessous.Voir A-G, ci-dessous.Voir A-G, ci-dessous.Voir A-G, ci-dessous.
  1. L’article 9.3.3 permet la saisie séquentielle de plusieurs touches (avec accord) ;25

5.9 Actions simultanées de la part de l’utilisateur

Lorsque les TIC requièrent des actions simultanées de la part de l’utilisateur pour fonctionner, ces TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas d’actions simultanées de la part de l’utilisateur pour fonctionner.

REMARQUE : L’utilisation des deux mains pour ouvrir le couvercle d’un ordinateur portable, la pression simultanée de deux ou plusieurs touches ou le contact d’une surface avec plus d’un doigt sont des exemples d’actions simultanées de la part de l’utilisateur.

Reformulation stylistique

Mise à jour explicative

5.9 Actions simultanées de la part de l’utilisateur

Lorsque les TIC requièrent des actions simultanées de la part de l’utilisateur pour fonctionner, ces TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas d’actions simultanées de la part de l’utilisateur pour fonctionner.

REMARQUE : L’utilisation des deux mains pour ouvrir le couvercle d’un ordinateur portable, la pression simultanée de deux ou plusieurs touches ou le contact d’une surface avec plus d’un doigt sont des exemples d’actions simultanées de la part de l’utilisateur.

5.9 Actions simultanées de la part de l’utilisateur

Lorsque les TIC ont un mode de fonctionnement exigeant des actions simultanées de la part de l’utilisateur pour fonctionner, ces TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas d’actions simultanées de la part de l’utilisateur pour fonctionner.

REMARQUE : L’utilisation des deux mains pour ouvrir le couvercle d’un ordinateur portable, la pression simultanée de deux ou plusieurs touches ou le contact d’une surface avec plus d’un doigt sont des exemples d’actions simultanées de la part de l’utilisateur.

Reformulation stylistique

5.9 Actions simultanées de la part de l’utilisateur

Lorsque les TIC ont un mode de fonctionnement exigeant des actions simultanées de la part de l’utilisateur pour fonctionner, ces TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas d’actions simultanées de la part de l’utilisateur pour fonctionner.

REMARQUE : L’utilisation des deux mains pour ouvrir le couvercle d’un ordinateur portable, la pression simultanée de deux ou plusieurs touches ou le contact d’une surface avec plus d’un doigt sont des exemples d’actions simultanées de la part de l’utilisateur.

  1. L’article 9.3.4 prévoit l’ajustement du délai avant l’acceptation de la frappe;

5.7 Répétition des touches

Lorsque des TIC avec fonction de répétition des touches sont fournies et que la fonction de répétition des touches ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.

Reformulation stylistique

Mise à jour explicative

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.
Reformulation stylistique

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.
  1. L’article 9.3.5 prévoit l’ajustement de l’acceptation de la double frappe de la même touche;26

5.8 Acceptation de la double frappe

Lorsqu’un clavier ou un pavé numérique sont fournis, le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la frappe précédente, doit être réglable jusqu’à au moins 0,5 seconde.

Reformulation stylistique

Mise à jour explicative

5.8 Acceptation de la double frappe

Lorsque les TIC sont dotées d’un clavier ou d’un pavé numérique, le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la frappe précédente, doit être réglable jusqu’à au moins 0,5 seconde.

Reformulation stylistique

5.8 Acceptation de la double frappe

Lorsque les TIC sont dotées d’un clavier ou d’un pavé numérique, le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la frappe précédente, doit être réglable jusqu’à au moins 0,5 seconde.

5.8 Acceptation de la double frappe

Lorsque les TIC sont dotées d’un clavier ou d’un pavé numérique, le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la frappe précédente, doit être réglable jusqu’à au moins 0,5 seconde.

  1. L’article 10.7.1 prévoit l’affichage des sous-titres fournis.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est fourni, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

Reformulation stylistique

Mise à jour explicative

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

Changement fonctionnel

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

REMARQUE 3 : La clause 7.1.1 fait référence à la capacité du lecteur d’afficher des sous-titres. Les clauses 9.1.2.2, 10.1.2.2 et 11.1.2.2 font référence à la fourniture de sous-titres pour le contenu (la vidéo).

Changement explicatif

Liste des tableaux

503 Applications

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

503.2 Préférences de l’utilisateur

Les applications doivent autoriser les réglages de la plateforme, en ce qui concerne la couleur, le contraste, le type et la taille de police ainsi que le curseur du focus, en fonction des préférences de l’utilisateur.

EXCEPTION : Les applications conçues pour être isolées de leur logiciel de plateforme sous-jacent, y compris les applications Web, n’ont pas à être conformes à la clause 503.2.

11.5 Préférences de l’utilisateur

Lorsque le logiciel fournit une interface utilisateur, il doit fournir suffisamment de modes de fonctionnement se servant des préférences de l’utilisateur pour les réglages de la plateforme en ce qui concerne la couleur, le contraste, le type et la taille de police et le curseur du focus, sauf s’il s’agit de logiciels conçus pour être isolés de leur plateforme sous-jacente.

REMARQUE : Les logiciels isolés de leur plateforme sous-jacente n’ont pas accès aux paramètres de l’utilisateur de la plateforme et ne peuvent donc pas respecter cette clause.

Reformulation stylistique

Mise à jour explicative

11.7 Préférences de l’utilisateur

Lorsque le logiciel fournit une interface utilisateur, il doit fournir suffisamment de modes de fonctionnement se servant des préférences de l’utilisateur pour les réglages de la plateforme en ce qui concerne la couleur, le contraste, le type et la taille de police et le curseur du focus, sauf s’il s’agit de logiciels conçus pour être isolés de leur plateforme sous-jacente.

REMARQUE : Les logiciels isolés de leur plateforme sous-jacente n’ont pas accès aux paramètres de l’utilisateur de la plateforme et ne peuvent donc pas respecter cette clause.

Changement de numérotation

11.7 Préférences de l’utilisateur

Lorsque le logiciel n’est pas conçu pour être isolé de sa plateforme et qu’il fournit une interface utilisateur, cette interface utilisateur doit respecter les valeurs des préférences de l’utilisateur pour les réglages de la plateforme en ce qui concerne les unités de mesure, la couleur, le contraste, le type et la taille de police et le curseur du focus, sauf s’ils sont remplacés par l’utilisateur.

REMARQUE 1 : Les logiciels isolés de leur plateforme sous-jacente n’ont pas accès aux paramètres de l’utilisateur de la plateforme et ne peuvent donc pas respecter cette clause.

REMARQUE 2 : Pour le contenu Web, la plateforme sous-jacente est l’agent utilisateur.

REMARQUE 3 : Cela n’empêche pas le logiciel d’avoir des valeurs supplémentaires pour un paramètre, tant qu’il existe un mode dans lequel l’application suivra les paramètres du système, même s’ils sont plus restreints.

Reformulation stylistique

Changement fonctionnel

11.7 Préférences de l’utilisateur

Lorsque le logiciel n’est pas conçu pour être isolé de sa plateforme et qu’il fournit une interface utilisateur, cette interface utilisateur doit respecter les valeurs des préférences de l’utilisateur pour les réglages de la plateforme en ce qui concerne les unités de mesure, la couleur, le contraste, le type et la taille de police et le curseur du focus, sauf s’ils sont remplacés par l’utilisateur.
REMARQUE 1 :

Les logiciels isolés de leur plateforme sous-jacente n’ont pas accès aux paramètres de l’utilisateur de la plateforme et ne peuvent donc pas respecter cette clause.

REMARQUE 2 : Pour le contenu Web, la plateforme sous-jacente est l’agent utilisateur.

REMARQUE 3 : Cela n’empêche pas le logiciel d’avoir des valeurs supplémentaires pour un paramètre, tant qu’il existe un mode dans lequel l’application suivra les paramètres du système, même s’ils sont plus restreints.

503.3 Autres interfaces utilisateurs

Lorsqu’une application prévoit une autre interface utilisateur qui fonctionne comme une technologie d’assistance, l’application doit utiliser une plateforme et d’autres services d’accessibilité standard de l’industrie.

11.3.2.4 Technologie d’assistance

Lorsque la TIC est une technologie d’assistance, elle doit utiliser les services d’accessibilité documentés de la plateforme.

REMARQUE : L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.3.2.1 et 11.3.2.2.

REMARQUE 2 : Les technologies d’assistance peuvent également utiliser d’autres services d’accessibilité documentés.

Reformulation stylistique

Mise à jour explicative

11.5.2.4 Technologie d’assistance

Lorsque la TIC est une technologie d’assistance, elle doit utiliser les services d’accessibilité documentés de la plateforme.

REMARQUE : L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.5.2.1 et 11.5.2.2.

REMARQUE 2 : Les technologies d’assistance peuvent également utiliser d’autres services d’accessibilité documentés.

Changement de numérotation

11.5.2.4 Technologie d’assistance

Lorsque la TIC est une technologie d’assistance, elle doit utiliser les services d’accessibilité documentés de la plateforme.

REMARQUE : L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.5.2.1 et 11.5.2.2.

REMARQUE 2 : Les technologies d’assistance peuvent également utiliser d’autres services d’accessibilité documentés.

11.5.2.4 Technologie d’assistance

Lorsque la TIC est une technologie d’assistance, elle doit utiliser les services d’accessibilité documentés de la plateforme.

REMARQUE : L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.5.2.1 et 11.5.2.2.

REMARQUE 2 : Les technologies d’assistance peuvent également utiliser d’autres services d’accessibilité documentés.

503.4 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent des vidéos avec synchronisation sonore, elles doivent permettre à l’utilisateur de contrôler les sous-titres et les descriptions audio conformes à la clause 503.4.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est fourni, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

Reformulation stylistique

Mise à jour explicative

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

Changement fonctionnel

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

REMARQUE 3 : la clause 7.1.1 fait référence à la capacité du lecteur d’afficher des sous-titres. Les clauses 9.1.2.2, 10.1.2.2 et 11.1.2.2 font référence à la fourniture de sous-titres pour le contenu (la vidéo).

Mise à jour explicative

503.4.1 Commandes pour les sous-titres

Lorsque des commandes sont fournies à l’utilisateur pour régler le volume, les commandes de l’utilisateur pour sélectionner les sous-titres doivent être fournies par les TIC au même niveau de menu que les commandes de l’utilisateur pour le réglage du volume ou la sélection des programmes.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Reformulation stylistique

Mise à jour explicative

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

503.4.2 Commandes pour les descriptions audio

Lorsque des commandes sont fournies à l’utilisateur pour sélectionner les programmes, les commandes de l’utilisateur pour sélectionner les descriptions audios doivent être fournies par les TIC au même niveau de menu que les commandes de l’utilisateur pour le réglage du volume ou la sélection des programmes.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Reformulation stylistique

Mise à jour explicative

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Liste des tableaux

504 Outils-auteurs

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

504.1 Généralités

Lorsqu’une application est un outil-auteur, l’application doit être conforme à la clause 504 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format de destination.

11.6.1 Technologie du contenu

Les outils-auteurs doivent être conformes aux clauses 11.6.2 à 11.6.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

Reformulation stylistique

11.8.1 Technologie du contenu

Les outils-auteurs doivent être conformes aux clauses 11.8.2 à 11.8.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

Changement de numérotation

11.8.1 Technologie du contenu

Les outils-auteurs doivent être conformes aux clauses 11.8.2 à 11.8.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

11.8.1 Technologie du contenu

Les outils-auteurs doivent être conformes aux clauses 11.8.2 à 11.8.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

504.2 Création ou modification de contenu

Les outils-auteurs doivent prévoir un mode de fonctionnement permettant de créer ou de modifier du contenu qui est conforme aux critères de succès de niveau A et de niveau AA ainsi qu’aux exigences de conformité dans les WCAG 2.0 (incorporées par renvoi, voir l’article 702.10.1) pour toutes les caractéristiques prises en charge et, le cas échéant, aux formats de fichier pris en charge par l’outil-auteur. Les outils-auteurs doivent permettre aux auteurs de remplacer les renseignements requis pour l’accessibilité.

EXCEPTION : Les outils-auteurs n’ont pas à être conformes à la clause 504.2 lorsqu’ils sont utilisés pour modifier directement le code source en texte brut.

11.6.2 Création de contenu accessible

Les outils-auteurs doivent permettre et orienter la production de contenu conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

REMARQUE : Les outils-auteurs peuvent s’appuyer sur des outils supplémentaires lorsqu’il n’est pas possible de respecter des exigences spécifiques avec un seul outil. Par exemple, un outil de montage vidéo peut permettre la création de fichiers vidéo aux fins de diffusion via la télévision et le Web, mais la création de fichiers de sous-titres pour des formats multiples peut être assurée par un outil différent.

Reformulation stylistique

Mise à jour explicative

11.8.2 Création de contenu accessible

Les outils-auteurs doivent permettre et orienter la production de contenu conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

REMARQUE : Les outils-auteurs peuvent s’appuyer sur des outils supplémentaires lorsqu’il n’est pas possible de respecter des exigences spécifiques avec un seul outil. Par exemple, un outil de montage vidéo peut permettre la création de fichiers vidéo aux fins de diffusion via la télévision et le Web, mais la création de fichiers de sous-titres pour des formats multiples peut être assurée par un outil différent.

Changement de numérotation

11.8.2 Création de contenu accessible

Les outils-auteurs doivent permettre et orienter la production de contenu conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

REMARQUE : Les outils-auteurs peuvent s’appuyer sur des outils supplémentaires lorsqu’il n’est pas possible de respecter des exigences spécifiques avec un seul outil. Par exemple, un outil de montage vidéo peut permettre la création de fichiers vidéo aux fins de diffusion via la télévision et le Web, mais la création de fichiers de sous-titres pour des formats multiples peut être assurée par un outil différent.

11.8.2 Création de contenu accessible

Les outils-auteurs doivent permettre et orienter la production de contenu conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

REMARQUE : Les outils-auteurs peuvent s’appuyer sur des outils supplémentaires lorsqu’il n’est pas possible de respecter des exigences spécifiques avec un seul outil. Par exemple, un outil de montage vidéo peut permettre la création de fichiers vidéo aux fins de diffusion via la télévision et le Web, mais la création de fichiers de sous-titres pour des formats multiples peut être assurée par un outil différent.

504.2.1 Préservation des renseignements fournis aux fins d’accessibilité dans le cadre de la conversion de format

Les outils-auteurs doivent, lors de la conversion de contenu d’un format à un autre ou de l’enregistrement de contenu dans plusieurs formats, préserver les renseignements requis pour l’accessibilité dans la mesure où ceux-ci sont pris en charge par le format de destination.

11.6.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Lorsque l’outil-auteur fournit des transformations de restructuration ou de recodage, les renseignements sur l’accessibilité doivent alors être préservés dans l’extrant s’il existe des mécanismes équivalents dans la technologie du contenu de l’extrant.

REMARQUE 1 : Les transformations de restructuration sont des transformations dans le cadre desquelles la technologie du contenu reste identique, mais les caractéristiques structurelles du contenu sont modifiées (par exemple, linéarisation des tableaux, division d’un document en pages).

REMARQUE 2 : Les transformations de recodage sont des transformations dans le cadre desquelles la technologie utilisée pour coder le contenu est modifiée.

Reformulation stylistique

Mise à jour explicative

11.8.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Lorsque l’outil-auteur fournit des transformations de restructuration ou de recodage, les renseignements sur l’accessibilité doivent alors être préservés dans l’extrant s’il existe des mécanismes équivalents dans la technologie du contenu de l’extrant.

REMARQUE 1 : Les transformations de restructuration sont des transformations dans le cadre desquelles la technologie du contenu reste identique, mais les caractéristiques structurelles du contenu sont modifiées (par exemple, linéarisation des tableaux, division d’un document en pages).

REMARQUE 2 : Les transformations de recodage sont des transformations dans le cadre desquelles la technologie utilisée pour coder le contenu est modifiée.

Changement de numérotation

11.8.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Lorsque l’outil-auteur fournit des transformations de restructuration ou de recodage, les renseignements sur l’accessibilité doivent alors être préservés dans l’extrant s’il existe des mécanismes équivalents dans la technologie du contenu de l’extrant.

REMARQUE 1 : Les transformations de restructuration sont des transformations dans le cadre desquelles la technologie du contenu reste identique, mais les caractéristiques structurelles du contenu sont modifiées (par exemple, linéarisation des tableaux, division d’un document en pages).

REMARQUE 2 : Les transformations de recodage sont des transformations dans le cadre desquelles la technologie utilisée pour coder le contenu est modifiée.

11.8.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Lorsque l’outil-auteur fournit des transformations de restructuration ou de recodage, les renseignements sur l’accessibilité doivent alors être préservés dans l’extrant s’il existe des mécanismes équivalents dans la technologie du contenu de l’extrant.

REMARQUE 1 : Les transformations de restructuration sont des transformations dans le cadre desquelles la technologie du contenu reste identique, mais les caractéristiques structurelles du contenu sont modifiées (par exemple, linéarisation des tableaux, division d’un document en pages).

REMARQUE 2 : Les transformations de recodage sont des transformations dans le cadre desquelles la technologie utilisée pour coder le contenu est modifiée.

504.3 Invites

Les outils-auteurs doivent prévoir un mode de fonctionnement qui invite les auteurs à créer du contenu qui est conforme aux critères de succès de niveau A et de niveau AA ainsi qu’aux exigences de conformité dans les WCAG 2.0 (incorporées par renvoi, voir l’article 702.10.1) pour les caractéristiques prises en charge et, le cas échéant, aux formats de fichier pris en charge par l’outil-auteur.

11.6.4 Aide à la réparation

Si la fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (documents), selon le cas, alors l’outil-auteur doit formuler des suggestions en matière de réparation.

REMARQUE : Cela n’exclut pas les réparations automatisées ou semi-automatisées qui sont possibles (et recommandées) pour de nombreux types de problèmes d’accessibilité du contenu.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.8.4 Aide à la réparation

Si la fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, alors l’outil-auteur doit formuler des suggestions en matière de réparation.

REMARQUE : Cela n’exclut pas les réparations automatisées ou semi-automatisées qui sont possibles (et recommandées) pour de nombreux types de problèmes d’accessibilité du contenu.

Changement de numérotation

Reformulation stylistique

11.8.4 Aide à la réparation

Si la fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, alors l’outil-auteur doit formuler des suggestions en matière de réparation.

REMARQUE : Cela n’exclut pas les réparations automatisées ou semi-automatisées qui sont possibles (et recommandées) pour de nombreux types de problèmes d’accessibilité du contenu.

11.8.4 Aide à la réparation

Si la fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, alors l’outil-auteur doit formuler des suggestions en matière de réparation.

REMARQUE : Cela n’exclut pas les réparations automatisées ou semi-automatisées qui sont possibles (et recommandées) pour de nombreux types de problèmes d’accessibilité du contenu.

504.4 Modèles

Lorsque des modèles sont fournis, des modèles permettant la création de contenu qui est conforme aux critères de succès de niveau A et de niveau AA ainsi qu’aux exigences de conformité dans les WCAG 2.0 (incorporées par renvoi, voir l’article 702.10.1) doivent être fournis aux fins d’une gamme d’applications des modèles pour les caractéristiques prises en charge et, le cas échéant, aux formats de fichier pris en charge par l’outil de création.

11.6.5 Modèles

Lorsque l’outil-auteur fournit des modèles, au moins l’un des modèles qui prend en charge la création de contenu conforme aux exigences des clauses 9 (contenu Web) ou 10 (documents), selon le cas, doit être disponible et identifié en tant que tel.

Reformulation stylistique

Mise à jour explicative

11.8.5 Modèles

Lorsque l’outil-auteur fournit des modèles, au moins l’un des modèles qui prend en charge la création de contenu conforme aux exigences des clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, doit être disponible et identifié en tant que tel.

Changement de numérotation

Reformulation stylistique

11.8.5 Modèles

Lorsque l’outil-auteur fournit des modèles, au moins l’un des modèles qui prend en charge la création de contenu conforme aux exigences des clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, doit être disponible et identifié en tant que tel.

11.8.5 Modèles

Lorsque l’outil-auteur fournit des modèles, au moins l’un des modèles qui prend en charge la création de contenu conforme aux exigences des clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, doit être disponible et identifié en tant que tel.

Liste des tableaux

Chapitre 6 – Documentation et services de soutien

602 Documentation de soutien

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

602.2 Caractéristiques d’accessibilité et de compatibilité

La documentation doit énumérer et expliquer comment utiliser les caractéristiques d’accessibilité et de compatibilité exigées par les chapitres 4 et 5. La documentation doit inclure les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

12.1.1 Caractéristiques d’accessibilité et de compatibilité

La documentation du produit fournie avec les TIC, qu’elle soit fournie séparément ou intégrée aux TIC doit énumérer et expliquer les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

Reformulation stylistique

Mise à jour explicative

12.1.1 Caractéristiques d’accessibilité et de compatibilité

La documentation du produit fournie avec les TIC, qu’elle soit fournie séparément ou intégrée aux TIC doit énumérer et expliquer les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

12.1.1 Caractéristiques d’accessibilité et de compatibilité

La documentation du produit fournie avec les TIC, qu’elle soit fournie séparément ou intégrée aux TIC doit énumérer et expliquer les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

REMARQUE 2 : Une pratique exemplaire consiste à utiliser WebSchemas / Accessibility 2.0 pour fournir des métadonnées sur l’accessibilité des TIC.

REMARQUE 3 : L’énoncé sur l'accessibilité et les pages d’aide sont deux exemples de diffusion de renseignements sur les produits.

Changement fonctionnel

12.1.1 Caractéristiques d’accessibilité et de compatibilité

La documentation du produit fournie avec les TIC, qu’elle soit fournie séparément ou intégrée aux TIC doit énumérer et expliquer les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

REMARQUE 2 : Une pratique exemplaire consiste à utiliser WebSchemas / Accessibility 2.0 [i.38] pour fournir des métadonnées sur l’accessibilité des TIC.

REMARQUE 3 : L’énoncé sur l'accessibilité et les pages d’aide sont deux exemples de diffusion de renseignements sur les produits.

602.3 Documentation de soutien électronique

La documentation au format électronique, y compris le soutien en libre-service sur le Web, doit être conforme aux critères de succès de niveau A et de niveau AA ainsi qu’aux exigences de conformité dans les WCAG 2.0 (incorporées par renvoi, voir l’article 702.10.1).

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3 : Lorsque la documentation fait partie intégrante des TIC, elle est fournie par l’intermédiaire de l’interface utilisateur qui est accessible.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

Reformulation stylistique

Mise à jour explicative

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3 : Lorsque la documentation fait partie intégrante des TIC, elle est fournie par l’intermédiaire de l’interface utilisateur qui est accessible.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant des capacités cognitives, linguistiques et d'apprentissage limitées).

REMARQUE 3 : Lorsque la documentation est intégrée dans les TIC, elle est soumise aux exigences d’accessibilité du présent document.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

Changement fonctionnel

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant des capacités cognitives, linguistiques et d'apprentissage limitées).

REMARQUE 3 : Lorsque la documentation est intégrée dans les TIC, elle est soumise aux exigences d’accessibilité du présent document.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

602.4 Autres formats pour la documentation de soutien non électronique

Lorsque la documentation de soutien est uniquement fournie dans des formats non électroniques, d’autres formats utilisables par les personnes handicapées doivent être fournis sur demande.

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3 : Lorsque la documentation fait partie intégrante des TIC, elle est fournie par l’intermédiaire de l’interface utilisateur qui est accessible.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

Reformulation stylistique

Mise à jour explicative

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3 : Lorsque la documentation fait partie intégrante des TIC, elle est fournie par l’intermédiaire de l’interface utilisateur qui est accessible.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant des capacités cognitives, linguistiques et d'apprentissage limitées).

REMARQUE 3 : Lorsque la documentation est intégrée dans les TIC, elle est soumise aux exigences d’accessibilité du présent document.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

Changement fonctionnel

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant des capacités cognitives, linguistiques et d'apprentissage limitées).

REMARQUE 3 : Lorsque la documentation est intégrée dans les TIC, elle est soumise aux exigences d’accessibilité du présent document.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

Liste des tableaux

603 Services de soutien

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

603.1 Généralités

Les services de soutien en matière de TIC, y compris, mais sans s’y limiter, les centres d’assistance, les centres d’appel, les services de formation et le soutien technique automatisé en libre-service, doivent être conformes à la clause 603.

12.2.1 Généralités (information)

Les services d’appui en matière de TIC comprennent, sans s’y limiter, les centres d’assistance, les centres d’appel, le soutien technique, les services de relais et les services de formation.

Reformulation stylistique

12.2.1 Généralités (information)

Les services d’appui en matière de TIC comprennent, sans s’y limiter, les centres d’assistance, les centres d’appel, le soutien technique, les services de relais et les services de formation.

12.2.1 Généralités (information)

Les services d’appui en matière de TIC comprennent, sans s’y limiter, les centres d’assistance, les centres d’appel, le soutien technique, les services de relais et les services de formation.

12.2.1 Généralités (information)

Les services d’appui en matière de TIC comprennent, sans s’y limiter, les centres d’assistance, les centres d’appel, le soutien technique, les services de relais et les services de formation.

603.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent inclure des renseignements sur les caractéristiques d’accessibilité et de compatibilité exigées par la clause 602.2.

12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent fournir des renseignements sur les caractéristiques d’accessibilité et de compatibilité inclus dans la documentation du produit.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

Reformulation stylistique

Mise à jour explicative

12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent fournir des renseignements sur les caractéristiques d’accessibilité et de compatibilité inclus dans la documentation du produit.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent fournir des renseignements sur les caractéristiques d’accessibilité et de compatibilité inclus dans la documentation du produit.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent fournir des renseignements sur les caractéristiques d’accessibilité et de compatibilité inclus dans la documentation du produit.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

603.3 Adaptation des besoins en communication

Les services de soutien doivent être fournis directement à l’utilisateur ou par l’intermédiaire d’une référence à un point de contact. Ces services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées.

12.2.3 Communication efficace

Les services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

Reformulation stylistique

Mise à jour explicative

12.2.3 Communication efficace

Les services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

12.2.3 Communication efficace

Les services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

12.2.3 Communication efficace

Les services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

Liste des tableaux

Dispositions non mises en correspondance

Article 508 révisé

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

402.3 Volume

Les TIC qui transmettent du son, y compris la sortie vocale exigée par la clause 402.2, doivent permettre de régler le volume et l’amplification de sortie conformément à la clause 402.3.

EXCEPTION : Les TIC conformes à la clause 412.2 n’ont pas à être conformes à la clause 402.3.

407.1 Généralités

Le cas échéant, les pièces manœuvrables utilisées dans le fonctionnement normal des TIC doivent être conformes à la clause 407.

407.2 Contraste

Le cas échéant, les touches et les commandes doivent se distinguer avec netteté des surfaces en arrière-plan. Les caractères et les symboles doivent se distinguer avec netteté des surfaces en arrière-plan, soit au moyen de caractères ou de symboles de couleur claire sur fond sombre, soit de caractères ou de symboles de couleur sombre sur fond clair.

407.3 Commandes d’entrée

Au moins une commande d’entrée conforme à la clause 407.3 doit être fournie pour chaque fonction.

EXCEPTION : Les dispositifs à usage personnel avec commandes d’entrée que l’on peut distinguer de manière audible sans activation et qui fonctionnent de manière tactile n’ont pas à être conformes à la clause 407.3.

407.5 Réponse minutée

Lorsqu’une réponse minutée est requise, l’utilisateur doit être averti visuellement, ainsi que de manière tactile et auditive, et il doit avoir la possibilité d’indiquer qu’il a besoin de plus de temps.27

407.8 Hauteur et profondeur de portée

Au moins un de chaque type de pièce manœuvrable des TIC fixes doit être à une hauteur conforme à la clause 407.8.2 ou 407.8.3 selon sa position établie par le plan de référence vertical spécifié à la clause 407.8.1 pour une portée latérale ou une portée avant. Les pièces manœuvrables utilisées avec sortie vocale qui sont requises par la clause 402.2 ne doivent pas être le seul type de pièce manœuvrable conforme à la clause 407.8, sauf si la pièce est la seule pièce manœuvrable de son type.28

407.8.1 Plan de référence vertical

Les pièces manœuvrables doivent être positionnées pour une portée latérale ou une portée avant déterminée par rapport à un plan de référence vertical. Le plan de référence vertical doit être situé conformément à la clause 407.8.2 ou 407.8.3.

407.8.2 Portée latérale

Les pièces manœuvrables des TIC dotées d’une portée latérale doivent être conformes à la clause 407.8.2.1 ou 407.8.2.2. Le plan de référence vertical doit être centré sur la pièce manœuvrable et placé sur le bord avant de la saillie maximale des TIC, dans la longueur du plan de référence vertical. Lorsqu’une portée latérale exige d’atteindre au-dessus d’une partie des TIC, la hauteur de cette partie des TIC doit être au maximum de 865 mm (34 po).

408.1 Généralités

Lorsqu’ils sont fournis, les écrans d’affichage doivent être conformes à la norme 408.

408.3 Clignotement

Lorsque les TIC émettent des lumières sous forme de flash, il ne doit pas y avoir plus de trois flashs dans un intervalle d’une seconde.

EXCEPTION : Les flashs qui ne dépassent pas le seuil de flash générique et le seuil de flash rouge définis dans les WCAG 2.0 (incorporés par renvoi, voir l’article 702.10.1) n’ont pas à être conformes à la clause 408.3. 29

411.1 Généralités

Lorsqu’ils sont fournis, les signaux ou indices sonores ne doivent pas être utilisés comme seul moyen de véhiculer de l’information, d’indiquer une action ou de solliciter une réponse.30

412.1 Généralités

Les TIC qui permettent une communication vocale bidirectionnelle doivent être conformes à la clause 412.

412.2 Gain de volume

Les TIC qui permettent une communication vocale bidirectionnelle doivent être conformes à la clause 412.2.1 ou 412.2.2.

412.3 Réduction des interférences et couplage magnétique

Lorsque les TIC fournissent une sortie par un combiné ou un autre type de transducteur audio qui est normalement tenu à l’oreille, elles doivent réduire les interférences avec les technologies auditives et fournir un moyen efficace de couplage magnétique sans fil conformément à la clause 412.3.1 ou 412.3.2.

412.8 Prise en charge d’ATS existant

L’équipement ou les systèmes des TIC avec communication vocale bidirectionnelle qui ne fournissent pas eux-mêmes la fonctionnalité ATS doivent être conformes à la clause 412.8.

412.8.1 Connexion ATS

Les TIC doivent inclure un point de connexion non acoustique standard pour les ATS.

412.8.2 Transmission vocale et auditive

Les TIC doivent fournir un microphone qui peut être activé et désactivé pour permettre à l’utilisateur de combiner la capacité vocale avec l’utilisation d’un ATS.

412.8.3 Compatibilité du signal

Les TIC doivent prendre en charge tous les protocoles de signaux ATS standard librement accessibles et couramment utilisés par différents fabricants lorsque le système interagit avec le réseau téléphonique commuté (RTC).

412.8.4 Messagerie vocale et autres systèmes de messagerie

Lorsqu’ils sont fournis, les systèmes de messagerie vocale, de réception automatique, de réponse vocale interactive et d’identification de l’appelant doivent être utilisables avec un ATS.

413.1 Généralités

Lorsque les TIC affichent ou traitent des vidéos avec synchronisation sonore, elles doivent fournir une technologie de traitement des sous-titres codés conforme à la clause 413.1.1 ou 413.1.2.

414.1 Généralités

Lorsque les TIC affichent ou traitent des vidéos avec synchronisation sonore, elles doivent fournir une technologie de traitement des descriptions audio conforme à la clause 414.1.1 ou 414.1.2.

415.1 Généralités

Lorsque les TIC affichent des vidéos avec synchronisation sonore, elles doivent permettre à l’utilisateur de contrôler les sous-titres et les descriptions audio conformes à la clause 415.1.

EXCEPTION : Les dispositifs à usage personnel n’ont pas à être conformes à la clause 415.1 à condition que les sous-titres et les descriptions audio puissent être activés par les paramètres de la plateforme à l’échelle du système.

502.1 Généralités

Le logiciel doit interagir avec la technologie d’assistance et être conforme à la clause 502.

EXCEPTION : Les TIC conformes à la clause 402 n’ont pas à être conformes à la clause 502.

502.4 Caractéristiques d’accessibilité de la plateforme

Les plateformes et les logiciels de plateforme doivent être conformes aux exigences de la norme ANSI/HFES 200.2, Human Factors Engineering of Software User interfaces — Part 2: Accessibility (2008) (incorporée par renvoi, voir l’article 702.4.1) énumérées ci-dessous :

  1. L’article 10.6.7 permet aux utilisateurs de choisir un équivalent visuel pour la sortie audio.31

502.4 Caractéristiques d’accessibilité de la plateforme

Les plateformes et les logiciels de plateforme doivent être conformes aux exigences de la norme ANSI/HFES 200.2, Human Factors Engineering of Software User interfaces — Part 2: Accessibility (2008) (incorporée par renvoi, voir l’article 702.4.1) énumérées ci-dessous :

  1. L’article 10.6.8 synchronise les équivalents audios pour les événements visuels.32

502.4 Caractéristiques d’accessibilité de la plateforme

Les plateformes et les logiciels de plateforme doivent être conformes aux exigences de la norme ANSI/HFES 200.2, Human Factors Engineering of Software User interfaces — Part 2: Accessibility (2008) (incorporée par renvoi, voir l’article 702.4.1) énumérées ci-dessous :

  1. L’article 10.6.9 fournit des services de sortie vocale.33

504.2.2 Exportation de fichier PDF

Les outils-auteurs capables d’exporter des fichiers PDF qui sont conformes à la norme ISO 32000-1:2008 (PDF 1.7) doivent également pouvoir exporter des fichiers PDF conformes à la norme ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1) (incorporée par renvoi, voir l’article 702.3.1).34

Liste des tableaux

EN 301 549

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

4.2.11 Confidentialité

Lorsque les TIC fournissent des fonctions d’accessibilité, elles préservent la vie privée des utilisateurs de ces fonctions au même niveau que celle des autres utilisateurs.

REMARQUE : Permettre la connexion de casques d’écoute personnels pour une écoute privée, ne pas fournir une version parlée des caractères masqués et permettre à l’utilisateur de contrôler les données juridiques, financières et personnelles sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

4.2.11 Confidentialité

Lorsque les TIC fournissent des fonctions d’accessibilité, elles préservent la vie privée des utilisateurs de ces fonctions au même niveau que celle des autres utilisateurs.

REMARQUE : Permettre la connexion de casques d’écoute personnels pour une écoute privée, ne pas fournir une version parlée des caractères masqués et permettre à l’utilisateur de contrôler les données juridiques, financières et personnelles sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

4.2.11 Confidentialité

Lorsque les TIC fournissent des fonctions d’accessibilité, elles préservent la vie privée des utilisateurs de ces fonctions au même niveau que celle des autres utilisateurs.

REMARQUE : Permettre la connexion de casques d’écoute personnels pour une écoute privée, ne pas fournir une version parlée des caractères masqués et permettre à l’utilisateur de contrôler les données juridiques, financières et personnelles sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

4.2.11 Confidentialité

Lorsque les TIC fournissent des fonctions d’accessibilité, elles préservent la vie privée des utilisateurs de ces fonctions au même niveau que celle des autres utilisateurs.

REMARQUE : Permettre la connexion de casques d’écoute personnels pour une écoute privée, ne pas fournir une version parlée des caractères masqués et permettre à l’utilisateur de contrôler les données juridiques, financières et personnelles sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

4.2.9 Réduction au minimum du risque de provoquer des crises photosensibles

Lorsque les TIC prévoient des modes de fonctionnement visuels, elles fournissent au moins un mode de fonctionnement qui réduit au minimum le risque de provoquer des crises photosensibles.

REMARQUE : La limitation de la zone et du nombre de flashs par seconde peut contribuer au respect de cette clause.

4.2.9 Réduction au minimum du risque de provoquer des crises photosensibles

Lorsque les TIC prévoient des modes de fonctionnement visuels, elles fournissent au moins un mode de fonctionnement qui réduit au minimum le risque de provoquer des crises photosensibles.

REMARQUE : La limitation de la zone et du nombre de flashs par seconde peut contribuer au respect de cette clause.

4.2.9 Réduction au minimum du risque de provoquer des crises photosensibles

Lorsque les TIC prévoient des modes de fonctionnement visuels, elles fournissent au moins un mode de fonctionnement qui réduit au minimum le risque de provoquer des crises photosensibles. Ceci est essentiel pour les utilisateurs chez qui des crises photosensibles peuvent être déclenchées.

REMARQUE : La limitation de la zone et du nombre de flashs par seconde peut contribuer au respect de cette clause.

4.2.9 Réduction au minimum du risque de provoquer des crises photosensibles

Lorsque les TIC prévoient des modes de fonctionnement visuels, elles fournissent au moins un mode de fonctionnement qui réduit au minimum le risque de provoquer des crises photosensibles. Ceci est essentiel pour les utilisateurs chez qui des crises photosensibles peuvent être déclenchées.

REMARQUE : La limitation de la zone et du nombre de flashs par seconde peut contribuer au respect de cette clause.

5.1.2.1 Fonctions restreintes

Lorsque les TIC ont des fonctions restreintes, elles doivent satisfaire aux exigences énoncées dans les clauses 5.2 à 13, selon le cas.

REMARQUE 1 : Les TIC peuvent restreindre certaines de ses fonctions, mais pas toutes. Seules les fonctions restreintes doivent se conformer aux exigences de la clause 5.1.

REMARQUE 2 : Les exigences de la présente clause remplacent celles des clauses 5.2 à 13 qui indiquent expressément qu’elles ne s’appliquent pas aux fonctions restreintes. Cela peut être dû au fait qu’elles concernent la compatibilité avec les technologies d’assistance ou la capacité de l’utilisateur de régler les paramètres d’accessibilité du système dans les produits aux fonctions restreintes (p. ex. les produits qui empêchent l’accès au panneau de commande des paramètres du système).

5.1.2.1 Fonctions restreintes

Lorsque les TIC ont des fonctions restreintes, elles doivent satisfaire aux exigences énoncées dans les clauses 5.2 à 13, selon le cas.

REMARQUE 1 : Les TIC peuvent restreindre certaines de ses fonctions, mais pas toutes. Seules les fonctions restreintes doivent se conformer aux exigences de la clause 5.1.

REMARQUE 2 : Les exigences de la présente clause remplacent celles des clauses 5.2 à 13 qui indiquent expressément qu’elles ne s’appliquent pas aux fonctions restreintes. Cela peut être dû au fait qu’elles concernent la compatibilité avec les technologies d’assistance ou la capacité de l’utilisateur de régler les paramètres d’accessibilité du système dans les produits aux fonctions restreintes (p. ex. les produits qui empêchent l’accès au panneau de commande des paramètres du système).

5.1.2.1 Fonctions restreintes

Lorsque les TIC ont des fonctions restreintes, elles doivent satisfaire aux exigences énoncées dans les clauses 5.2 à 13, selon le cas.

REMARQUE 1 : Les TIC peuvent restreindre certaines de ses fonctions, mais pas toutes. Seules les fonctions restreintes doivent se conformer aux exigences de la clause 5.1.

REMARQUE 2 : Les exigences de la présente clause remplacent celles des clauses 5.2 à 13 qui indiquent expressément qu’elles ne s’appliquent pas aux fonctions restreintes. Cela peut être dû au fait qu’elles concernent la compatibilité avec les technologies d’assistance ou la capacité de l’utilisateur de régler les paramètres d’accessibilité du système dans les produits aux fonctions restreintes (p. ex. les produits qui empêchent l’accès au panneau de commande des paramètres du système).

5.1.3.10 Sortie sonore non interférente

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC ne doivent pas lire automatiquement, en même temps, toute sortie audible interférente d’une durée supérieure à trois secondes.

5.1.3.10 Sortie sonore non interférente

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC ne doivent pas lire automatiquement, en même temps, toute sortie audible interférente d’une durée supérieure à trois secondes.

5.1.3.10 Sortie sonore non interférente

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC ne doivent pas lire automatiquement, en même temps, toute sortie audible interférente d’une durée supérieure à trois secondes.

5.1.3.10 Sortie sonore non interférente

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC ne doivent pas lire automatiquement, en même temps, toute sortie audible interférente d’une durée supérieure à trois secondes.

5.1.3.14 Langues parlées

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit être dans la même langue humaine que le contenu affiché fourni, sauf :

  1. pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement;
  2. lorsque le contenu est généré à l’extérieur et n’est pas sous le contrôle du fournisseur de TIC, La clause 5.1.3.14 n’est pas tenue de s’appliquer aux langues non prises en charge par le synthétiseur vocal de TIC;
  3. pour les langues affichées qui ne peuvent pas être sélectionnées à l’aide d’un accès non visuel;
  4. lorsque l’utilisateur choisit explicitement une langue vocale différente de la langue du contenu affiché.

5.1.3.14 Langues parlées

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit être dans la même langue humaine que le contenu affiché fourni, sauf :

  1. pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement;
  2. lorsque le contenu est généré à l’extérieur et n’est pas sous le contrôle du fournisseur de TIC, La clause 5.1.3.14 n’est pas tenue de s’appliquer aux langues non prises en charge par le synthétiseur vocal de TIC;
  3. pour les langues affichées qui ne peuvent pas être sélectionnées à l’aide d’un accès non visuel;
  4. lorsque l’utilisateur choisit explicitement une langue vocale différente de la langue du contenu affiché.

5.1.3.14 Langues parlées

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit être dans la même langue humaine que le contenu affiché fourni, sauf :

  1. pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement;
  2. lorsque le contenu est généré à l’extérieur et n’est pas sous le contrôle du fournisseur de TIC, la présente clause 5.1.3.14 n’est pas tenue de s’appliquer aux langues non prises en charge par le synthétiseur vocal de TIC;
  3. pour les langues affichées qui ne peuvent pas être sélectionnées à l’aide d’un accès non visuel;
  4. lorsque l’utilisateur choisit explicitement une langue vocale différente de la langue du contenu affiché.
Reformulation stylistique

5.1.3.14 Langues parlées

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit être dans la même langue humaine que le contenu affiché fourni, sauf :

  1. pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement;
  2. lorsque le contenu est généré à l’extérieur et n’est pas sous le contrôle du fournisseur de TIC, la présente clause 5.1.3.14 n’est pas tenue de s’appliquer aux langues non prises en charge par le synthétiseur vocal de TIC;
  3. pour les langues affichées qui ne peuvent pas être sélectionnées à l’aide d’un accès non visuel;
  4. lorsque l’utilisateur choisit explicitement une langue vocale différente de la langue du contenu affiché.

5.1.3.15 Détermination non visuelle des erreurs

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte et qu’une erreur de saisie est automatiquement détectée, la sortie vocale doit identifier et décrire l’élément qui est en erreur.

5.1.3.15 Détermination non visuelle des erreurs

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte et qu’une erreur de saisie est automatiquement détectée, la sortie vocale doit identifier et décrire l’élément qui est en erreur.

5.1.3.15 Détermination non visuelle des erreurs

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte et qu’une erreur de saisie est automatiquement détectée, la sortie vocale doit identifier et décrire l’élément qui est en erreur.

5.1.3.15 Détermination non visuelle des erreurs

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte et qu’une erreur de saisie est automatiquement détectée, la sortie vocale doit identifier et décrire l’élément qui est en erreur.

5.1.5 Sortie visuelle pour renseignement audio

Lorsque des renseignements audio préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, les TIC doivent fournir des renseignements visuels équivalents aux résultats sonores préenregistrés.

REMARQUE : Ce renseignement visuel peut prendre la forme de sous-titre ou de transcriptions textuelles.

5.1.5 Sortie visuelle pour renseignement audio

Lorsque des renseignements audio préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, les TIC doivent fournir des renseignements visuels équivalents aux résultats sonores préenregistrés.

REMARQUE : Ce renseignement visuel peut prendre la forme de sous-titre ou de transcriptions textuelles.

5.1.5 Sortie visuelle pour renseignement audio

Où des renseignements audio sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, les TIC doivent fournir des renseignements visuels équivalents aux résultats sonores.

REMARQUE : Ce renseignement visuel peut prendre la forme de sous-titre ou de transcriptions textuelles.

Reformulation stylistique

5.1.5 Sortie visuelle pour renseignement audio

Où des renseignements audio sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, les TIC doivent fournir des renseignements visuels équivalents aux résultats sonores.

REMARQUE : Ce renseignement visuel peut prendre la forme de sous-titre ou de transcriptions textuelles.

5.1.6.1 Fonction restreinte

Lorsque la fonction des TIC est restreinte aux claviers ou aux interfaces clavier, toutes les fonctions doivent pouvoir fonctionner sans vision, comme l’exige la clause 5.1.3.

5.1.6.1 Fonction restreinte

Lorsque la fonction des TIC est restreinte aux claviers ou aux interfaces clavier, toutes les fonctions doivent pouvoir fonctionner sans vision, comme l’exige la clause 5.1.3.

5.1.6.1 Fonction restreinte

Lorsque la fonction des TIC est restreinte aux claviers ou aux interfaces clavier, toutes les fonctions doivent pouvoir fonctionner sans vision, comme l’exige la clause 5.1.3.

5.1.6.1 Fonction restreinte

Lorsque la fonction des TIC est restreinte aux claviers ou aux interfaces clavier, toutes les fonctions doivent pouvoir fonctionner sans vision, comme l’exige la clause 5.1.3.

5.1.6.2 Focus de la saisie

Lorsque la fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier et que le focus de la saisie peut être déplacé vers un élément d’interface utilisateur, il doit être possible d’éloigner le focus de la saisie de cet élément en utilisant le même mécanisme, afin d’éviter de piéger le focus de la saisie.

5.1.6.2 Focus de la saisie

Lorsque la fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier et que le focus de la saisie peut être déplacé vers un élément d’interface utilisateur, il doit être possible d’éloigner le focus de la saisie de cet élément en utilisant le même mécanisme, afin d’éviter de piéger le focus de la saisie.

5.1.6.2 Focus de la saisie

Lorsque la fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier et que le focus de la saisie peut être déplacé vers un élément d’interface utilisateur, il doit être possible d’éloigner le focus de la saisie cet élément en utilisant le même mécanisme, afin d’éviter de piéger le focus de la saisie.

5.1.6.2 Focus de la saisie

Lorsque la fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier et que le focus de la saisie peut être déplacé vers un élément d’interface utilisateur, il doit être possible d’éloigner le focus de la saisie de cet élément en utilisant le même mécanisme, afin d’éviter de piéger le focus de la saisie.

55.1.7 Accès sans capacité vocale

Lorsque la capacité vocale est nécessaire pour faire fonctionner des fonctions restreintes des TIC, celles-ci doivent prévoir au moins un mode de fonctionnement utilisant un autre mécanisme de saisie ne nécessitant pas la capacité vocale.

Nouvelle exigence

55.1.7 Accès sans capacité vocale

Lorsque la capacité vocale est nécessaire pour faire fonctionner des fonctions restreintes des TIC, celles-ci doivent prévoir au moins un mode de fonctionnement utilisant un autre mécanisme de saisie ne nécessitant pas la capacité vocale.

6.2.1.1 Communication par TTR

Lorsque les TIC permettent la communication vocale bidirectionnelle pour un contexte d’utilisation particulière, les TIC permettent à un utilisateur de communiquer avec un autre utilisateur par TTR.

REMARQUE 1 : La capacité de TTR peut être réglée par défaut ou ajoutée.

REMARQUE 2 : La fourniture des communications par TTR peut nécessiter des services, du matériel ou des logiciels supplémentaires qui peuvent être fournis séparément ou ensemble.

6.2.1.1 Communication par TTR

Lorsque les TIC permettent la communication vocale bidirectionnelle pour un contexte d’utilisation particulière, les TIC permettent à un utilisateur de communiquer avec un autre utilisateur par TTR.

REMARQUE 1 : La capacité de TTR peut être réglée par défaut ou ajoutée.

REMARQUE 2 : La fourniture des communications par TTR peut nécessiter des services, du matériel ou des logiciels supplémentaires qui peuvent être fournis séparément ou ensemble.

6.2.1.1 Communication par TTR

Lorsque le mode des TIC prévoit un moyen de communication vocale bidirectionnelle, les TIC doivent fournir un moyen de communication vocale bidirectionnelle par TTR, sauf si cela nécessite des modifications de conception pour ajouter du matériel d'entrée ou de sortie aux TIC.

REMARQUE 1 : Cette exigence inclut les produits qui ne sont pas dotés de fonctionnalités d’affichage physique ou de saisie de texte mais qui ont la capacité de se connecter à des périphériques qui possèdent de telles fonctionnalités. Elle inclut également les TIC intermédiaires situés entre les points finaux de la communication.

REMARQUE 2 : Il n’est pas nécessaire d’ajouter : un écran matériel, un clavier matériel ou du matériel pour permettre de se connecter à un écran ou à un clavier, filaire ou sans fil, si ce matériel n’est normalement pas fourni.

REMARQUE 3 : Aux fins de l’interopérabilité, la Recommandation T.140 de l’UIT-T est largement utilisée.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

6.2.1.1 Communication par TTR

Lorsque le mode des TIC prévoit un moyen de communication vocale bidirectionnelle, les TIC doivent fournir un moyen de communication vocale bidirectionnelle par TTR, sauf si cela nécessite des modifications de conception pour ajouter du matériel d'entrée ou de sortie aux TIC.

REMARQUE 1 : Cette exigence inclut les produits qui ne sont pas dotés de fonctionnalités d’affichage physique ou de saisie de texte mais qui ont la capacité de se connecter à des périphériques qui possèdent de telles fonctionnalités. Elle inclut également les TIC intermédiaires situés entre les points finaux de la communication.

REMARQUE 2 : Il n’est pas nécessaire d’ajouter : un écran matériel, un clavier matériel ou du matériel pour permettre de se connecter à un écran ou à un clavier, filaire ou sans fil, si ce matériel n’est normalement pas fourni.

REMARQUE 3 : Aux fins de l’interopérabilité, la Recommandation T.140 de l’UIT-T est largement utilisée.

6.2.1.2 Voix et texte simultanés

Lorsque les TIC permettent la communication vocale bidirectionnelle pour un contexte d’utilisation particulière et permettent à un utilisateur de communiquer avec un autre utilisateur par TTR, elles prévoient un mécanisme permettant de choisir un mode de fonctionnement qui permet la communication vocale et textuelle simultanée.

REMARQUE : le fonctionnement simultané de la communication vocale et de la communication par TTR peut permettre que la communication par TTR remplace ou prenne en charge la communication vocale et d’autres renseignements tels que les numéros, les montants en devises et l’épellation des noms.

6.2.1.2 Voix et texte simultanés

Lorsque les TIC permettent la communication vocale bidirectionnelle pour un contexte d’utilisation particulière et permettent à un utilisateur de communiquer avec un autre utilisateur par TTR, elles prévoient un mécanisme permettant de choisir un mode de fonctionnement qui permet la communication vocale et textuelle simultanée.

REMARQUE : le fonctionnement simultané de la communication vocale et de la communication par TTR peut permettre que la communication par TTR remplace ou prenne en charge la communication vocale et d’autres renseignements tels que les numéros, les montants en devises et l’épellation des noms.

6.2.1.2 Voix et texte simultanés

Lorsque les TIC prévoient un moyen de communication vocale bidirectionnelle et permettent aux utilisateurs de communiquer par TTR, elles doivent permettre la communication vocale et textuelle simultanément par l’intermédiaire d’une connexion utilisateur unique.

REMARQUE 1 : Dans le cas d’une communication entre plusieurs participants, comme dans un système de conférence, il est permis (mais pas obligatoire ou nécessairement recommandé) que le TTR soit traité dans un champ d’affichage unique et que « la prise de parole à tour de rôle » soit nécessaire afin d’éviter toute confusion (de la même manière que la prise de parole à tour de rôle est requise pour ceux qui présentent ou parlent moyennant une capacité vocale).

REMARQUE 2 : Dans le cas d’une communication entre plusieurs participants, la pratique exemplaire consiste à lever la main pour que les utilisateurs de capacité vocale et les utilisateurs du TTR soient traités de la même manière, afin que les utilisateurs de capacité vocale et de TTR soient placés dans la même file d’attente.

REMARQUE 3 : Dans le cas d’un système de conférence entre plusieurs participants dont l’une des fonctions est le clavardage – le TTR (tout comme la capacité vocale) est généralement séparé de la fonction de clavardage pour que celle-ci n’interfère pas avec le TTR (c.-à-d. les personnes peuvent envoyer des messages dans la zone de clavardage pendant qu’une personne présente des renseignements ou parle avec le TTR – de la même manière que les personnes s’envoient des messages en utilisant la fonction de clavardage pendant que des personnes utilisent la capacité vocale pour parler). Les utilisateurs de TTR utiliseraient alors le TTR pour présenter des renseignements et la fonction de clavardage pour envoyer des messages pendant que les autres présentent des renseignements (par la capacité vocale ou le TTR).

REMARQUE 4 : La possibilité de faire fonctionner la capacité vocale et le TTR simultanément (et séparément de la fonction de clavardage) peut également permettre à la zone de TTR de prendre en charge le sous-titrage lorsque quelqu’un parle (et elle n’est donc pas utilisée pour le TTR puisque ce n’est pas au tour de l’utilisateur du TTR de prendre la parole).

REMARQUE 5 : Lorsque le logiciel côté serveur tout comme le matériel et les logiciels locaux sont nécessaires pour fournir la communication vocale, mais qu’aucune partie ne peut prendre en charge la communication vocale sans l’autre et qu’elles sont vendues comme une seule unité pour la fonction de communication vocale, les composants des logiciels locaux et du serveur sont considérés comme un seul produit.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

6.2.1.2 Voix et texte simultanés

Lorsque les TIC prévoient un moyen de communication vocale bidirectionnelle et permettent aux utilisateurs de communiquer par TTR, elles doivent permettre la communication vocale et textuelle simultanément par l’intermédiaire d’une connexion utilisateur unique.

REMARQUE 1 : Dans le cas d’une communication entre plusieurs participants, comme dans un système de conférence, il est permis (mais pas obligatoire ou nécessairement recommandé) que le TTR soit traité dans un champ d’affichage unique et que « la prise de parole à tour de rôle » soit nécessaire afin d’éviter toute confusion (de la même manière que la prise de parole à tour de rôle est requise pour ceux qui présentent ou parlent moyennant une capacité vocale).

REMARQUE 2 : Dans le cas d’une communication entre plusieurs participants, la pratique exemplaire consiste à lever la main pour que les utilisateurs de capacité vocale et les utilisateurs du TTR soient traités de la même manière, afin que les utilisateurs de capacité vocale et de TTR soient placés dans la même file d’attente.

REMARQUE 3 : Dans le cas d’un système de conférence entre plusieurs participants dont l’une des fonctions est le clavardage – le TTR (tout comme la capacité vocale) est généralement séparé de la fonction de clavardage pour que celle-ci n’interfère pas avec le TTR (c.-à-d. les personnes peuvent envoyer des messages dans la zone de clavardage pendant qu’une personne présente des renseignements ou parle avec le TTR – de la même manière que les personnes s’envoient des messages en utilisant la fonction de clavardage pendant que des personnes utilisent la capacité vocale pour parler). Les utilisateurs de TTR utiliseraient alors le TTR pour présenter des renseignements et la fonction de clavardage pour envoyer des messages pendant que les autres présentent des renseignements (par la capacité vocale ou le TTR).

REMARQUE 4 : La possibilité de faire fonctionner la capacité vocale et le TTR simultanément (et séparément de la fonction de clavardage) peut également permettre à la zone de TTR de prendre en charge le sous-titrage lorsque quelqu’un parle (et elle n’est donc pas utilisée pour le TTR puisque ce n’est pas au tour de l’utilisateur du TTR de prendre la parole).

REMARQUE 5 : Lorsque le logiciel côté serveur tout comme le matériel et les logiciels locaux sont nécessaires pour fournir la communication vocale, mais qu’aucune partie ne peut prendre en charge la communication vocale sans l’autre et qu’elles sont vendues comme une seule unité pour la fonction de communication vocale, les composants des logiciels locaux et du serveur sont considérés comme un seul produit.

6.2.2.1 Affichage visuellement reconnaissable

Lorsque les TIC sont dotées de capacités d’envoi et de réception de TTR, l’affichage du texte envoyé doit être visuellement différenciable et séparé de l’affichage du texte reçu.

6.2.2.1 Affichage visuellement reconnaissable

Lorsque les TIC sont dotées de capacités d’envoi et de réception de TTR, l’affichage du texte envoyé doit être visuellement différenciable et séparé de l’affichage du texte reçu.

6.2.2.1 Affichage visuellement reconnaissable

Lorsque les TIC sont dotées de capacités d’envoi et de réception de TTR, l’affichage du texte envoyé doit être visuellement différenciable et séparé de l’affichage du texte reçu.

REMARQUE : La possibilité pour l’utilisateur de choisir entre l’affichage du texte d’envoi et de réception sur une ligne ou séparément, et avec des options de sélection, permet aux utilisateurs d’afficher le TTR dans le format qui leur convient le mieux. Cela permettrait aux utilisateurs de texte en braille d’utiliser un seul champ et d’intervenir à tour de rôle, mais aussi de faire apparaître le texte de la manière séquentielle dont ils peuvent avoir besoin ou qu’ils préfèrent.

Mise à jour explicative

6.2.2.1 Affichage visuellement reconnaissable

Lorsque les TIC sont dotées de capacités d’envoi et de réception de TTR, l’affichage du texte envoyé doit être visuellement différenciable et séparé de l’affichage du texte reçu.

REMARQUE : La possibilité pour l’utilisateur de choisir entre l’affichage du texte d’envoi et de réception sur une ligne ou séparément, et avec des options de sélection, permet aux utilisateurs d’afficher le TTR dans le format qui leur convient le mieux. Cela permettrait aux utilisateurs de texte en braille d’utiliser un seul champ et d’intervenir à tour de rôle, mais aussi de faire apparaître le texte de la manière séquentielle dont ils peuvent avoir besoin ou qu’ils préfèrent.

6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Lorsque les TIC présentent des capacités d’envoi et de réception de TTR, la direction de l’envoi et de la réception du texte doit pouvoir être déterminée par un programme informatique, à moins que la fonction de TTR soit une fonctionnalité restreinte.

REMARQUE : Le but de la clause 6.2.2.2 est de permettre aux lecteurs d’écran de différencier le texte entrant du texte sortant lorsque la fonction de TTR est utilisée.

6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Lorsque les TIC présentent des capacités d’envoi et de réception de TTR, la direction de l’envoi et de la réception du texte doit pouvoir être déterminée par un programme informatique, à moins que la fonction de TTR soit une fonctionnalité restreinte.

REMARQUE : Le but de cette clause est de permettre aux lecteurs d’écran de différencier le texte entrant du texte sortant lorsque la fonction de TTR est utilisée.

Reformulation stylistique

6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Lorsque les TIC présentent des capacités d’envoi et de réception de TTR, la direction de l’envoi et de la réception du texte doit pouvoir être déterminée par un programme informatique, à moins que la fonction de TTR soit mise en œuvre en tant que fonctionnalité restreinte.

REMARQUE : Cette clause permet aux lecteurs d’écran de différencier le texte entrant du texte sortant lorsque la fonction de TTR est utilisée.

Changement fonctionnel

Reformulation stylistique

6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Lorsque les TIC présentent des capacités d’envoi et de réception de TTR, la direction de l’envoi et de la réception du texte doit pouvoir être déterminée par un programme informatique, à moins que la fonction de TTR soit mise en œuvre en tant que fonctionnalité restreinte.

REMARQUE : Cette clause permet aux lecteurs d’écran de différencier le texte entrant du texte sortant lorsque la fonction de TTR est utilisée.

6.2.2.3 Identification des interlocuteurs

Lorsque les TIC sont dotées de capacités de TTR et offrent l’identification des interlocuteurs par capacité vocale, elles doivent fournir l’identification des interlocuteurs pour le TTR.

REMARQUE : Cela est nécessaire pour permettre aux participants utilisant la fonction de capacité vocale comme ceux utilisant la fonction de TTR de savoir qui communique à un moment donné, que ce soit par TTR ou capacité vocale.

Nouvelle exigence

6.2.2.3 Identification des interlocuteurs

Lorsque les TIC sont dotées de capacités de TTR et offrent l’identification des interlocuteurs par capacité vocale, elles doivent fournir l’identification des interlocuteurs pour le TTR.

REMARQUE : Cela est nécessaire pour permettre aux participants utilisant la fonction de capacité vocale comme ceux utilisant la fonction de TTR de savoir qui communique à un moment donné, que ce soit par TTR ou capacité vocale.

6.2.2.4 Indicateur visuel de l’audio avec TTR

Lorsque les TIC prévoient une communication vocale bidirectionnelle et qu’elles sont dotées de capacités de TTR, elles doivent fournir un indicateur visuel en temps réel de l’activité audio à l’écran.

REMARQUE 1 : L’indicateur visuel peut être une position de caractère simple sur l’écran qui clignote pour refléter l’activité audio, ou la présentation des renseignements d’une autre manière qui peut être à la fois visible par les utilisateurs voyants et transmis aux utilisateurs sourds-aveugles qui utilisent un écran braille.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

Nouvelle exigence

6.2.2.4 Indicateur visuel de l’audio avec TTR

Lorsque les TIC prévoient une communication vocale bidirectionnelle et qu’elles sont dotées de capacités de TTR, elles doivent fournir un indicateur visuel en temps réel de l’activité audio à l’écran.

REMARQUE 1 : L’indicateur visuel peut être une position de caractère simple sur l’écran qui clignote pour refléter l’activité audio, ou la présentation des renseignements d’une autre manière qui peut être à la fois visible par les utilisateurs voyants et transmis aux utilisateurs sourds-aveugles qui utilisent un écran braille.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

6.2.3 Interopérabilité

Lorsque les TIC dotées d’une fonction de TTR fonctionnent avec d’autres TIC dotées d’une fonction de TTR (comme l’exige 6.2.1.1), elles doivent prendre en charge au moins un des quatre mécanismes d’interopérabilité de TTR décrits ci-dessous :

  1. l’interopérabilité des TIC sur le réseau téléphonique commuté (RTC), avec d’autres TIC qui se raccordent directement au RTC, comme le décrit la Recommandation V.18 de l’UIT-T ou l’une de ses annexes pour les signaux de téléphonie texte à l’interface du RTC;
  2. l’interopérabilité des TIC avec d’autres TIC à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initiation de session (SIP) et du texte en temps réel conforme à RFC 4103;
  3. l’interopérabilité des TIC avec d’autres TIC dotées de TTR conformes aux protocoles du sous-système multimédia IP (IMS) conformément aux spécifications TS 126 114, TS 122 173 et TS 134 229;
  4. l’interopérabilité des TIC avec d’autres TIC utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible. Cette spécification commune comprend une méthode permettant d’indiquer la perte ou la corruption de caractères.

6.2.3 Interopérabilité

Lorsque les TIC dotées d’une fonction de TTR fonctionnent avec d’autres TIC dotées d’une fonction de TTR (comme l’exige la clause 6.2.1.1), elles doivent prendre en charge au moins un des quatre mécanismes d’interopérabilité de TTR décrits ci-dessous :

  1. l’interopérabilité des TIC sur le réseau téléphonique commuté (RTC), avec d’autres TIC qui se raccordent directement au RTC, comme le décrit la Recommandation V.18 de l’UIT-T ou l’une de ses annexes pour les signaux de téléphonie texte à l’interface du RTC;
  2. l’interopérabilité des TIC avec d’autres TIC à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initiation de session (SIP) et du texte en temps réel conforme à RFC 4103 de l’IETF;
  3. l’interopérabilité des TIC avec d’autres TIC dotées de TTR conformes aux protocoles du sous-système multimédia IP (IMS) conformément aux spécifications TS 126 114, TS 122 173 et TS 134 229 de l’ETSI;
  4. l’interopérabilité des TIC avec d’autres TIC utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible. Cette spécification commune comprend une méthode permettant d’indiquer la perte ou la corruption de caractères.

Reformulation stylistique

Mise à jour explicative

6.2.3 Interopérabilité

Lorsque les TIC dotées d’une fonction de TTR fonctionnent avec d’autres TIC dotées d’une fonction de TTR (comme l’exige la clause 6.2.1.1), elles doivent prendre en charge au moins un des quatre mécanismes d’interopérabilité de TTR applicables décrits ci-dessous :

  1. l’interopérabilité des TIC avec d’autres TIC raccordées directement au réseau téléphonique commuté (RTC), utilisant la Recommandation V.18 de l’UIT-T ou l’une de ses annexes pour les signaux de téléphonie texte à l’interface du RTC;
  2. l’interopérabilité des TIC avec d’autres TIC à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initiation de session (SIP) et du TTR en temps réel conforme à RFC 4103. Pour l’interopérabilité des TIC avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, l’ensemble des protocoles spécifiés dans TS 126 114, TS 122 173 et TS 134 229 de l’ETSI décrivent la façon dont RFC 4103 de l’IETF s’appliquerait;
  3. l’interopérabilité des TIC avec d’autres TIC utilisant des technologies autres que a ou b, ci-dessus, utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible pour les environnements dans lesquels ils fonctionneront. Cette spécification commune comprend une méthode permettant d’indiquer la perte ou la corruption de caractères.
  4. l’interopérabilité des TIC avec d’autres TIC utilisant une norme pour TTR qui a été mise en place aux fins d’utilisation dans un des environnements susmentionnés, et qui est compatible avec toutes les autres TIC actives qui prennent en charge la capacité vocale et le TTR dans l’environnement en question.

REMARQUE 1 : En pratique, de nouvelles normes sont mises en place comme un autre codec ou protocole, pris en charge parallèlement à la norme commune existante et utilisé lorsqu’il est compatible avec tous les composants de bout en bout, lorsque le développement technologique, associé à d’autres raisons, dont le développement sociétal et la rentabilité, peut rendre d’autres normes obsolètes.

REMARQUE 2 : Lorsque plusieurs technologies sont utilisées pour fournir la communication vocale, plusieurs mécanismes d’interopérabilité peuvent être nécessaires pour garantir que tous les utilisateurs peuvent utiliser le TTR.

EXEMPLE : Un système de conférence prenant en charge la communication vocale par une connexion Internet peut fournir une communication par TTR par une connexion Internet au moyen d’une méthode TTR exclusive (option c). Toutefois, que la méthode TTR soit libre ou exclusive, si le système de conférence offre aussi la communication par téléphone, il devra également prendre en charge les options a ou b pour garantir que le TTR est pris en charge par la connexion par téléphone.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.2.3 Interopérabilité

Lorsque les TIC dotées d’une fonction de TTR fonctionnent avec d’autres TIC dotées d’une fonction de TTR (comme l’exige la clause 6.2.1.1), elles doivent prendre en charge au moins un des quatre mécanismes d’interopérabilité de TTR applicables décrits ci-dessous :

  1. l’interopérabilité des TIC avec d’autres TIC raccordées directement au réseau téléphonique commuté (RTC), utilisant la Recommandation V.18 de l’UIT-T [i.23] ou l’une de ses annexes pour les signaux de téléphonie texte à l’interface du RTC;
  2. l’interopérabilité des TIC avec d’autres TIC à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initiation de session (SIP) et du TTR en temps réel conforme à RFC 4103 [i.13] . Pour l’interopérabilité des TIC avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, l’ensemble des protocoles spécifiés dans TS 126 114 [i.10], TS 122 173 [i.11] et TS 134 229 [i.12] de l’ETSI décrivent la façon dont RFC 4103 [i.13] de l’IETF s’appliquerait;
  3. l’interopérabilité des TIC avec d’autres TIC utilisant des technologies autres que a ou b, ci-dessus, utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible pour les environnements dans lesquels ils fonctionneront. Cette spécification commune comprend une méthode permettant d’indiquer la perte ou la corruption de caractères;
  4. l’interopérabilité des TIC avec d’autres TIC utilisant une norme pour TTR qui a été mise en place aux fins d’utilisation dans un des environnements susmentionnés, et qui est compatible avec toutes les autres TIC actives qui prennent en charge la capacité vocale et le TTR dans l’environnement en question.

REMARQUE 1 : En pratique, de nouvelles normes sont mises en place comme un autre codec ou protocole, pris en charge parallèlement à la norme commune existante et utilisé lorsqu’il est compatible avec tous les composants de bout en bout, lorsque le développement technologique, associé à d’autres raisons, dont le développement sociétal et la rentabilité, peut rendre d’autres normes obsolètes.

REMARQUE 2 : Lorsque plusieurs technologies sont utilisées pour fournir la communication vocale, plusieurs mécanismes d’interopérabilité peuvent être nécessaires pour garantir que tous les utilisateurs peuvent utiliser le TTR.

EXEMPLE : Un système de conférence prenant en charge la communication vocale par une connexion Internet peut fournir une communication par TTR par une connexion Internet au moyen d’une méthode TTR exclusive (option c). Toutefois, que la méthode TTR soit libre ou exclusive, si le système de conférence offre aussi la communication par téléphone, il devra également prendre en charge les options a ou b pour garantir que le TTR est pris en charge par la connexion par téléphone.

6.2.4 Réactivité du texte en temps réel

Lorsque les TIC permettent la saisie de TTR, cette saisie est transmise au réseau des TIC prenant en charge le TTR dans un délai d’une seconde après la saisie.

REMARQUE 1 : La saisie est considérée comme ayant été exécutée lorsque l’utilisateur a saisi suffisamment de caractères pour que les TIC établissent quels caractères envoyer.

REMARQUE 2 : La saisie différera selon que le système permet d’entrer le texte mot par mot (p. ex., la conversion de la voix en texte et la saisie du texte prédictif) ou d’entrer un caractère à la fois.

6.2.4 Réactivité du texte en temps réel

Lorsque les TIC permettent la saisie de TTR, cette saisie est transmise au réseau des TIC prenant en charge le TTR dans un délai d’une seconde après la saisie.

REMARQUE 1 : La saisie est considérée comme ayant été exécutée lorsque l’utilisateur a saisi suffisamment de caractères pour que les TIC établissent quels caractères envoyer.

REMARQUE 2 : La saisie différera selon que le système permet d’entrer le texte mot par mot (p. ex., la conversion de la voix en texte et la saisie du texte prédictif) ou d’entrer un caractère à la fois.

6.2.4 Réactivité du TTR

Lorsque les TIC permettent la saisie de TTR, cette saisie est transmise au réseau des TIC ou à la plateforme sur laquelle fonctionnent les TIC dans un délai de 500 ms à compter du moment où la plus petite unité de saisie de texte fiable est accessible aux TIC aux fins de transmission. Les retards attribuables à la performance de la plateforme ou du réseau ne doivent pas être inclus dans la limite de 500 ms.

REMARQUE 1 : Pour la saisie de caractère par caractère, la « plus petite unité de saisie de texte fiable » serait un caractère.

Pour la prédiction des mots, ce serait un mot. Pour certains systèmes de reconnaissance vocale, le texte peut ne pas quitter le logiciel de reconnaissance tant qu’un mot entier (ou une expression entière) n’a pas été prononcé. Dans ce cas, la plus petite unité de saisie de texte fiable accessible aux TIC serait le mot (ou l’expression).

REMARQUE 2 : La limite de 500 ms permet de conserver en mémoire tampon les caractères avant leur transmission de sorte que la transmission caractère par caractère ne soit pas nécessaire à moins que les caractères soient générés plus lentement que 1 caractère par 500 ms.

REMARQUE 3 : Un délai de 300 ms, ou moins, produit une meilleure impression de fluidité pour l'utilisateur.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

6.2.4 Réactivité du TTR

Lorsque les TIC permettent la saisie de TTR, cette saisie est transmise au réseau des TIC ou à la plateforme sur laquelle fonctionnent les TIC dans un délai de 500 ms à compter du moment où la plus petite unité de saisie de texte fiable est accessible aux TIC aux fins de transmission. Les retards attribuables à la performance de la plateforme ou du réseau ne doivent pas être inclus dans la limite de 500 ms.

REMARQUE 1 : Pour la saisie de caractère par caractère, la « plus petite unité de saisie de texte fiable » serait un caractère.

Pour la prédiction des mots, ce serait un mot. Pour certains systèmes de reconnaissance vocale, le texte peut ne pas quitter le logiciel de reconnaissance tant qu’un mot entier (ou une expression entière) n’a pas été prononcé. Dans ce cas, la plus petite unité de saisie de texte fiable accessible aux TIC serait le mot (ou l’expression).

REMARQUE 2 : La limite de 500 ms permet de conserver en mémoire tampon les caractères avant leur transmission de sorte que la transmission caractère par caractère ne soit pas nécessaire à moins que les caractères soient générés plus lentement que 1 caractère par 500 ms.

REMARQUE 3 : Un délai de 300 ms, ou moins, produit une meilleure impression de fluidité pour l'utilisateur.

6.4 Autres solutions de services vocaux

Lorsque les TIC permettent la communication vocale en temps réel ainsi que la messagerie vocale, la réception automatique ou la réponse vocale interactive, elles devraient permettre à l’utilisateur d’accéder aux renseignements et d’exécuter les tâches sans recourir à l’ouïe ou à la parole.

REMARQUE : Des solutions permettant de traiter les supports sons, texte et vidéo en temps réel pourraient répondre au besoin susmentionné.

6.4 Autres solutions de services vocaux

Lorsque les TIC permettent la communication vocale en temps réel ainsi que la messagerie vocale, la réception automatique ou la réponse vocale interactive, elles devraient permettre à l’utilisateur d’accéder aux renseignements et d’exécuter les tâches sans recourir à l’ouïe ou à la parole.

REMARQUE : Des solutions permettant de traiter les supports sons, texte et vidéo en temps réel pourraient répondre au besoin susmentionné.

6.4 Autres solutions de services vocaux

Lorsque les TIC permettent la communication vocale en temps réel ainsi que la messagerie vocale, la réception automatique ou la réponse vocale interactive, elles doivent permettre à l’utilisateur d’accéder aux renseignements et d’exécuter les tâches sans recourir à l’ouïe ou à la parole.

REMARQUE 1 : Les tâches qui impliquent à la fois l’utilisation de l'interface et la perception des renseignements exigeraient que l'interface et les renseignements soient accessibles sans recourir à la parole ou à l’ouïe.

REMARQUE 2 : Des solutions permettant de traiter les supports sons, TTR et vidéo en temps réel pourraient répondre au besoin susmentionné.

Changement fonctionnel

Mise à jour explicative

Reformulation stylistique

6.4 Autres solutions de services vocaux

Lorsque les TIC permettent la communication vocale en temps réel ainsi que la messagerie vocale, la réception automatique ou la réponse vocale interactive, elles doivent permettre à l’utilisateur d’accéder aux renseignements et d’exécuter les tâches sans recourir à l’ouïe ou à la parole.

REMARQUE 1 : Les tâches qui impliquent à la fois l’utilisation de l'interface et la perception des renseignements exigeraient que l'interface et les renseignements soient accessibles sans recourir à la parole ou à l’ouïe.

REMARQUE 2 : Des solutions permettant de traiter les supports sons, TTR et vidéo en temps réel pourraient répondre au besoin susmentionné.

6.5.5 Indicateur visuel de l’audio avec vidéo

Lorsque les TIC prévoient une communication vocale bidirectionnelle et qu’elles comprennent une fonctionnalité de vidéo en temps réel, elles doivent fournir un indicateur visuel en temps réel de l’activité audio.

REMARQUE 1 : L’indicateur visuel peut être un simple point visuel ou lumière LED, ou d’autre type d’indicateur marche-arrêt, qui clignote pour refléter l’activité audio.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

Nouvelle exigence

6.5.5 Indicateur visuel de l’audio avec vidéo

Lorsque les TIC prévoient une communication vocale bidirectionnelle et qu’elles comprennent une fonctionnalité de vidéo en temps réel, elles doivent fournir un indicateur visuel en temps réel de l’activité audio.

REMARQUE 1 : L’indicateur visuel peut être un simple point visuel ou lumière LED, ou d’autre type d’indicateur marche-arrêt, qui clignote pour refléter l’activité audio.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

6.5.6 Identification des interlocuteurs avec communication vidéo (langue des signes)

Lorsque les TIC prévoient une fonction d’identification des interlocuteurs pour les utilisateurs de la capacité vocale, elles doivent fournir un moyen d’identification des interlocuteurs pour les utilisateurs de signes en temps réel et de langage des signes dès qu’il est indiqué que des signes sont utilisés.

REMARQUE 1 : L’ID des interlocuteurs peut se trouver au même emplacement que celui des utilisateurs de capacité vocale dans le cas des appels avec plusieurs interlocuteurs.

REMARQUE 2 : Ce mécanisme peut être déclenché manuellement par un utilisateur ou automatiquement lorsque cela est techniquement réalisable.

Nouvelle exigence

6.5.6 Identification des interlocuteurs avec communication vidéo (langue des signes)

Lorsque les TIC prévoient une fonction d’identification des interlocuteurs pour les utilisateurs de la capacité vocale, elles doivent fournir un moyen d’identification des interlocuteurs pour les utilisateurs de signes en temps réel et de langage des signes dès qu’il est indiqué que des signes sont utilisés.

REMARQUE 1 : L’ID des interlocuteurs peut se trouver au même emplacement que celui des utilisateurs de capacité vocale dans le cas des appels avec plusieurs interlocuteurs.

REMARQUE 2 : Ce mécanisme peut être déclenché manuellement par un utilisateur ou automatiquement lorsque cela est techniquement réalisable.

6.6 Autres solutions de services vidéo

Lorsque les TIC sont dotées de la communication vidéo en temps réel ainsi que d’un répondeur, d’un standard automatique ou de moyens de réponse interactifs, elles doivent permettre aux utilisateurs d’accéder aux renseignements et d’exécuter les tâches liées à ces moyens :

  1. pour des renseignements audibles, sans recourir à l’ouïe;
  2. pour les commandes vocales, sans recourir à la parole;
  3. pour les renseignements visuels, sans recourir à la vision.

REMARQUE : Les solutions pouvant produire des sous-titres en temps réel ou traiter du texte en temps réel pourraient répondre au besoin susmentionné.

6.6 Autres solutions de services vidéo

Lorsque les TIC sont dotées de la communication vidéo en temps réel ainsi que d’un répondeur, d’un standard automatique ou de moyens de réponse interactifs, elles doivent permettre aux utilisateurs d’accéder aux renseignements et d’exécuter les tâches liées à ces moyens :

  1. pour des renseignements audibles, sans recourir à l’ouïe;
  2. pour les commandes vocales, sans recourir à la parole;
  3. pour les renseignements visuels, sans recourir à la vision.

REMARQUE : Les solutions pouvant produire des sous-titres en temps réel ou traiter du texte en temps réel pourraient répondre au besoin susmentionné.

6.6 Autres solutions de services vidéo

Lorsque les TIC sont dotées de la communication vidéo en temps réel ainsi que d’un répondeur, d’un standard automatique ou de moyens de réponse interactifs, elles doivent permettre aux utilisateurs d’accéder aux renseignements et d’exécuter les tâches liées à ces moyens :

  1. pour des renseignements audibles, sans recourir à l’ouïe;
  2. pour les commandes vocales, sans recourir à la parole;
  3. pour les renseignements visuels, sans recourir à la vision.

REMARQUE : Les solutions pouvant produire des sous-titres en temps réel ou traiter du TTR pourraient répondre au besoin susmentionné.

Reformulation stylistique

6.6 Autres solutions de services vidéo

Lorsque les TIC sont dotées de la communication vidéo en temps réel ainsi que d’un répondeur, d’un standard automatique ou de moyens de réponse interactifs, elles doivent permettre aux utilisateurs d’accéder aux renseignements et d’exécuter les tâches liées à ces moyens :

  1. pour des renseignements audibles, sans recourir à l’ouïe;
  2. pour les commandes vocales, sans recourir à la parole;
  3. pour les renseignements visuels, sans recourir à la vision.

REMARQUE : Les solutions pouvant produire des sous-titres en temps réel ou traiter du TTR pourraient répondre au besoin susmentionné.

7.1.2 Synchronisation des sous-titres

Lorsque les TIC affichent des sous-titres, le mécanisme d’affichage des sous-titres doit préserver la synchronisation entre le son et les sous-titres correspondants.

7.1.2 Synchronisation des sous-titres

Lorsque les TIC affichent des sous-titres, le mécanisme d’affichage des sous-titres doit préserver la synchronisation entre le son et les sous-titres correspondants.

7.1.2 Synchronisation des sous-titres

Lorsque les TIC affichent des sous-titres, le mécanisme d’affichage des sous-titres doit préserver la synchronisation entre le son et les sous-titres correspondants comme suit :

  • Sous-titres dans le matériel enregistré : dans les 100 ms de l’horodatage du sous-titre.
  • Sous-titres en direct : dans les 100 ms suivant la disponibilité du sous-titre pour le lecteur.
Changement fonctionnel

7.1.2 Synchronisation des sous-titres

Lorsque les TIC affichent des sous-titres, le mécanisme d’affichage des sous-titres doit préserver la synchronisation entre le son et les sous-titres correspondants comme suit :

  • Sous-titres dans le matériel enregistré : dans les 100 ms de l’horodatage du sous-titre.
  • Sous-titres en direct : dans les 100 ms suivant la disponibilité du sous-titre pour le lecteur.

7.1.4 Caractéristiques des sous-titres

Lorsque les TIC affichent des sous-titres, elles doivent permettre à l’utilisateur d’adapter les caractéristiques affichées des sous-titres à ses besoins individuels, sauf lorsque les sous-titres sont affichés sous forme de caractères non modifiables.

REMARQUE 1 : La définition de la couleur d’arrière-plan et d’avant-plan des sous-titres, du type de police, de l’opacité de la zone d’arrière-plan des sous-titres et du contour ou de la bordure des polices peut contribuer à répondre à cette exigence.

REMARQUE 2 : Les sous-titres qui sont des images bitmap sont des exemples de caractères non modifiables.

Nouvelle exigence

7.1.4 Caractéristiques des sous-titres

Lorsque les TIC affichent des sous-titres, elles doivent permettre à l’utilisateur d’adapter les caractéristiques affichées des sous-titres à ses besoins individuels, sauf lorsque les sous-titres sont affichés sous forme de caractères non modifiables.

REMARQUE 1 : La définition de la couleur d’arrière-plan et d’avant-plan des sous-titres, du type de police, de l’opacité de la zone d’arrière-plan des sous-titres et du contour ou de la bordure des polices peut contribuer à répondre à cette exigence.

REMARQUE 2 : Les sous-titres qui sont des images bitmap sont des exemples de caractères non modifiables.

7.1.5 Sous-titres vocaux

Lorsque les TIC affichent des vidéos avec son synchronisé, elles doivent fournir un mode de fonctionnement qui fournit une sortie vocale pour les sous-titres disponibles, sauf lorsque le contenu des sous-titres affichés ne peut être déterminé par programmation.

REMARQUE 1 : Il est préférable pour la plupart des utilisateurs de pouvoir gérer la gamme de sortie vocale pour les sous-titres vocaux indépendamment de la capacité vocale générale des TIC. Cela est possible lorsque le fichier audio avec sous-titres vocaux est reçu dans une piste audio distincte puis mixé sur l’appareil des utilisateurs finaux.

REMARQUE 2 : Présenter la piste audio distincte avec des sous-titres vocaux en synchronisme avec les sous-titres affichés améliore la compréhension des sous-titres.

REMARQUE 3 : Fournir les sous-titres sous forme de flux de texte distincts facilite la conversion des textes respectifs en audio.

REMARQUE 4 : Les sous-titres qui sont des images bitmap sont des exemples pour lesquels le contenu de sous-titres affichés ne peut pas être déterminé par programmation.

Nouvelle exigence

7.1.5 Sous-titres vocaux

Lorsque les TIC affichent des vidéos avec son synchronisé, elles doivent fournir un mode de fonctionnement qui fournit une sortie vocale pour les sous-titres disponibles, sauf lorsque le contenu des sous-titres affichés ne peut être déterminé par programmation.

REMARQUE 1 : Il est préférable pour la plupart des utilisateurs de pouvoir gérer la gamme de sortie vocale pour les sous-titres vocaux indépendamment de la capacité vocale générale des TIC. Cela est possible lorsque le fichier audio avec sous-titres vocaux est reçu dans une piste audio distincte puis mixé sur l’appareil des utilisateurs finaux.

REMARQUE 2 : Présenter la piste audio distincte avec des sous-titres vocaux en synchronisme avec les sous-titres affichés améliore la compréhension des sous-titres.

REMARQUE 3 : Fournir les sous-titres sous forme de flux de texte distincts facilite la conversion des textes respectifs en audio.

REMARQUE 4 : Les sous-titres qui sont des images bitmap sont des exemples pour lesquels le contenu de sous-titres affichés ne peut pas être déterminé par programmation.

7.2.1 Lecture de la description audio

Lorsque les TIC affichent des vidéos avec du son synchronisé, elles doivent fournir un mécanisme permettant de sélectionner et de lire la description audio disponible sur le canal audio par défaut.

Lorsque les technologies vidéo ne disposent pas de mécanismes explicites et distincts pour la description audio, une TIC est réputée satisfaire à cette exigence si elle permet à l'utilisateur de sélectionner et de lire plusieurs pistes audio.

REMARQUE 1 : Dans ce cas, le contenu vidéo peut inclure la description audio comme l’une des pistes audio disponibles.

REMARQUE 2 : Les descriptions audio dans les médias numériques comprennent parfois des informations permettant des descriptions plus longues que les intervalles entre les dialogues. La prise en charge de cette fonction de « description audio étendue » par les lecteurs de médias numériques est utile, en particulier pour les médias numériques qui sont visionnés personnellement.

7.2.1 Lecture de la description audio

Lorsque les TIC affichent des vidéos avec du son synchronisé, elles doivent fournir un mécanisme permettant de sélectionner et de lire la description audio disponible sur le canal audio par défaut.

Lorsque les technologies vidéo ne disposent pas de mécanismes explicites et distincts pour la description audio, une TIC est réputée satisfaire à cette exigence si elle permet à l'utilisateur de sélectionner et de lire plusieurs pistes audio.

REMARQUE 1 : Dans ce cas, le contenu vidéo peut inclure la description audio comme l’une des pistes audio disponibles.

REMARQUE 2 : Les descriptions audio dans les médias numériques comprennent parfois des informations permettant des descriptions plus longues que les intervalles entre les dialogues. La prise en charge de cette fonction de « description audio étendue » par les lecteurs de médias numériques est utile, en particulier pour les médias numériques qui sont visionnés personnellement.

7.2.1 Lecture de la description audio

Lorsque les TIC affichent des vidéos avec du son synchronisé, elles doivent fournir un mécanisme permettant de sélectionner et de lire la description audio disponible sur le canal audio par défaut.

Lorsque les technologies vidéo ne disposent pas de mécanismes explicites et distincts pour la description audio, une TIC est réputée satisfaire à cette exigence si elle permet à l'utilisateur de sélectionner et de lire plusieurs pistes audio.

REMARQUE 1 : Dans ce cas, le contenu vidéo peut inclure la description audio comme l’une des pistes audio disponibles.

REMARQUE 2 : Les descriptions audio dans les médias numériques comprennent parfois des informations permettant des descriptions plus longues que les intervalles entre les dialogues. La prise en charge de cette fonction de « description audio étendue » par les lecteurs de médias numériques est utile, en particulier pour les médias numériques qui sont visionnés personnellement.

7.2.1 Lecture de la description audio

Lorsque les TIC affichent des vidéos avec du son synchronisé, elles doivent fournir un mécanisme permettant de sélectionner et de lire la description audio disponible sur le canal audio par défaut.

Lorsque les technologies vidéo ne disposent pas de mécanismes explicites et distincts pour la description audio, une TIC est réputée satisfaire à cette exigence si elle permet à l'utilisateur de sélectionner et de lire plusieurs pistes audio.

REMARQUE 1 : Dans ce cas, le contenu vidéo peut inclure la description audio comme l’une des pistes audio disponibles.

REMARQUE 2 : Les descriptions audio dans les médias numériques comprennent parfois des informations permettant des descriptions plus longues que les intervalles entre les dialogues. La prise en charge de cette fonction de « description audio étendue » par les lecteurs de médias numériques est utile, en particulier pour les médias numériques qui sont visionnés personnellement.

7.2.2 Synchronisation de la description audio

Lorsque les TIC prévoient un mécanisme de lecture de la description audio, celui-ci doit préserver la synchronisation entre le contenu audio/visuel et la description audio correspondante.

7.2.2 Synchronisation de la description audio

Lorsque les TIC prévoient un mécanisme de lecture de la description audio, celui-ci doit préserver la synchronisation entre le contenu audio/visuel et la description audio correspondante.

7.2.2 Synchronisation de la description audio

Lorsque les TIC prévoient un mécanisme de lecture de la description audio, celui-ci doit préserver la synchronisation entre le contenu audio/visuel et la description audio correspondante.

7.2.2 Synchronisation de la description audio

Lorsque les TIC prévoient un mécanisme de lecture de la description audio, celui-ci doit préserver la synchronisation entre le contenu audio/visuel et la description audio correspondante.

8.3.0 Généralités

Le présent document définit les dimensions pour accéder aux TIC fixes qui peuvent être placées dans un environnement bâti, mais ne définit pas les normes de l’environnement bâti en général.

Le champ d’application inclut les TIC fixes, dont les planchers et les espaces de circulation font « partie intégrante » (généralement les kiosques et les cabines), et où il existe des plages de portée externe qui sont importantes pour le fonctionnement des TIC fixes.

Les clauses 8.3.2 à 8.3.4 précisent les limites obligatoires pour la hauteur maximale et minimale des pièces manœuvrables et des écrans.

Selon les dimensions indiquées à la figure 53 de la norme ISO 21542:2011, il est recommandé que la portée possible en hauteur soit ramenée :

  • aux hauteurs minimale et maximale des pièces manœuvrables : 800 mm et 1 100 mm respectivement, et
  • aux hauteurs minimale et maximale des écrans : 1 200 mm et 1 400 mm respectivement.
Nouvelle exigence

8.3.0 Généralités

Le présent document définit les dimensions pour accéder aux TIC fixes qui peuvent être placées dans un environnement bâti, mais ne définit pas les normes de l’environnement bâti en général.

Le champ d’application inclut les TIC fixes, dont les planchers et les espaces de circulation font « partie intégrante » (généralement les kiosques et les cabines), et où il existe des plages de portée externe qui sont importantes pour le fonctionnement des TIC fixes.

Les clauses 8.3.2 à 8.3.4 précisent les limites obligatoires pour la hauteur maximale et minimale des pièces manœuvrables et des écrans.

Selon les dimensions indiquées à la figure 53 de la norme ISO 21542:2011, il est recommandé que la portée possible en hauteur soit ramenée :

  • aux hauteurs minimale et maximale des pièces manœuvrables : 800 mm et 1 100 mm respectivement, et
  • aux hauteurs minimale et maximale des écrans : 1 200 mm et 1 400 mm respectivement.

8.3.2.1 Changement de niveau

Lorsqu’un dénivelé de plancher fait partie intégrante des TIC, une rampe présentant une pente d’au plus 1 : 48 doit être aménagée.

Exceptions

  1. Si le dénivelé est inférieur ou égal à 6,4 mm (¼ po), le dénivelé peut être vertical.
  2. Si le dénivelé est inférieur ou égal à 13 mm (½ po), le dénivelé peut présenter une pente d’au plus 1 : 2.

8.3.2.1 Changement de niveau

Lorsqu’un dénivelé de plancher fait partie intégrante des TIC, une rampe présentant une pente d’au plus 1 : 48 doit être aménagée.

Exceptions

  1. Si le dénivelé est inférieur ou égal à 6,4 mm (¼ po), le dénivelé peut être vertical.
  2. Si le dénivelé est inférieur ou égal à 13 mm (½ po), le dénivelé peut présenter une pente d’au plus 1 : 2.

8.3.4.1 Changement de niveau

Lorsque des TIC fixes comportent un plancher, tout dénivelé de plancher qui y est intégré doit être aménagé d’une rampe présentant une pente d’au plus 1 : 48.

Exceptions

  1. Si le dénivelé est inférieur ou égal à 6,4 mm (¼ po), le dénivelé peut être vertical.
  2. Si le dénivelé est inférieur ou égal à 13 mm (½ po), le dénivelé peut présenter une pente d’au plus 1 : 2.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.1 Changement de niveau

Lorsque des TIC fixes comportent un plancher, tout dénivelé de plancher qui y est intégré doit être aménagé d’une rampe présentant une pente d’au plus 1 : 48.

Exceptions

  1. Si le dénivelé est inférieur ou égal à 6,4 mm (¼ po), le dénivelé peut être vertical comme il est illustré à la figure 8.
  2. Si le dénivelé est inférieur ou égal à 13 mm (½ po), le dénivelé peut présenter une pente d’au plus 1 : 2.

8.3.2.3.1 Généralités

Lorsque l’espace d’accès fait partie intégrante des TIC, au moins un côté complet de l’espace doit être dégagé.

8.3.2.3.1 Généralités

Lorsque l’espace d’accès fait partie intégrante des TIC, au moins un côté complet de l’espace doit être dégagé.

8.3.4.3.1 Généralités

Lorsque des TIC fixes comportent un espace d’accès, au moins un côté complet de l’espace doit être dégagé.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.3.1 Généralités

Lorsque des TIC fixes comportent un espace d’accès, au moins un côté complet de l’espace doit être dégagé.

8.3.2.3.2 Approche avant

Lorsque l’espace opérationnel se trouve dans une alcôve faisant partie intégrante des TIC, la profondeur de l’alcôve est supérieure à 610 mm (24 po), et lorsqu’une approche avant est nécessaire, l’espace d’accès doit être d’au moins 915 mm (36 po) de largeur.

8.3.2.3.2 Approche avant

Lorsque l’espace opérationnel se trouve dans une alcôve faisant partie intégrante des TIC, la profondeur de l’alcôve est supérieure à 610 mm (24 po), et lorsqu’une approche avant est nécessaire, l’espace d’accès doit être d’au moins 915 mm (36 po) de largeur.

8.3.4.3.2 Approche avant

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 610 mm (24 po), et lorsqu’une approche avant est nécessaire, l’espace d’accès doit être d’au moins 915 mm (36 po) de largeur.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.3.2 Approche avant

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 610 mm (24 po), et lorsqu’une approche avant est nécessaire, l’espace d’accès doit être d’au moins 915 mm (36 po) de largeur.

8.3.2.3.3 Approche parallèle

Lorsque l’espace opérationnel se trouve dans une alcôve faisant partie intégrante des TIC, la profondeur de l’alcôve est supérieure à 380 mm (15 po), et lorsqu’une approche parallèle est nécessaire, l’espace d’accès devrait être d’au moins 1 525 mm (60 po) de largeur.

8.3.2.3.3 Approche parallèle

Lorsque l’espace opérationnel se trouve dans une alcôve faisant partie intégrante des TIC, la profondeur de l’alcôve est supérieure à 380 mm (15 po), et lorsqu’une approche parallèle est nécessaire, l’espace d’accès devrait être d’au moins 1 525 mm (60 po) de largeur.

8.3.4.3.3 Approche parallèle

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 380 mm (15 po), et lorsqu’une approche parallèle est nécessaire, l’espace d’accès doit être d’au moins 1 525 mm (60 po) de largeur.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.3.3 Approche parallèle

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 380 mm (15 po), et lorsqu’une approche parallèle est nécessaire, l’espace d’accès doit être d’au moins 1 525 mm (60 po) de largeur.

8.3.5 Instructions d’installation

Lorsque les TIC doivent être installées, des instructions doivent présenter une méthode d’installation des TIC de manière à garantir que les dimensions des espaces faisant partie intégrante des TIC sont conformes aux clauses 8.3.2 à 8.3.4.

8.3.5 Instructions d’installation

Lorsque les TIC doivent être installées, des instructions doivent présenter une méthode d’installation des TIC de manière à garantir que les dimensions des espaces faisant partie intégrante des TIC sont conformes aux clauses 8.3.2 à 8.3.4.

8.3.6 Instructions d’installation

Les instructions d’installation doivent être accessibles pour toutes les TIC fixes. Ces instructions doivent donner des directives sur la façon d’installer les TIC d’une manière qui tient compte des exigences applicables en matière d’accessibilité de l’environnement bâti lorsqu’elles s’appliquent à l’installation des TIC. Lorsque de telles exigences n’existent pas, les instructions devraient exiger que les dimensions des TIC installées soient conformes aux clauses 8.3.2 à 8.3.5 du présent document.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.6 Instructions d’installation

Les instructions d’installation doivent être accessibles pour toutes les TIC fixes. Ces instructions doivent donner des directives sur la façon d’installer les TIC d’une manière qui tient compte des exigences applicables en matière d’accessibilité de l’environnement bâti lorsqu’elles s’appliquent à l’installation des TIC. Lorsque de telles exigences n’existent pas, les instructions devraient exiger que les dimensions des TIC installées soient conformes aux clauses 8.3.2 à 8.3.5 du présent document.

9.1.3.4 Orientation

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.4 Orientation des WCAG 2.1.

Nouvelle exigence

9.1.3.4 Orientation

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.4 Orientation des WCAG 2.1.

9.1.3.4 Orientation

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.4 Orientation des WCAG 2.1.

9.1.3.5 Identifier la finalité de la saisie

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Nouvelle exigence

9.1.3.5 Identifier la finalité de la saisie

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

9.1.3.5 Identifier la finalité de la saisie

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

9.1.4.10 Redistribution

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.10 Redistribution des WCAG 2.1.

Nouvelle exigence

9.1.4.10 Redistribution

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.10 Redistribution des WCAG 2.1.

9.1.4.10 Redistribution

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.10 Redistribution des WCAG 2.1.

9.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Nouvelle exigence

9.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

9.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

9.1.4.12 Espacement du texte

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Nouvelle exigence

9.1.4.12 Espacement du texte

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

9.1.4.12 Espacement du texte

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

9.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est une page Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Nouvelle exigence

9.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est une page Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

9.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est une page Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

9.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

Nouvelle exigence

9.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

9.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

9.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.1 Gestes pour le contrôle du pointeur.

Nouvelle exigence

9.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.1 Gestes pour le contrôle du pointeur.

9.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.1 Gestes pour le contrôle du pointeur.

9.2.5.2 Annulation de l’action du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.2 Annulation de l’action du pointeur.

Nouvelle exigence

9.2.5.2 Annulation de l’action du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.2 Annulation de l’action du pointeur.

9.2.5.2 Annulation de l’action du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.2 Annulation de l’action du pointeur.

9.2.5.3 Étiquette dans le nom

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom de WCAG 2.1.

Nouvelle exigence

9.2.5.3 Étiquette dans le nom

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom de WCAG 2.1.

9.2.5.3 Étiquette dans le nom

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom de WCAG 2.1.

9.2.5.4 Activation par le mouvement

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement.

Nouvelle exigence

9.2.5.4 Activation par le mouvement

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement.

9.2.5.4 Activation par le mouvement

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement.

9.4.1.3 Messages d’état

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

Nouvelle exigence

9.4.1.3 Messages d’état

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

9.4.1.3 Messages d’état

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

9.5 Critères de succès de niveau AAA des WCAG 2.1

Outre les critères de succès de niveau AA, les Règles pour l’accessibilité des contenus Web comprennent les critères de succès pour le niveau AAA, aux clauses 9.1 à 9.4. Ces critères sont énumérés dans le tableau 9.1. Les auteurs de sites Web et les spécialistes de l’approvisionnement en matière d’accessibilité sont invités à tenir compte des critères de succès de niveau AAA des WCAG 2.1 qui, lorsqu’il est possible de les appliquer, peuvent fournir un accès au-delà de ce qui est requis dans le présent document.

REMARQUE : Le W3C stipule qu’« il n’est pas recommandé de se fixer le niveau AAA comme objectif à l’échelle de sites entiers car il n’est pas possible de satisfaire à tous les critères de succès du niveau AAA pour certains contenus ».

Nouvelle exigence

9.5 Critères de succès de niveau AAA des WCAG 2.1

Outre les critères de succès de niveau AA, les Règles pour l’accessibilité des contenus Web comprennent les critères de succès pour le niveau AAA, aux clauses 9.1 à 9.4. Ces critères sont énumérés dans le tableau 9.1. Les auteurs de sites Web et les spécialistes de l’approvisionnement en matière d’accessibilité sont invités à tenir compte des critères de succès de niveau AAA des WCAG 2.1 qui, lorsqu’il est possible de les appliquer, peuvent fournir un accès au-delà de ce qui est requis dans le présent document.

REMARQUE : Le W3C stipule qu’« il n’est pas recommandé de se fixer le niveau AAA comme objectif à l’échelle de sites entiers car il n’est pas possible de satisfaire à tous les critères de succès du niveau AAA pour certains contenus ».

10.2.7 Information et relations

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès. L’information, la structure et les relations véhiculées dans la présentation peuvent être déterminées à l’aide d’un programme informatique ou être disponibles sous forme de texte.

Remarque :Ce critère de succès est identique au critère de succès 1.3.1 Information et relations des WCAG 2.0.

10.1.3.1 Information et relations

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

Changement de numérotation

10.1.3.1 Information et relations

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE : Lorsque les documents contiennent des types de structure non standard (rôles), il est préférable de les faire correspondre à un type de structure standard comme solution de secours pour le lecteur.

Mise à jour explicative

10.1.3.1 Information et relations

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE : Lorsque les documents contiennent des types de structure non standard (rôles), il est préférable de les faire correspondre à un type de structure standard comme solution de secours pour le lecteur.

10.1.3.4 Orientation

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

Nouvelle exigence

10.1.3.4 Orientation

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

10.1.3.4 Orientation

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

10.1.3.5 Identifier la finalité de la saisie

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Nouvelle exigence

10.1.3.5 Identifier la finalité de la saisie

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

10.1.3.5 Identifier la finalité de la saisie

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

10.1.4.10 Redistribution

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

Nouvelle exigence

10.1.4.10 Redistribution

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

10.1.4.10 Redistribution

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

10.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Nouvelle exigence

10.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

10.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

10.1.4.12 Espacement du texte

Dans le cas où la TIC est un document non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Nouvelle exigence

10.1.4.12 Espacement du texte

Dans le cas où la TIC est un document non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

10.1.4.12 Espacement du texte

Dans le cas où la TIC est un document non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

10.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Nouvelle exigence

10.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

10.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

10.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC ne sont pas un document Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

Nouvelle exigence

10.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC ne sont pas un document Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

10.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC ne sont pas un document Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

10.2.20 Clause vide

Cette clause ne contient aucune exigence. Elle est incluse afin d’aligner la numérotation des sous-clauses connexes dans les clauses 9.2, 10.2 et 11.2.

10.2.4.1 VideChangement de numérotation

10.2.4.1 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Contourner des blocs » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents » qui sont rares.

REMARQUE 2 : Bien qu’il ne s’agisse pas d’une exigence, la possibilité de contourner des blocs de contenu qui sont répétés dans les documents est généralement considérée comme une pratique exemplaire et répond aux besoins des utilisateurs.

Mise à jour explicative

10.2.4.1 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Contourner des blocs » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents » qui sont rares.

REMARQUE 2 : Bien qu’il ne s’agisse pas d’une exigence, la possibilité de contourner des blocs de contenu qui sont répétés dans les documents est généralement considérée comme une pratique exemplaire et répond aux besoins des utilisateurs.

10.2.20 Clause vide

Cette clause ne contient aucune exigence. Elle est incluse afin d’aligner la numérotation des sous-clauses connexes dans les clauses 9.2, 10.2 et 11.2.

10.2.4.5 VideChangement de numérotation

10.2.4.5 Vide

REMARQUE : L’exigence de la page Web connexe «Accès multiples » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents »qui sont rares.

Mise à jour explicative

10.2.4.5 Vide

REMARQUE : L’exigence de la page Web connexe «Accès multiples » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents »qui sont rares.

10.2.5.1 Gestes pour le contrôle du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Toutes les fonctionnalités qui utilisent des gestes multipoints ou basés sur un tracé peuvent être utilisées avec un pointage à contact unique sans geste basé sur un tracé, à moins qu’un geste multipoint ou basé sur un tracé ne soit essentiel.

REMARQUE 1 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

Nouvelle exigence

10.2.5.1 Gestes pour le contrôle du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Toutes les fonctionnalités qui utilisent des gestes multipoints ou basés sur un tracé peuvent être utilisées avec un pointage à contact unique sans geste basé sur un tracé, à moins qu’un geste multipoint ou basé sur un tracé ne soit essentiel.

REMARQUE 1 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

10.2.5.1 Gestes pour le contrôle du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Toutes les fonctionnalités qui utilisent des gestes multipoints ou basés sur un tracé peuvent être utilisées avec un pointage à contact unique sans geste basé sur un tracé, à moins qu’un geste multipoint ou basé sur un tracé ne soit essentiel.

REMARQUE 1 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

10.2.5.2 Annulation de l’action du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

Nouvelle exigence

10.2.5.2 Annulation de l’action du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

10.2.5.2 Annulation de l’action du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

10.2.5.3 Étiquette dans le nom

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Nouvelle exigence

10.2.5.3 Étiquette dans le nom

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

10.2.5.3 Étiquette dans le nom

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

10.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

Nouvelle exigence

10.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

10.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

10.2.32 Clause vide

Cette clause ne contient aucune exigence. Elle est incluse afin d’aligner la numérotation des sous-clauses connexes dans les clauses 9.2, 10.2 et 11.2.

10.3.2.3 VideChangement de numérotation

10.3.2.3 Vide

REMARQUE : L’exigence de la page Web connexe « Navigation cohérente » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents » qui sont rares.

Mise à jour explicative

10.3.2.3 Vide

REMARQUE : L’exigence de la page Web connexe « Navigation cohérente » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents » qui sont rares.

10.4.1.3 Vide

10.4.1.3 Messages d’état

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

Nouvelle exigence

10.4.1.3 Messages d’état

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

10.2.39 Positionnement des sous-titres

Lorsque la TIC est un document non Web qui contient des médias synchronisés avec des sous-titres, les sous-titres ne devraient pas cacher les renseignements pertinents dans les médias synchronisés.

10.5 Positionnement des sous-titres

Lorsque la TIC est un document non Web qui contient des médias synchronisés avec des sous-titres, les sous-titres ne devraient pas cacher les renseignements pertinents dans les médias synchronisés.

Changement de numérotation

10.5 Positionnement des sous-titres

Lorsque la TIC est un document non Web qui contient des médias synchronisés avec des sous-titres, les sous-titres ne devraient pas cacher les renseignements pertinents dans les médias synchronisés.

10.5 Positionnement des sous-titres

Lorsque la TIC est un document non Web qui contient des médias synchronisés avec des sous-titres, les sous-titres ne devraient pas cacher les renseignements pertinents dans les médias synchronisés.

11.1.2.1.2.1 Préenregistrement audio uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran et lorsque des renseignements auditifs préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes de la TIC, la fonctionnalité du logiciel qui fournit une interface utilisateur doit satisfaire à l'exigence 5.1.5 (sortie visuelle pour renseignements audio).

Nouvelle exigence

11.1.2.1.2.1 Préenregistrement audio uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran et lorsque des renseignements auditifs préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes de la TIC, la fonctionnalité du logiciel qui fournit une interface utilisateur doit satisfaire à l'exigence 5.1.5 (sortie visuelle pour renseignements audio).

11.1.2.1.2.1 Préenregistrement audio uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran et lorsque des renseignements auditifs préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes de la TIC, la fonctionnalité du logiciel qui fournit une interface utilisateur doit satisfaire à l'exigence 5.1.5 (sortie visuelle pour renseignements audio).

11.1.2.1.2.2 Préenregistrement vidéo uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l'exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

Nouvelle exigence

11.1.2.1.2.2 Préenregistrement vidéo uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l'exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

11.1.2.1.2.2 Préenregistrement vidéo uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l'exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

11.2.1.6 Description audio (préenregistrée)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur, elle doit satisfaire au critère de succès 1.2.5 Description audio (préenregistrée) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin. REMARQUE 3 : Ce critère de succès est identique au critère 1.2.5 Description audio (Pré-enregistrée) des WCAG 2.0, avec l’ajout de la remarque 1 ci-dessus.

11.1.2.5 Description audio (préenregistrée)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur, elle doit satisfaire au critère de succès 1.2.5 Description audio (préenregistrée) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

Changement de numérotation

11.1.2.5 Description audio (préenregistrée)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur, elle doit satisfaire au critère de succès 1.2.5 Description audio (préenregistrée) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

11.1.2.5 Description audio (préenregistrée)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur, elle doit satisfaire au critère de succès 1.2.5 Description audio (préenregistrée) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

11.1.2.3.1 Audio-description ou version de remplacement pour un média temporel (préenregistré – fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

Nouvelle exigence

11.1.2.3.1 Audio-description ou version de remplacement pour un média temporel (préenregistré – fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

11.1.2.3.1 Audio-description ou version de remplacement pour un média temporel (préenregistré – fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

11.1.2.3.2 Audio-description ou version de remplacement pour un média temporel (pré-enregistré – fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

Nouvelle exigence

11.1.2.3.2 Audio-description ou version de remplacement pour un média temporel (pré-enregistré – fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

11.1.2.3.2 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) – fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

11.2.1.7 Information et relations

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès. L’information, la structure et les relations véhiculées dans la présentation peuvent être déterminées avec un programme informatique ou être disponibles en texte.

REMARQUE 1 : Dans les logiciels, la déterminabilité par un programme informatique est le mieux réalisée par l'utilisation des services d'accessibilité fournis par les logiciels de plateforme pour permettre l'interopérabilité entre les logiciels et les technologies d'assistance et les fonctions d'accessibilité des logiciels (voir la clause 11.3 Interopérabilité avec les technologies d'assistance). REMARQUE 2 : Ce critère de succès est identique au critère 1.3.1 Information et relations des WCAG 2.0, avec l’ajout de la remarque 1 ci-dessus.

11.1.3.1.1 Information et relations (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE : Dans les logiciels, la déterminabilité par un programme informatique est le mieux réalisée par l'utilisation des services d'accessibilité fournis par les logiciels de plateforme pour permettre l'interopérabilité entre les logiciels et les technologies d'assistance et les fonctions d'accessibilité des logiciels (voir la clause 11.5 Interopérabilité avec les technologies d'assistance).

Changement de numérotation

Mise à jour explicative

11.1.3.1.1 Information et relations (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE : Dans les logiciels, la déterminabilité par un programme informatique est le mieux réalisée par l'utilisation des services d'accessibilité fournis par les logiciels de plateforme pour permettre l'interopérabilité entre les logiciels et les technologies d'assistance et les fonctions d'accessibilité des logiciels (voir la clause 11.5 Interopérabilité avec les technologies d'assistance).

11.1.3.1.1 Information et relations (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE : Dans les logiciels, la déterminabilité par un programme informatique est le mieux réalisée par l'utilisation des services d'accessibilité fournis par les logiciels de plateforme pour permettre l'interopérabilité entre les logiciels et les technologies d'assistance et les fonctions d'accessibilité des logiciels (voir la clause 11.5 Interopérabilité avec les technologies d'assistance).

11.1.3.1.2 Information et relations (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

Nouvelle exigence

11.1.3.1.2 Information et relations (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

11.1.3.1.2 Information et relations (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

11.2.1.8 Ordre séquentiel logique

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès. Lorsque la séquence dans laquelle le contenu est présenté affecte sa signification, une bonne séquence de lecture peut être déterminée par un programme informatique.

REMARQUE : Ce critère de succès est identique au critère 1.3.2 Ordre séquentiel logique des WCAG 2.0.

11.1.3.2.1 Ordre séquentiel logique (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

Changement de numérotation

11.1.3.2.1 Ordre séquentiel logique (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

11.1.3.2.1 Ordre séquentiel logique (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

11.1.3.2.2 Ordre séquentiel logique (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

Nouvelle exigence

11.1.3.2.2 Ordre séquentiel logique (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

11.1.3.2.2 Ordre séquentiel logique (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

11.1.3.4 Orientation

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

Nouvelle exigence

11.1.3.4 Orientation

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

11.1.3.4 Orientation

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

11.1.3.5 Identifier la finalité de la saisie

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Nouvelle exigence

11.1.3.5.1 Identifier la finalité de la saisie (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit remplir le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Changement de numérotation

Changement fonctionnel

11.1.3.5.1 Identifier la finalité de la saisie (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit remplir le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

11.1.3.5.2 Identifier la finalité de la saisie (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui est restreint aux technologies d’assistance, elle doit prévoir au moins un mode de fonctionnement selon lequel l’utilisateur est présenté, sous forme audio, l’objectif de chaque champ de saisie recueillant des renseignements sur l’utilisateur, lorsque ce champ sert un objectif défini à la section Identifier la finalité de la saisie pour les composants d’interface utilisateur des WCAG 2.1.

Nouvelle exigence

11.1.3.5.2 Identifier la finalité de la saisie (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui est restreint aux technologies d’assistance, elle doit prévoir au moins un mode de fonctionnement selon lequel l’utilisateur est présenté, sous forme audio, l’objectif de chaque champ de saisie recueillant des renseignements sur l’utilisateur, lorsque ce champ sert à un objectif définie à la section Identifier la finalité de la saisie pour les composants d’interface utilisateur des WCAG 2.1.

11.2.1.13 Redimensionnement du texte

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux fonctions d’agrandissement d’une plateforme ou d’une technologie d’assistance, elle doit satisfaire au critère de succès. À l’exception des légendes et des images de texte, le texte peut être redimensionné sans technologie d’assistance jusqu’à 200 % sans perte de contenu ou de fonctionnalité.

REMARQUE 1 : Le contenu pour lequel il existe des logiciels de lecture, de visualisation ou d’édition dotés d'une fonction de zoom de 200 % répondrait automatiquement à ce critère de succès lorsqu'il est utilisé avec ces logiciels, sauf si le contenu ne fonctionne pas avec le zoom.

REMARQUE 2 : technologies. Ce critère de succès a trait à la capacité de permettre aux utilisateurs d’agrandir le texte à l’écran au moins jusqu’à 200 % sans avoir besoin d'utiliser des technologies d’assistance. Cela signifie que l’application fournit un moyen d’agrandir le texte de 200 % (zoom ou autre) sans perte de contenu ou de fonctionnalité ou que l’application fonctionne avec les fonctionnalités de la plate-forme qui répondent à cette exigence.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.4 Redimensionner le texte des WCAG 2.0 avec l’ajout des remarques 1 et 2 ci-dessus.

11.1.4.4.2 Redimensionnement du texte (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui n’est pas en mesure d’accéder aux fonctions d’agrandissement d’une plateforme ou d’une technologie d’assistance, elle doit satisfaire à l’exigence 5.1.4 (Fonction restreinte à l’agrandissement du texte).

REMARQUE : Étant donné que la prise en charge du rendu de texte dans un environnement restreint peut être plus limitée que celle que l’on trouve dans les agents utilisateurs pour le Web, le respect de la clause 11.1.4.4.2 dans un environnement restreint peut imposer un fardeau beaucoup plus lourd à l’auteur du contenu.

Changement de numérotation
Changement fonctionnel

11.1.4.4.2 Redimensionnement du texte (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui n’est pas en mesure d’accéder aux fonctions d’agrandissement d’une plateforme ou d’une technologie d’assistance, elle doit satisfaire à l’exigence 5.1.4 (Fonction restreinte à l’agrandissement du texte).

REMARQUE : Étant donné que la prise en charge du rendu de texte dans un environnement restreint peut être plus limitée que celle que l’on trouve dans les agents utilisateurs pour le Web, le respect de la présente clause dans un environnement restreint peut imposer un fardeau beaucoup plus lourd à l’auteur du contenu.

11.1.4.4.2 Redimensionnement du texte (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui n’est pas en mesure d’accéder aux fonctions d’agrandissement d’une plateforme ou d’une technologie d’assistance, elle doit satisfaire à l’exigence 5.1.4 (Fonction restreinte à l’agrandissement du texte).

REMARQUE : Étant donné que la prise en charge du rendu de texte dans un environnement restreint peut être plus limitée que celle que l’on trouve dans les agents utilisateurs pour le Web, le respect de la présente clause dans un environnement restreint peut imposer un fardeau beaucoup plus lourd à l’auteur du contenu.

11.2.1.14 Texte sous forme d’image

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès.

Si les technologies utilisées peuvent réaliser la présentation visuelle, du texte est utilisé pour véhiculer l’information plutôt que du texte sous forme d’image sauf dans les cas suivants :

  • Personnalisable : le texte sous forme d’image peut être personnalisé visuellement selon les exigences de l’utilisateur ;
  • Essentielle : une présentation spécifique du texte est essentielle à l’information véhiculée.

REMARQUE 1 : Les logotypes sont considérés comme essentiels (le texte qui fait partie d’un logo ou d’un nom de marque).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 1.4.5 Images de texte des WCAG 2.0.

11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

Changement de numérotation

Changement fonctionnel

Mise à jour explicative

11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

11.1.4.5.2 Texte sous forme d’image (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle n’a pas besoin de satisfaire au critère de succès 1.4.5 Images de texte des WCAG 2.1 parce qu’il n’est pas nécessaire d’imposer à toutes les fonctionnalités fermées que le texte affiché à l'écran soit effectivement représenté en interne comme du texte (aux termes des WCAG 2.1), étant donné qu'il n'y a pas d’interopérabilité avec les technologies d’assistance.

Nouvelle exigence

11.1.4.5.2 Texte sous forme d’image (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.6 (sortie vocale pour les contenus non textuels).

Changement fonctionnel

11.1.4.5.2 Texte sous forme d’image (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.6 (sortie vocale pour les contenus non textuels).

11.1.4.10.1 Redistribution (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès suivant.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

Nouvelle exigence

11.1.4.10 Redistribution

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, il doit remplir le critère de succès suivant.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

Changement de numérotation

Changement fonctionnel

11.1.4.10 Redistribution

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, il doit remplir le critère de succès.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

11.1.4.10.2 Redistribution (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne pas prend en charge l’accès aux fonctions d’agrandissement de la plateforme ou à la technologie d’assistance, elle remplit l’exigence 5.1.4 (fonction restreinte à l’agrandissement du texte).

Nouvelle exigenceVideVide

11.1.4.11 Contraste du contenu non textuel

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Nouvelle exigence

11.1.4.11 Contraste du contenu non textuel

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

11.1.4.11 Contraste du contenu non textuel

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

11.1.4.12 Espacement du texte

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Nouvelle exigence

11.1.4.12 Espacement du texte

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

11.1.4.12 Espacement du texte

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

11.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Nouvelle exigence

11.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

11.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

11.2.1.1.2 Clavier (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

Nouvelle exigence

11.2.1.1.2 Clavier (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

11.2.1.1.2 Clavier (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

11.2.1.4.1 Raccourcis clavier utilisant des caractères (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

Nouvelle exigence

11.2.1.4.1 Raccourcis clavier utilisant des caractères (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

11.2.1.4.1 Raccourcis clavier utilisant des caractères (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

11.2.1.4.2 Raccourcis clavier utilisant des caractères (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

Nouvelle exigence

11.2.1.4.2 Raccourcis clavier utilisant des caractères (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

11.2.1.4.2 Raccourcis clavier utilisant des caractères (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

11.2.1.20 Clause vide

Cette clause ne contient aucune exigence. Elle est incluse afin d’aligner la numérotation des sous-clauses connexes dans les clauses 9.2, 10.2 et 11.2.

11.2.4.1 Vide

11.2.4.1 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Contourner des blocs » ne s’applique pas aux programmes logiciels uniques, mais à une définition précise d’ « ensembles de programmes logiciels » qui sont extrêmement rares.

REMARQUE 2 : Bien qu’il ne s’agisse pas d’une exigence, la possibilité de contourner des blocs de contenu qui sont répétés dans les logiciels est généralement considérée comme une pratique exemplaire et répond aux besoins des utilisateurs.

Reformulation stylistique

11.2.4.1 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Contourner des blocs » ne s’applique pas aux programmes logiciels uniques, mais à une définition précise d’ « ensembles de programmes logiciels » qui sont extrêmement rares.

REMARQUE 2 : Bien qu’il ne s’agisse pas d’une exigence, la possibilité de contourner des blocs de contenu qui sont répétés dans les logiciels est généralement considérée comme une pratique exemplaire et répond aux besoins des utilisateurs.

11.2.1.21 Clause vide

Cette clause ne contient aucune exigence. Elle est incluse afin d’aligner la numérotation des sous-clauses connexes dans les clauses 9.2, 10.2 et 11.2.

11.2.4.2 Vide

11.2.4.2 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Page intitulée » ne s’applique pas aux programmes logiciels uniques, mais à une définition précise d’« ensembles de programmes logiciels » qui sont extrêmement rares.

REMARQUE 2 : Bien que le nom d’un produit logiciel puisse constituer un titre suffisant s’il décrit le sujet ou l’objectif, les noms de logiciels sont des marques déposées et les noms de marques ne peuvent pas, selon la loi, être des noms descriptifs. Il n’est pas pratique de rendre les noms de logiciels à la fois uniques et descriptifs.

Reformulation stylistique

11.2.4.2 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Page intitulée » ne s’applique pas aux programmes logiciels uniques, mais à une définition précise d’« ensembles de programmes logiciels » qui sont extrêmement rares.

REMARQUE 2 : Bien que le nom d’un produit logiciel puisse constituer un titre suffisant s’il décrit le sujet ou l’objectif, les noms de logiciels sont des marques déposées et les noms de marques ne peuvent pas, selon la loi, être des noms descriptifs. Il n’est pas pratique de rendre les noms de logiciels à la fois uniques et descriptifs.

11.3.1.1.2 Langue du logiciel (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.14 (Langues parlées).

Nouvelle exigence

11.3.1.1.2 Langue du logiciel (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.14 (Langues parlées).

11.3.1.1.2 Langue du logiciel (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.14 (Langues parlées).

11.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès suivant.

Toutes les fonctions qui utilisent des mouvements multipoints ou basés sur un tracé pour exécuter une commande peuvent être utilisées avec un seul pointeur sans mouvement basé sur un tracé, à moins qu’un mouvement multipoint ou basé sur un tracé soit essentiel.

REMARQUE 1 : Cette exigence s’applique au logiciel non Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

Nouvelle exigence

11.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès suivant.

Toutes les fonctions qui utilisent des mouvements multipoints ou basés sur un tracé pour exécuter une commande peuvent être utilisées avec un seul pointeur sans mouvement basé sur un tracé, à moins qu’un mouvement multipoint ou basé sur un tracé soit essentiel.

REMARQUE 1 : Cette exigence s’applique au logiciel non Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

11.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès.

Toutes les fonctions qui utilisent des mouvements multipoints ou basés sur un tracé pour exécuter une commande peuvent être utilisées avec un seul pointeur sans mouvement basé sur un tracé, à moins qu’un mouvement multipoint ou basé sur un tracé soit essentiel.

REMARQUE 1 : Cette exigence s’applique au logiciel non Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1

Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

11.2.5.2 Annulation de l’action du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès suivant.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

Nouvelle exigence

11.2.5.2 Annulation de l’action du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès suivant.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

11.2.5.2 Annulation de l’action du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

11.2.5.3 Étiquette dans le nom

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Nouvelle exigence

11.2.5.3.1 Étiquette dans le nom (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Changement de numérotation

11.2.5.3.1 Étiquette dans le nom (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

11.2.5.3.2 Étiquette dans le nom (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.3 (Corrélation de sortie sonore).

Nouvelle exigence

11.2.5.3.2 Étiquette dans le nom (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.3 (Corrélation de sortie sonore).

11.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

Nouvelle exigence

11.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

11.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

11.4.1.3.1 Messages d’état (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web, elle doit satisfaire au critère de succès 4.1.3 Messages d’état des WCAG 2.1.

Nouvelle exigence

11.4.1.3.1 Messages d’état (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web, elle doit satisfaire au critère de succès 4.1.3 Messages d’état des WCAG 2.1.

11.4.1.3.2 Messages d’état (fonction restreinte)

Sans objet.

Nouvelle exigence

11.4.1.3.2 Messages d’état (fonction restreinte)

Sans objet.

13.1.1 Généralités (information)

Les services de relais permettent aux utilisateurs de différents modes de communication (texte, signes, parole, etc.) d’interagir à distance, grâce aux TIC et à la communication bidirectionnelle, en assurant une conversion entre les modes de communication, normalement effectuée par un opérateur humain.

Une pratique exemplaire consiste à respecter les exigences de la norme en vigueur ES 202 975 en matière de services de relais.

13.1.1 Généralités (information)

Les services de relais permettent aux utilisateurs de différents modes de communication (texte, signes, parole, etc.) d’interagir à distance, grâce aux TIC et à la communication bidirectionnelle, en assurant une conversion entre les modes de communication, normalement effectuée par un opérateur humain.

Une pratique exemplaire consiste à respecter les exigences de la norme en vigueur ES 202 975 de l’ETSI en matière de services de relais.

Mise à jour explicative

13.1.1 Généralités (information)

Les services de relais permettent aux utilisateurs de différents modes de communication (texte, signes, parole, etc.) d’interagir à distance, grâce aux TIC et à la communication bidirectionnelle, en assurant une conversion entre les modes de communication, normalement effectuée par un opérateur humain.

Une pratique exemplaire consiste à respecter les exigences de la norme en vigueur ES 202 975 de l’ETSI en matière de services de relais.

13.1.1 Généralités (information)

Les services de relais permettent aux utilisateurs de différents modes de communication (texte, signes, parole, etc.) d’interagir à distance, grâce aux TIC et à la communication bidirectionnelle, en assurant une conversion entre les modes de communication, normalement effectuée par un opérateur humain.

Une pratique exemplaire consiste à respecter les exigences de la norme en vigueur ES 202 975 [i.5] de l’ETSI en matière de services de relais.

13.1.6 Services de relais de la parole à la parole

Lorsque les TIC visent à fournir un service de relais de la parole à la parole, celui-ci doit permettre aux utilisateurs de téléphones souffrant de troubles de l’élocution ou de troubles cognitifs et à tout autre utilisateur de communiquer en leur fournissant une assistance mutuelle.

13.1.6 Services de relais de la parole à la parole

Lorsque les TIC visent à fournir un service de relais de la parole à la parole, celui-ci doit permettre aux utilisateurs de téléphones souffrant de troubles de l’élocution ou de troubles cognitifs et à tout autre utilisateur de communiquer en leur fournissant une assistance mutuelle.

13.1.6 Services de relais de la parole à la parole

Lorsque les TIC visent à fournir un service de relais de la parole à la parole, celui-ci doit permettre aux utilisateurs de téléphones souffrant de troubles de l’élocution ou ayant des capacités cognitives, linguistiques et d’apprentissage limitées, ainsi qu’à tout autre utilisateur, de communiquer en leur fournissant une assistance mutuelle.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

13.1.6 Services de relais de la parole à la parole

Lorsque les TIC visent à fournir un service de relais de la parole à la parole, celui-ci doit permettre aux utilisateurs de téléphones souffrant de troubles de l’élocution ou ayant des capacités cognitives, linguistiques et d’apprentissage limitées, ainsi qu’à tout autre utilisateur, de communiquer en leur fournissant une assistance mutuelle.

13.2 Accès aux services de relais

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et qu’un ensemble de services de relais est spécifié pour ce type de communication, l’accès à ces services de relais ne doit pas être bloqué pour les appels sortants et entrants.

REMARQUE 1 : La communication bidirectionnelle peut comprendre les communications vocales, par texte en temps réel ou par vidéo, seules ou combinées, appuyées par un service de relais et le système des TIC.

REMARQUE 2 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

13.2 Accès aux services de relais

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et qu’un ensemble de services de relais est spécifié pour ce type de communication, l’accès à ces services de relais ne doit pas être bloqué pour les appels sortants et entrants.

REMARQUE 1 : La communication bidirectionnelle peut comprendre les communications vocales, par texte en temps réel ou par vidéo, seules ou combinées, appuyées par un service de relais et le système des TIC.

REMARQUE 2 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

13.2 Accès aux services de relais

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services de relais, l’accès à ces services de relais ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par un service de relais et le système des TIC.

REMARQUE 1 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services de relais, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

Mise à jour explicative

Reformulation stylistique

Changement fonctionnel

13.2 Accès aux services de relais

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services de relais, l’accès à ces services de relais ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par un service de relais et le système des TIC.

REMARQUE 1 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services de relais, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

13.3 Accès aux services d’urgence

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et qu’un ensemble de services d’urgence est spécifié pour ce type de communication, l’accès à ces services d’urgence ne doit pas être bloqué pour les appels sortants et entrants.

REMARQUE 1 : La communication bidirectionnelle peut comprendre les communications vocales, par texte en temps réel ou par vidéo, seules ou combinées, appuyées par un service d’urgence et le système des TIC.

REMARQUE 2 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel avec les services d’urgence.

13.3 Accès aux services d’urgence

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et qu’un ensemble de services d’urgence est spécifié pour ce type de communication, l’accès à ces services d’urgence ne doit pas être bloqué pour les appels sortants et entrants.

REMARQUE 1 : La communication bidirectionnelle peut comprendre les communications vocales, par texte en temps réel ou par vidéo, seules ou combinées, appuyées par un service d’urgence et le système des TIC.

REMARQUE 2 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel avec les services d’urgence.

13.3 Accès aux services d’urgence

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services d’urgence, l’accès à ces services d’urgence ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par le service d’urgence et le système des TIC.

REMARQUE 1 : La présente exigence vise à assurer aux personnes handicapées un accès aux services d’urgence équivalent sur le plan fonctionnel.
REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services d’urgence, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

Mise à jour explicative

Reformulation stylistique

Changement fonctionnel

13.3 Accès aux services d’urgence

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services d’urgence, l’accès à ces services d’urgence ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par le service d’urgence et le système des TIC.

REMARQUE 1 : La présente exigence vise à assurer aux personnes handicapées un accès aux services d’urgence équivalent sur le plan fonctionnel.

REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services d’urgence, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

Liste des tableaux

Notes de bas de page

  1. Les critères de rendement fonctionnel 302.7 et 302.8 de l’article 508 et les énoncés de rendement fonctionnel 4.2.7 et 4.2.8 de la norme EN 301 549 inclusivement visent les mêmes exigences, même s’ils sont regroupés légèrement différemment dans chaque norme.Return to reference 1

  2. Les critères de rendement fonctionnel 302.7 et 302.8 de l’article 508 et les énoncés de rendement fonctionnel 4.2.7 et 4.2.8 de la norme EN 301 549 inclusivement visent les mêmes exigences, même s’ils sont regroupés légèrement différemment dans chaque norme.Return to reference 2

  3. L’article 508 précise que le mode de fonctionnement non visuel doit être une sortie vocale.Return to reference 3

  4. L’article 508 fait référence à une configuration de clavier spécifique qui n’est pas nécessairement pertinente à toutes les langues.Return to reference 4

  5. L’article 508 contient des exigences supplémentaires relatives à la superposition des touches alphabétiques sur les touches numériques.Return to reference 5

  6. Certaines différences quant à la méthode de calcul de l’espace pour les genoux et les pieds.Return to reference 6

  7. Certaines différences quant à la méthode de calcul de l’espace pour les genoux et les pieds.Return to reference 7

  8. Certaines différences quant à la méthode de calcul de l’espace pour les genoux et les pieds.Return to reference 7b

  9. Certaines différences quant à la méthode de calcul de l’espace pour les genoux et les pieds.Return to reference 8

  10. La norme EN 301 549 V3.1.1 (2019-11) contient une erreur: «Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher est considéré comme un espace libre pour les genoux et il devrait […] » Les 685 mm auraient dû être convertis en 27 po. Ce document démontre l’erreur dans la documentation originale de la norme EN.Return to reference 9

  11. La norme EN 301 549 V3.1.1 (2019-11) contient une erreur: «Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher est considéré comme un espace libre pour les genoux et il devrait […] » Les 685 mm auraient dû être convertis en 27 po. Ce document démontre l’erreur dans la documentation originale de la norme EN.Return to reference 10

  12. L’article 508 fait référence à la norme 47 CFR 68.317 (une réglementation américaine), tandis que la norme EN 301 549 fait référence au niveau spécifique de gain de volume requis.Return to reference 11

  13. La norme EN 301 549 comprend des exigences plus spécifiques en matière de gain de volume.Return to reference 12

  14. Chacune fait référence à des normes locales pertinentes.Return to reference 13

  15. Chacune fait référence à des normes locales pertinentes.Return to reference 14

  16. Les exigences de la norme EN 301 549 n’ont qu’une valeur informative et font référence à une limite de fréquence supérieure plutôt qu’à la norme de l’UTI.Return to reference 15

  17. La norme EN 301 549 fournit les exigences relatives au TTR, dont il est question ci-dessous.Return to reference 16

  18. La norme EN 301 549 précise qu’elle doit être offerte « en mode textuel et dans au moins un autre mode » tandis que l’article 508 précise qu’elle doit être « visible et audible ».Return to reference 17

  19. La norme EN 301 549 contient des exigences plus spécifiques.Return to reference 18

  20. La norme EN 301 549 contient des exigences plus spécifiques.Return to reference 19

  21. La norme EN 301 549 contient des exigences plus spécifiques.Return to reference 20

  22. La norme EN 301 549 contient des exigences plus spécifiques.Return to reference 21

  23. L’article 508 fait référence aux normes locales spécifiques relatives aux syntoniseurs de télévision numérique.Return to reference 22

  24. L’article 508 met l’accent sur les pièces manœuvrables tandis que la norme EN 301 549 met l’accent sur le niveau d’interaction.Return to reference 23

  25. L’article 508 met l’accent sur les pièces manœuvrables tandis que la norme EN 301 549 met l’accent sur le niveau d’interaction.Return to reference 24

  26. L’article 508 mentionne spécifiquement les touches; tandis que la norme EN 301 549 a une portée plus large et doit inclure les touches.Return to reference 25

  27. L’article 508 exige que le délai soit réglé jusqu’à 2 secondes, tandis que la norme EN 301 549 exige le réglage du délai jusqu’à 0,5 seconde.Return to reference 26

  28. La norme EN 301 549 considère la réponse minutée comme un problème logiciel. Voir 11.2.1.17 (réglable du délai).Return to reference 27

  29. Les clauses des normes EN 301 549 V1.1.1 (2014) et V2.1.2 (2018) de la série 407.8 sont des recommandations (« devrait » par opposition à « doit »). Toutefois, les dispositions de la norme 301 549 V3.1.1 (2019) sont des exigences (« doit » par opposition à « devrait »).Return to reference 28

  30. La norme EN 301 549 considère les problèmes liés au clignotement et à la photosensibilité comme des critères de rendement fonctionnel (voir 4.2.9) et un critère logiciel (voir 11.2.1.19)Return to reference 29

  31. La norme EN 301 549 considère les problèmes liés à la transmission des renseignements par multiples modalités comme des problèmes logiciels (voir 11.2.1.9)Return to reference 30

  32. Aucune clause correspondante dans la norme EN 301 549. Certains aspects sont abordés dans les articles 5.1.5, 7.1.1, 7.1.2, 7.3, 11.2.1.2, 11.2.1.3 et 11.2.1.5 de la norme EN 301 549 (2014).Return to reference 31

  33. Aucune clause correspondante dans la norme EN 301 549. Certains aspects sont abordés dans les articles 5.1.3, 7.2.2 et 11.3 de la norme

    EN 301 549 (2014).Return to reference 32

  34. Aucune clause correspondante dans la norme EN 301 549. La question de l’interopérabilité avec les technologies d’assistance est abordée à l’article 11.3 de la norme EN 301 549 (2014).Return to reference 33

  35. Aucune clause correspondante dans la norme EN 301 549, mais la clause 11.6.3 couvre la même exigence sans préciser PDF.Return to reference 34

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Mise en correspondance entre l’article 508 révisé (Revised Section 508) et la norme EN 301 549 (2014, 2018, 2019 et 2021)

Comme les normes EN 301 549 (en anglais seulement) continuent, d’évoluer et de publier des mises à jour, le présent document montre la progression des normes EN 301 549 depuis 2014, jusqu’aux mises à jour de 2018, 2019 et 2021. Ces renseignements sont importants, car le GC se dirige vers l’adoption de la norme EN 301 549 (2021)) comme norme d’accessibilité pour les TIC. Le GC, dans le cadre du processus d’invitation à soumissionner, peut demander aux fournisseurs de fournir des rapports de conformité en matière d’accessibilité basés sur le modèle d’accessibilité volontaire des produits Voluntary Product Accessibility Template - (VPAT). Chaque VPAT est fondé sur une norme technique précise – l’article 508 révisé, la norme EN 301 549 ou les Web Content Accessibility Guidelines (WCAG) (en anglais seulement). Les fournisseurs, les responsables techniques et les autorités contractantes doivent comprendre les différences entre ces normes pour s’assurer que les exigences d’accessibilité sont abordées comme il se doit.

Sur cette page

Avis de droit d’auteur

Ce document reproduit les exigences pertinentes en matière d’accessibilité des TIC du EN 301 549 norme européenne harmonisée « Exigences en accessibilité pour les produits et services en TIC », disponible en anglais seulement, (© utilisé sous la licence de l’Institut Européen de Normalisation des Télécommunications 2014, 2018, 2019 et 2021. © Comité Européen de Normalisation 2014, 2018, 2019 et 2021. © Comité Européen de Normalisation Électrotechnique 2014, 2018, 2019, 2021. Tous droits réservés.)

Avertissement

Ce document a été créé en février 2020 et mis à jour en octobre 2022 par le programme d’accessibilité, d’adaptation et de technologie informatique adaptée (AATIA) appartenant au ministère des Services partagés Canada (SPC). Au mieux de notre connaissance, il était exact en date d’octobre 2022. SPC ne garantit pas qu'une autorité compétente quelconque se fiera à ce travail. Si vous avez des questions au sujet de ce document, veuillez envoyer un courriel au programme d’AATIA.

Public visé

Le public visé comprend les responsables techniques et les autorités contractantes au sein de SPC et du gouvernement du Canada (GC), ainsi que les fournisseurs qui offrent des produits et des services de technologie de l’information et des communications (TIC).

Contexte

Ce document traite des normes techniques pour l’accessibilité des TIC. Les normes les plus courantes sont les Règles pour l’accessibilité des contenus Web (Web Content Accessibility Guidelines - WCAG), l’article 508 révisé (Revised Section 508) et la norme européenne harmonisée EN 301 549 pour l’accessibilité des TIC.

L'article 508 révisé (2017) fournit la norme technique permettant au gouvernement américain de s’approvisionner en produits et services accessibles. Cette norme est, à dessein, étroitement harmonisée avec la norme EN 301 549 (2014) - qui a tiré ses exigences en grande partie des normes de l’article 508 initial et des WCAG 2.0. Par conséquent, ces normes sont très similaires mais contiennent des différences essentielles. La norme EN 301 549 a été mise à jour quatre fois depuis la publication de l’article 508 révisé, ce qui a introduit d’autres différences entre les normes.

But

Le but du présent document est de cerner les similarités et les différences entre l’article 508 révisé et les normes EN 301 549.

Comme les normes EN 301 549 continuent d’évoluer et de publier des mises à jour, le présent document montre la progression des normes EN 301 549 depuis 2014, jusqu’aux mises à jour de 2018, 2019 et 2021. Ces renseignements sont importants, car le GC se dirige vers l’adoption de la norme EN 301 549 (2021)) comme norme d’accessibilité pour les TIC. Le GC, dans le cadre du processus d’invitation à soumissionner, peut demander aux fournisseurs de fournir des rapports de conformité en matière d’accessibilité basés sur le modèle d’accessibilité volontaire des produits (Voluntary Product Accessibility Template - VPAT). Chaque VPAT est fondé sur une norme technique précise – l’article 508 révisé, la norme EN 301 549 ou les WCAG. Les fournisseurs, les responsables techniques et les autorités contractantes doivent comprendre les différences entre ces normes pour s’assurer que les exigences d’accessibilité sont abordées comme il se doit.

Résumé des différences

Des WCAG à l’article révisé 508 / la norme EN 301 549

Les WCAG, bien qu’elles soient neutres sur le plan technologique, sont habituellement applicables aux sites Web et aux applications Web. Pour ces produits, spécifier WCAG 2.0 niveau AA ou 2.1 niveau AA comme norme technique peut être suffisant. Cependant, les autres normes comprennent des exigences supplémentaires qui peuvent s’appliquer aux applications Web qui fournissent l’une ou l’autre des caractéristiques suivantes : caractéristiques d’accessibilité documentées, outils-auteurs, communication bidirectionnelle, vidéo et conversion de l’information entre formats électroniques. Les autres normes comprennent également des exigences relatives au soutien et à la documentation, qui peuvent s’appliquer aux achats de sites Web ou d’applications Web.

Par l’intermédiaire du groupe de travail WCAG2ICT, les exigences des WCAG ont été adaptées pour répondre plus précisément aux exigences d’autres types de TIC, notamment les logiciels et les documents non Web. Ces adaptations ont été intégrées dans l’article 508 révisé et dans la norme EN 301 549, de sorte que la spécification de ces normes, plutôt que des WCAG, donnera lieu à des exigences d’accessibilité plus claires pour les produits de TIC non Web.

Bien que l’article 508 révisé et la norme EN 301 549 incluent les exigences à niveaux des WCAG, ces normes ont une portée plus large. Pour l’équipement de TIC et les services de TIC, les WCAG n’aborderont pas comme il se doit les exigences d’accessibilité. Si la fonctionnalité du produit ou du service risque de ne pas être entièrement abordée par les WCAG, les approvisionnements du GC devraient spécifier la norme EN 301 549.

De l’article 508 révisé à la norme EN 301 549 (2014)

Ces normes sont étroitement harmonisées. Certaines exigences varient pour ce qui est de la spécificité, la norme EN 301 549 adoptants habituellement une approche plus générale. Les exigences de l’article 508 révisé pourraient faire référence à des normes américaines précises, tandis que la norme EN 301 549 inclut les spécifications pertinentes dans le document ou fait référence à des normes internationales. Certaines exigences générales de l’article 508 révisé ne sont abordées que dans le chapitre sur les logiciels de la norme EN 301 549, de sorte qu’il puisse être nécessaire d’inclure les exigences relatives aux logiciels même pour les dispositifs matériels dotés d’écrans.

De la norme EN 301 549 (2014) à la norme EN 301 549 (2018)

Principalement, les chapitres se rapportant aux WCAG (9, 10 et 11) diffèrent entre ces versions, ainsi que plusieurs mises à jour explicatives, reformulations stylistiques, changements de numérotation et changements fonctionnels. La version 2014 inclut tous les critères de succès des WCAG 2.0 niveau A et AA, tandis que la version 2018 est mise à jour pour faire directement référence à tous les critères de succès des WCAG 2.1 niveau A et AA. (Bien que les versions 2018 et 2019 ne reproduisent pas le texte des WCAG, nous avons inclus les nouvelles exigences avec le texte dans ce document par souci de clarté). La numérotation des chapitres se rapportant aux WCAG dans la version 2018 suit directement les critères de succès des WCAG 2.1. Par exemple, la clause 9.2.3.1 de la norme EN 301 549 fait référence au critère de succès 2.3.1 des WCAG.

De la norme EN 301 549 (2018) à la norme EN 301 549 (2019)

La majorité des changements sont des reformulations stylistiques et des notes explicatives supplémentaires. Il y a 14 nouvelles exigences, portant principalement sur l’utilisation avec une audition limitée. Quelques exigences de la version 2018 ont été divisées ou regroupées. Les exigences relatives à l’accès physique aux TIC ont été retravaillées pour indiquer « 8.3 TIC fixes ». La numérotation est autrement cohérente entre les versions.

De la norme EN 301 549 (2019) à la norme EN 301 549 (2021)

Le document EN 301 549 V3.2.1 (2021) a été élaboré à partir de la norme EN 301 549 V2.1.2 (2018). Il n’y a pas de nouvelles exigences. Le tableau des modifications de suivi de l’annexe F a été ajouté pour les futures versions. Quelques clarifications à 7.1.1 concernant le sous-titrage, mais la numérotation est autrement cohérente entre les versions. La numérotation des chapitres 9, 10 et 11 relatifs aux WCAG dans la version 2021 suit directement les critères de succès des WCAG 2.1. Par exemple, la clause 9.2.3.1 de la norme EN 301 549 (2021) fait référence au critère de succès 2.3.1 des WCAG. Comme indiqué dans les notes de bas de page, certains éléments renvoient à des clauses qui ne sont pas incluses dans le présent document. Ils ne sont inclus que s’il s'agit d’une nouvelle exigence et qu’ils renvoient uniquement aux lignes directrices des WCAG.

Sources

Tableaux comparatifs

Glossaire

Reformulation stylistique :
le texte du critère modifie ce qui est dit, mais ne modifie pas ce que le critère demande, ni n’ajoute de nouveau contenu ou de nouvelles stipulations au critère existant.
Changement fonctionnel :
le texte du critère modifie considérablement ce que le critère demande, par exemple : le mot « devrait » (dénotant une recommandation) est remplacé par le mot « doit » (dénotant une exigence).
Mise à jour explicative :
le texte comporte des contenus ou des stipulations qui clarifient le but du critère sans en changer carrément l’objectif, par exemple en précisant la source d'un document.
Changement de numérotation :
la numérotation des critères est mise à jour en raison de l’intégration de la numérotation des WCAG dans le document ou d’un changement de l’ordre dans lequel ils apparaissent dans le document pour une meilleure fluidité et une meilleure compréhension.
Nouvelle exigence :
un critère qui n’existe pas dans une version précédente du document EN 301 549. Plusieurs nouveaux critères ont été ajoutés dans la version 2019 qui ne figurent ni dans la version 2014 ni dans la version 2018.

Les changements entre les versions de l’EN 301 549 sont ainsi soulignés :

  1. Pour les changements dans les hyperliens, les changements sont reflétés en gras, à l’aide du style de texte bleu fort souligné.
  2. Pour les changements dans le texte, les changements sont reflétés en gras, à l’aide du style de texte fort.
  3. Pour les changements dans le titre de la clause, les changements sont reflétés en gras, à l’aide du style de texte bleu fort.
Sélectionner pour voir les changements

Liste des tableaux

Liste des tableaux

Chapitre 2 – Exigences relatives à la portée

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

E207.2 Conformité des WCAG

Les composants de l’interface utilisateur ainsi que le contenu des plateformes et des applications doivent être conformes aux critères de succès de niveau A et de niveau AA et aux exigences de conformité spécifiées pour les pages Web dans les WCAG 2.0.

EXCEPTIONS :

  1. Les logiciels qui sont des technologies d’assistance et qui prennent en charge les services d’accessibilité de la plateforme n’ont pas à être conformes à la clause E207.2.
  2. Les logiciels non Web n’ont pas à être conformes aux quatre critères de succès suivants dans les WCAG 2.0 : 2.4.1 Contourner des blocs; 2.4.5 Accès multiples; 3.2.3 Navigation cohérente; et 3.2.4 Identification cohérente.
  3. Les logiciels non Web n’ont pas à être conformes à l’exigence de conformité 3 Processus complets des WCAG 2.0.

Les chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.0 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).

EN 301 549 Série vidéo

Reformulation stylistiqueLes chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).Changement fonctionnelLes chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).Les chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11)

Chapitre 3 – Critères de rendement fonctionnel

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

302.1 Sans vision

Lorsqu’un mode de fonctionnement visuel est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas la vision des utilisateurs.

4.2.1 Utilisation sans vision

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas la vision.

REMARQUE : Les interfaces utilisateur audio et tactiles peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.1 Utilisation sans vision

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas la vision.

REMARQUE 1 : Une page Web ou une application ayant une structure sémantique bien formée peut permettre aux utilisateurs sans vision de naviguer dans une interface utilisateur visuelle et d’interagir avec celle-ci.

REMARQUE 2 : Les interfaces utilisateur audio et tactiles peuvent contribuer au respect de cette clause.

Mise à jour explicative

4.2.1 Utilisation sans vision

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent au moins un mode de fonctionnement qui ne requiert pas la vision. Ceci est essentiel pour les utilisateurs sans vision et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Une page Web ou une application ayant une structure sémantique bien formée peut permettre aux utilisateurs sans vision de naviguer dans une interface utilisateur visuelle et d’interagir avec celle-ci.

REMARQUE 2 : Les interfaces utilisateur audio et tactiles peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.1 Utilisation sans vision

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent au moins un mode de fonctionnement qui ne requiert pas la vision. Ceci est essentiel pour les utilisateurs sans vision et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Une page Web ou une application ayant une structure sémantique bien formée peut permettre aux utilisateurs sans vision de naviguer dans une interface utilisateur visuelle et d’interagir avec celle-ci.

REMARQUE 2 : Les interfaces utilisateur audio et tactiles peuvent contribuer au respect de cette clause.

302.2 Avec vision limitée

Lorsqu’un mode de fonctionnement visuel est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui permet aux utilisateurs d’utiliser leur vision limitée.

4.2.2 Utilisation avec vision limitée

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec des fonctions leur permettant de mieux utiliser leur vision limitée.

REMARQUE 1 : Le grossissement, la réduction du champ de vision requis et le contrôle du contraste, de la luminosité et de l’intensité peuvent contribuer au respect de cette clause.

REMARQUE 2 : Lorsque des caractéristiques importantes de l’interface utilisateur dépendent de la perception de la profondeur, la fourniture de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une vision limitée peuvent également bénéficier d’un accès non visuel (voir la clause 4.2.1)

Reformulation stylistique

Mise à jour explicative

4.2.2 Utilisation avec vision limitée

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec des fonctions leur permettant de mieux utiliser leur vision limitée.

REMARQUE 1 : Le grossissement, la réduction du champ de vision requis et le contrôle du contraste, de la luminosité et de l’intensité peuvent contribuer au respect de cette clause.

REMARQUE 2 : Lorsque des caractéristiques importantes de l’interface utilisateur dépendent de la perception de la profondeur, la fourniture de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une vision limitée peuvent également bénéficier d’un accès non visuel (voir la clause 4.2.1)

4.2.2 Utilisation avec vision limitée

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent des fonctions permettant aux utilisateurs de mieux utiliser leur vision limitée. Ceci est essentiel pour les utilisateurs ayant une vision limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Le grossissement, la réduction du champ de vision requis et le contrôle du contraste, de la luminosité et de l’intensité peuvent contribuer au respect de cette clause.

REMARQUE 2 : Lorsque des caractéristiques importantes de l’interface utilisateur dépendent de la perception de la profondeur, la fourniture de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une vision limitée peuvent également bénéficier d’un accès non visuel (voir la clause 4.2.1)

Reformulation stylistique

Mise à jour explicative

4.2.2 Utilisation avec vision limitée

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent des fonctions permettant aux utilisateurs de mieux utiliser leur vision limitée. Ceci est essentiel pour les utilisateurs ayant une vision limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Le grossissement, la réduction du champ de vision requis et le contrôle du contraste, de la luminosité et de l’intensité peuvent contribuer au respect de cette clause.

REMARQUE 2 : Lorsque des caractéristiques importantes de l’interface utilisateur dépendent de la perception de la profondeur, fournir des méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une vision limitée peuvent également bénéficier d’un accès non visuel (voir la clause 4.2.1)

302.3 Sans perception des couleurs

Lorsqu’un mode de fonctionnement visuel est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui n’exige pas la perception des couleurs par les utilisateurs.

4.2.3 Utilisation sans perception des couleurs

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec un mode de fonctionnement visuel qui n’exige pas la perception des couleurs par les utilisateurs.

REMARQUE : Lorsque des caractéristiques importantes de l’interface utilisateur sont codées par couleur, l’ajout de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.3 Utilisation sans perception des couleurs

Lorsque les TIC prévoient un mode de fonctionnement visuel, certains utilisateurs auront besoin de TIC avec un mode de fonctionnement visuel qui n’exige pas la perception des couleurs par les utilisateurs.

REMARQUE : Lorsque des caractéristiques importantes de l’interface utilisateur sont codées par couleur, l’ajout de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

4.2.3 Utilisation sans perception des couleurs

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent un mode de fonctionnement visuel qui n’exige pas la perception des couleurs par les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une perception limitée des couleurs et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : Lorsque des caractéristiques importantes de l’interface utilisateur sont codées par couleur, l’ajout de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.3 Utilisation sans perception des couleurs

Lorsque les TIC prévoient un mode de fonctionnement visuel, les TIC fournissent un mode de fonctionnement visuel qui n’exige pas la perception des couleurs par les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une perception limitée des couleurs et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : Lorsque des caractéristiques importantes de l’interface utilisateur sont codées par couleur, l’ajout de méthodes supplémentaires de distinction entre les caractéristiques peut contribuer au respect de cette clause.

302.4 Sans audition

Lorsqu’un mode de fonctionnement sonore est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas l’audition des utilisateurs.

4.2.4 Utilisation sans audition

Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas l’audition.

REMARQUE : Les interfaces utilisateur visuelles et tactiles peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.4 Utilisation sans audition

Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin de TIC avec au moins un mode de fonctionnement qui ne requiert pas l’audition.

REMARQUE : Les interfaces utilisateur visuelles et tactiles peuvent contribuer au respect de cette clause.

4.2.4 Utilisation sans audition

Lorsque les TIC prévoient un mode de fonctionnement sonore, les TIC fournissent au moins un mode de fonctionnement qui ne requiert pas l’audition. Ceci est essentiel pour les utilisateurs sans audition et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : Les interfaces utilisateur visuelles et tactiles, y compris celles fondées sur la langue des signes, peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.4 Utilisation sans audition

Lorsque les TIC prévoient un mode de fonctionnement sonore, les TIC fournissent au moins un mode de fonctionnement qui ne requiert pas l’audition. Ceci est essentiel pour les utilisateurs sans audition et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : Les interfaces utilisateur visuelles et tactiles, y compris celles fondées sur la langue des signes, peuvent contribuer au respect de cette clause.

302.5 Avec audition limitée

Lorsqu’un mode de fonctionnement sonore est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui permet aux utilisateurs d’utiliser leur audition limitée.

4.2.5 Utilisation avec audition limitée

Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin des TIC avec des fonctions audio améliorées.

REMARQUE 1 : L’amélioration de la clarté audio, la réduction du bruit de fond, l’augmentation de la plage de volume et l’augmentation du volume dans la plage de fréquences supérieures peuvent contribuer au respect de cette clause.

REMARQUE 2 : Les utilisateurs ayant une audition limitée peuvent également bénéficier d’un accès non auditif (voir la clause 4.2.4).

Reformulation stylistique

Mise à jour explicative

4.2.5 Utilisation avec audition limitée

Lorsque les TIC prévoient un mode de fonctionnement sonore, certains utilisateurs auront besoin des TIC avec des fonctions audio améliorées.

REMARQUE 1 : L’amélioration de la clarté audio, la réduction du bruit de fond, l’augmentation de la plage de volume et l’augmentation du volume dans la plage de fréquences supérieures peuvent contribuer au respect de cette clause.

REMARQUE 2 : Les utilisateurs ayant une audition limitée peuvent également bénéficier d’un accès non auditif (voir la clause 4.2.4).

4.2.5 Utilisation avec audition limitée

Lorsque les TIC prévoient un mode de fonctionnement sonore, les TIC fournissent des fonctions audios améliorées. Ceci est essentiel pour les utilisateurs ayant une audition limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : L’amélioration de la clarté audio, la réduction du bruit de fond, l’offre d’une option monaurale commune, le réglage d’équilibre des deux canaux audio, l’augmentation de la plage de volume et l’augmentation du volume dans la plage de fréquences supérieures peuvent contribuer au respect de cette clause.

REMARQUE 2 : Permettre l'utilisation d’aides de suppléance à l’audition, comme des casques avec annulation du bruit (connectés par câble, Bluetooth ou WLAN) peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une audition limitée peuvent également bénéficier d’un accès non auditif (voir la clause 4.2.4).

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

4.2.5 Utilisation avec audition limitée

Lorsque les TIC prévoient un mode de fonctionnement sonore, les TIC fournissent des fonctions audios améliorées. Ceci est essentiel pour les utilisateurs ayant une audition limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : L’amélioration de la clarté audio, la réduction du bruit de fond, l’offre d’une option monaurale commune, le réglage d’équilibre des deux canaux audio, l’augmentation de la plage de volume et l’augmentation du volume dans la plage de fréquences supérieures peuvent contribuer au respect de cette clause.

REMARQUE 2 : Permettre l'utilisation d’aides de suppléance à l’audition, comme des casques avec annulation du bruit (connectés par câble, Bluetooth ou WLAN) peut contribuer au respect de cette clause.

REMARQUE 3 : Les utilisateurs ayant une audition limitée peuvent également bénéficier d’un accès non auditif (voir la clause 4.2.4).

302.6 Sans capacité vocale

Lorsque la contribution vocale est utilisée pour la saisie, le contrôle ou le fonctionnement, les TIC doivent fournir au moins un mode de fonctionnement qui n’exige pas la contribution vocale des utilisateurs.

4.2.6 Utilisation sans capacité vocale

Lorsque les TIC nécessitent la contribution vocale des utilisateurs, certains utilisateurs auront besoin des TIC pour fournir au moins un mode de fonctionnement qui n’exige pas d’entrée vocale.

REMARQUE 1 : Cette clause couvre les solutions de rechange à l’utilisation des sons générés oralement, y compris la parole, les sifflements, les clics, etc.

REMARQUE 2 : Le clavier, le stylo ou les interfaces utilisateur tactiles peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.6 Utilisation sans capacité vocale

Lorsque les TIC nécessitent la contribution vocale des utilisateurs, certains utilisateurs auront besoin des TIC pour fournir au moins un mode de fonctionnement qui n’exige pas d’entrée vocale.

REMARQUE 1 : Cette clause couvre les solutions de rechange à l’utilisation des sons générés oralement, y compris la parole, les sifflements, les clics, etc.

REMARQUE 2 : Le clavier, le stylo ou les interfaces utilisateur tactiles peuvent contribuer au respect de cette clause.

4.2.6 Utilisation sans capacité vocale ou avec une capacité vocale limitée

Lorsque les TIC nécessitent la contribution vocale des utilisateurs, les TIC fournissent au moins un mode de fonctionnement qui n’exige pas d’entrée vocale. Ceci est essentiel pour les utilisateurs sans capacité vocale ou ayant une capacité vocale limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : La sortie vocale comprend la parole et les autres sons générés oralement, comme les sifflements et les clics.

REMARQUE 2 : Le clavier, le stylo ou les interfaces utilisateur tactiles peuvent contribuer au respect de cette clause.

Changement fonctionnel

Reformulation stylistique

Mise à jour explicative

4.2.6 Utilisation sans capacité vocale ou avec une capacité vocale limitée

Lorsque les TIC nécessitent la contribution vocale des utilisateurs, les TIC fournissent au moins un mode de fonctionnement qui n’exige pas d’entrée vocale. Ceci est essentiel pour les utilisateurs sans capacité vocale ou ayant une capacité vocale limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : La sortie vocale comprend la parole et les autres sons générés oralement, comme les sifflements et les clics.

REMARQUE 2 : Le clavier, le stylo ou les interfaces utilisateur tactiles peuvent contribuer au respect de cette clause.

302.7 Avec une capacité de manipulation limitée

Lorsqu’un mode de fonctionnement manuel est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui n’exige pas un contrôle de la motricité fine ou des actions manuelles simultanées des utilisateurs.1

4.2.7 Utilisation avec une capacité de manipulation ou de force limitée

Lorsque les TIC nécessitent des actions manuelles, certains utilisateurs auront besoin de TIC avec des caractéristiques qui permettent aux utilisateurs d’utiliser les TIC par d’autres actions ne nécessitant aucune manipulation ou force de la main.

REMARQUE 1 : Parmi les exemples d’opérations que les utilisateurs peuvent ne pas être en mesure d’effectuer, mentionnons celles qui nécessitent un contrôle de la motricité fine, des gestes dépendant de la trajectoire, un pincement, une torsion du poignet, une prise ferme ou des actions manuelles simultanées.

REMARQUE 2 : L’utilisation d’une seule main, la saisie séquentielle des touches et les interfaces utilisateur vocales peuvent contribuer au respect de cette clause.

REMARQUE 3 : Certains utilisateurs ont une force de la main limitée et peuvent ne pas être en mesure d’atteindre le niveau de force nécessaire pour effectuer une opération. D’autres solutions d’interface utilisateur qui ne nécessitent pas de force manuelle peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.7 Utilisation avec une capacité de manipulation ou de force limitée

Lorsque les TIC nécessitent des actions manuelles, certains utilisateurs auront besoin de TIC avec des caractéristiques qui permettent aux utilisateurs d’utiliser les TIC par d’autres actions ne nécessitant aucune manipulation ou force de la main.

REMARQUE 1 : Parmi les exemples d’opérations que les utilisateurs peuvent ne pas être en mesure d’effectuer, mentionnons celles qui nécessitent un contrôle de la motricité fine, des gestes dépendant de la trajectoire, un pincement, une torsion du poignet, une prise ferme ou des actions manuelles simultanées.

REMARQUE 2 : L’utilisation d’une seule main, la saisie séquentielle des touches et les interfaces utilisateur vocales peuvent contribuer au respect de cette clause.

REMARQUE 3 : Certains utilisateurs ont une force de la main limitée et peuvent ne pas être en mesure d’atteindre le niveau de force nécessaire pour effectuer une opération. D’autres solutions d’interface utilisateur qui ne nécessitent pas de force manuelle peuvent contribuer au respect de cette clause.

4.2.7 Utilisation avec une capacité de manipulation ou de force limitée

Lorsque les TIC nécessitent des actions manuelles, les TIC fournissent des caractéristiques qui permettent aux utilisateurs d’utiliser les TIC par d’autres actions ne nécessitant aucune manipulation, action simultanée ou force de la main. Ceci est essentiel pour les utilisateurs ayant une capacité de manipulation ou de force limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Parmi les exemples d’opérations que les utilisateurs peuvent ne pas être en mesure d’effectuer, mentionnons celles qui nécessitent un contrôle de la motricité fine, des gestes dépendant de la trajectoire, un pincement, une torsion du poignet, une prise ferme ou des actions manuelles simultanées.

REMARQUE 2 : L’utilisation d’une seule main, la saisie séquentielle des touches et les interfaces utilisateur vocales peuvent contribuer au respect de cette clause.

REMARQUE 3 : Certains utilisateurs ont une force de la main limitée et peuvent ne pas être en mesure d’atteindre le niveau de force nécessaire pour effectuer une opération. D’autres solutions d’interface utilisateur qui ne nécessitent pas de force manuelle peuvent contribuer au respect de cette clause.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

4.2.7 Utilisation avec une capacité de manipulation ou de force limitée

Lorsque les TIC nécessitent des actions manuelles, les TIC fournissent des caractéristiques qui permettent aux utilisateurs d’utiliser les TIC par d’autres actions ne nécessitant aucune manipulation, action simultanée ou force de la main. Ceci est essentiel pour les utilisateurs ayant une capacité de manipulation ou de force limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Parmi les exemples d’opérations que les utilisateurs peuvent ne pas être en mesure d’effectuer, mentionnons celles qui nécessitent un contrôle de la motricité fine, des gestes dépendant de la trajectoire, un pincement, une torsion du poignet, une prise ferme ou des actions manuelles simultanées.

REMARQUE 2 : L’utilisation d’une seule main, la saisie séquentielle des touches et les interfaces utilisateur vocales peuvent contribuer au respect de cette clause.

REMARQUE 3 : Certains utilisateurs ont une force de la main limitée et peuvent ne pas être en mesure d’atteindre le niveau de force nécessaire pour effectuer une opération. D’autres solutions d’interface utilisateur qui ne nécessitent pas de force manuelle peuvent contribuer au respect de cette clause.

302.8 Avec une portée et une force limitée

Lorsqu’un mode de fonctionnement manuel est prévu, les TIC doivent fournir au moins un mode de fonctionnement qui peut être manœuvrable moyennant une portée et une force limitée.2

4.2.8 Utilisation à portée limitée

Lorsque les produits des TIC sont autonomes ou installés, les éléments opérationnels doivent être à la portée de tous les utilisateurs.

REMARQUE : La prise en compte des besoins des utilisateurs de fauteuils roulants et de l’éventail de statures d’utilisateur dans la disposition des éléments opérationnels de l’interface utilisateur peut contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.8 Utilisation à portée limitée

Lorsque les produits des TIC sont autonomes ou installés, les éléments opérationnels doivent être à la portée de tous les utilisateurs.

REMARQUE : La prise en compte des besoins des utilisateurs de fauteuils roulants et de l’éventail de statures d’utilisateur dans la disposition des éléments opérationnels de l’interface utilisateur peut contribuer au respect de cette clause.

4.2.8 Utilisation à portée limitée

Lorsque les produits des TIC sont autonomes ou installés, tous les éléments requis pour les opérations doivent être à la portée de tous les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une portée limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : La prise en compte des besoins des utilisateurs de fauteuils roulants et de l’éventail de statures d’utilisateur dans la disposition des éléments opérationnels de l’interface utilisateur peut contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.8 Utilisation à portée limitée

Lorsque les produits des TIC sont autonomes ou installés, tous les éléments requis pour les opérations doivent être à la portée de tous les utilisateurs. Ceci est essentiel pour les utilisateurs ayant une portée limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE : La prise en compte des besoins des utilisateurs de fauteuils roulants et de l’éventail de statures d’utilisateur dans la disposition des éléments opérationnels de l’interface utilisateur peut contribuer au respect de cette clause.

302.9 Avec des capacités linguistiques, cognitives et d’apprentissage limitées

Les TIC doivent fournir des fonctions qui sont plus simples à utiliser par les utilisateurs ayant des capacités cognitives, linguistiques et d’apprentissage limitées.

4.2.10 Utilisation avec une cognition limitée

Certains utilisateurs auront besoin de TIC avec des fonctions qui simplifient l’utilisation.

REMARQUE 1 : Cette clause vise à inclure les besoins des personnes ayant des capacités cognitives, linguistiques et d’apprentissage limitées.

REMARQUE 2 : Les temporisations ajustables, l’indication et la suggestion d’erreurs, ainsi qu’un ordre de mise au point logique sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

Reformulation stylistique

Mise à jour explicative

4.2.10 Utilisation avec une cognition limitée

Certains utilisateurs auront besoin de TIC avec des fonctions qui simplifient l’utilisation.

REMARQUE 1 : Cette clause vise à inclure les besoins des personnes ayant des capacités cognitives, linguistiques et d’apprentissage limitées.

REMARQUE 2 : Les temporisations ajustables, l’indication et la suggestion d’erreurs, ainsi qu’un ordre de mise au point logique sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

4.2.10 Utilisation avec des capacités cognitives, linguistiques et d’apprentissage limitées

Les TIC fournissent des fonctions et/ou une présentation qui simplifient la compréhension, le fonctionnement et l’utilisation. Ceci est essentiel pour les utilisateurs ayant une cognition limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Cette clause vise à inclure les besoins des personnes ayant des capacités cognitives, linguistiques et d’apprentissage limitées.

REMARQUE 2 : Fournir une sortie audio du texte est un exemple de soutien aux personnes ayant des capacités de lecture limitées.

REMARQUE 3 : Fournir une assistance orthographique et la prédiction des mots du texte est un exemple de soutien aux personnes ayant des capacités d'écriture limitées.

REMARQUE 4 : L’interaction avec le contenu peut être facilitée, et moins sujette aux erreurs, en présentant les tâches par étapes faciles à suivre.

Changement fonctionnel

Reformulation stylistique

Mise à jour explicative

4.2.10 Utilisation avec des capacités cognitives, linguistiques et d’apprentissage limitées

Les TIC fournissent des fonctions et/ou une présentation qui simplifient la compréhension, le fonctionnement et l’utilisation. Ceci est essentiel pour les utilisateurs ayant une cognition limitée et profite à beaucoup d’autres utilisateurs dans différentes situations.

REMARQUE 1 : Les temporisations ajustables, l’indication et la suggestion d’erreurs, ainsi qu’un ordre de mise au point logique sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

REMARQUE 2 : Fournir une sortie audio du texte est un exemple de soutien aux personnes ayant des capacités de lecture limitées.

REMARQUE 3 : Fournir une assistance orthographique et la prédiction des mots du texte est un exemple de soutien aux personnes ayant des capacités d'écriture limitées.

REMARQUE 4 : L’interaction avec le contenu peut être facilitée, et moins sujette aux erreurs, en présentant les tâches par étapes faciles à suivre.

Liste des tableaux

### Chapitre 4 – Matériel

402 Fonctions restreintes

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

402.1 Généralités

Les TIC ayant une fonction restreinte doivent pouvoir fonctionner sans que l’utilisateur ait à joindre ou à installer une technologie d’assistance autre que des casques d’écoute personnels ou d’autres coupleurs audios, et doivent être conformes à la clause 402.

5.1.2.2 Technologie d’assistance

Lorsque les TIC ont une fonction restreinte, cette fonction restreinte doit pouvoir fonctionner sans que l’utilisateur ait à joindre, connecter ou installer une technologie d’assistance et doit être conforme aux exigences génériques des clauses 5.1.3 à 5.1.7 selon le cas. Les casques d’écoute personnels et les boucles inductives ne doivent pas être considérés comme une technologie d’assistance aux fins de la présente clause.

Reformulation stylistique

Mise à jour explicative

5.1.2.2 Technologie d’assistance

Lorsque les TIC ont une fonction restreinte, cette fonction restreinte doit pouvoir fonctionner sans que l’utilisateur ait à joindre, connecter ou installer une technologie d’assistance et doit être conforme aux exigences génériques des clauses 5.1.3 à 5.1.6 selon le cas. Les casques d’écoute personnels et les boucles inductives ne doivent pas être considérés comme une technologie d’assistance aux fins de la présente clause.

Changement de numérotation

5.1.2.2 Technologie d’assistance

Lorsque les TIC ont une fonction restreinte, cette fonction restreinte doit pouvoir fonctionner sans que l’utilisateur ait à joindre, connecter ou installer une technologie d’assistance et doit être conforme aux exigences génériques des clauses 5.1.3 à 5.1.6 selon le cas. Les casques d’écoute personnels et les boucles inductives personnelles ne doivent pas être considérés comme une technologie d’assistance aux fins de la présente clause.

Reformulation stylistique

5.1.2.2 Technologie d’assistance

Lorsque les TIC ont une fonction restreinte, cette fonction restreinte doit pouvoir fonctionner sans que l’utilisateur ait à joindre, connecter ou installer une technologie d’assistance et doit être conforme aux exigences génériques des clauses 5.1.3 à 5.1.6 selon le cas. Les casques d’écoute personnels et les boucles inductives personnelles ne doivent pas être considérés comme une technologie d’assistance aux fins de la présente clause.

402.2 Sortie vocale activée

Les TIC ayant un écran d’affichage doivent être dotées d’une sortie vocale pour permettre aux utilisateurs atteints de déficience visuelle une utilisation complète et autonome.3

EXCEPTIONS :

  1. Les panneaux à messages variables conformes à la clause 402.5 n’ont pas à être dotés d’une sortie vocale.
  2. Une sortie vocale n’est pas requise lorsque les écrans d’affichage des TIC fournissent uniquement des indicateurs d’état et ces indicateurs sont conformes à la clause 409.
  3. Lorsque la sortie vocale ne peut pas être prise en charge en raison de contraintes de mémoire disponible ou de capacité du processeur, les TIC doivent être autorisées à se conformer à la clause 409 au lieu de 402.2.
  4. Les tonalités sonores doivent être autorisées à la place d’une sortie vocale lorsque le contenu des entrées utilisateurs n’est pas affiché tel qu’il a été saisi à des fins de sécurité, y compris, sans toutefois s’y limiter, les astérisques représentant des numéros d’identification personnels.
  5. Une sortie vocale n’est pas requise pour : l’emplacement de la machine, la date et l’heure de la transaction, le numéro de compte client et l’identificateur ou la plaque signalétique de la machine.
  6. Une sortie vocale n’est pas requise pour les annonces publicitaires et autres renseignements similaires, sauf si elles transmettent des renseignements pouvant être utilisés pour la transaction en cours.

5.1.3.1 Généralités

Lorsque des informations visuelles sont nécessaires pour permettre l’utilisation des fonctions des TIC restreintes aux technologies d’assistance pour la lecture d’écran, les TIC doivent prévoir au moins un mode de fonctionnement utilisant un accès non visuel pour permettre l’utilisation de ces fonctions.

REMARQUE 1 : L’accès non visuel peut se faire sous forme audio, y compris la parole, ou sous forme tactile.

REMARQUE 2 : Les informations visuelles nécessaires pour permettre l’utilisation de certaines fonctions peuvent inclure les instructions d’utilisation et l’orientation, les invites de transaction, la vérification des entrées utilisateur, les messages d’erreur et le contenu non textuel.

Reformulation stylistique

Mise à jour explicative

5.1.3.1 Généralités

Lorsque des informations visuelles sont nécessaires pour permettre l’utilisation des fonctions des TIC restreintes aux technologies d’assistance pour la lecture d’écran, les TIC doivent prévoir au moins un mode de fonctionnement utilisant un accès non visuel pour permettre l’utilisation de ces fonctions.

REMARQUE 1 : L’accès non visuel peut se faire sous forme audio, y compris la parole, ou sous forme tactile.

REMARQUE 2 : Les informations visuelles nécessaires pour permettre l’utilisation de certaines fonctions peuvent inclure les instructions d’utilisation et l’orientation, les invites de transaction, la vérification des entrées utilisateur, les messages d’erreur et le contenu non textuel.

5.1.3.1 Sortie audio des informations visuelles

Lorsque des informations visuelles sont nécessaires pour permettre l’utilisation des fonctions des TIC restreintes aux technologies d’assistance pour la lecture d’écran, les TIC doivent prévoir au moins un mode de fonctionnement utilisant un accès non visuel pour permettre l’utilisation de ces fonctions.

REMARQUE 1 : L’accès non visuel peut se faire sous forme audio, y compris la parole, ou sous forme tactile, comme le braille pour les utilisateurs sourds et aveugles.

REMARQUE 2 : Les informations visuelles nécessaires pour permettre l’utilisation de certaines fonctions peuvent inclure les instructions d’utilisation et l’orientation, les invites de transaction, la vérification des entrées utilisateur, les messages d’erreur et le contenu non textuel.

Mise à jour explicative

5.1.3.1 Sortie audio des informations visuelles

Lorsque des informations visuelles sont nécessaires pour permettre l’utilisation des fonctions des TIC restreintes aux technologies d’assistance pour la lecture d’écran, les TIC doivent prévoir au moins un mode de fonctionnement utilisant un accès non visuel pour permettre l’utilisation de ces fonctions.

REMARQUE 1 : L’accès non visuel peut se faire sous forme audio, y compris la parole, ou sous forme tactile, comme le braille pour les utilisateurs sourds et aveugles.

REMARQUE 2 : Les informations visuelles nécessaires pour permettre l’utilisation de certaines fonctions peuvent inclure les instructions d’utilisation et l’orientation, les invites de transaction, la vérification des entrées utilisateur, les messages d’erreur et le contenu non textuel.

402.2.1 Renseignements affichés à l’écran

Une sortie vocale doit être fournie pour tous les renseignements affichés à l’écran.

5.1.3.7 Sortie vocale pour l’information vidéo

Lorsqu’un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation de fonctions restreintes des TIC et que la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit présenter des informations équivalentes pour le contenu vidéo préenregistré.

REMARQUE : Cette sortie vocale peut prendre la forme d’une description audio ou d’une transcription auditive du contenu vidéo.

Reformulation stylistique

Mise à jour explicative

5.1.3.7 Sortie vocale pour l’information vidéo

Lorsqu’un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation de fonctions restreintes des TIC et que la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit présenter des informations équivalentes pour le contenu vidéo préenregistré.

REMARQUE : Cette sortie vocale peut prendre la forme d’une description audio ou d’une transcription auditive du contenu vidéo.

5.1.3.7 Sortie vocale pour l’information vidéo

Lorsqu’un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation de fonctions restreintes des TIC et que la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit présenter des informations équivalentes pour le contenu vidéo préenregistré.

REMARQUE : Cette sortie vocale peut prendre la forme d’une description audio ou d’une transcription auditive du contenu vidéo.

5.1.3.7 Sortie vocale pour l’information vidéo

Lorsqu’un contenu vidéo préenregistré est nécessaire pour permettre l’utilisation de fonctions restreintes des TIC et que la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit présenter des informations équivalentes pour le contenu vidéo préenregistré.

REMARQUE : Cette sortie vocale peut prendre la forme d’une description audio ou d’une transcription auditive du contenu vidéo.

402.2.1 Renseignements affichés à l’écran

Une sortie vocale doit être fournie pour tous les renseignements affichés à l’écran.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

Reformulation stylistique

Mise à jour explicative

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

402.2.2 Sorties transactionnelles

Lorsque des sorties transactionnelles sont fournies, la sortie vocale doit fournir de manière audible tous les renseignements nécessaires pour vérifier une transaction.

5.1.3.16 Reçus, billets et sorties transactionnelles

Lorsque les TIC sont restreintes à l’accès visuel et qu’elles fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service, une sortie vocale doit être fournie, comprenant tous les renseignements nécessaires pour conclure ou vérifier la transaction.

Dans le cas des distributeurs automatiques de billets, les copies imprimées des itinéraires et des cartes n’ont pas à être audibles.

REMARQUE : La sortie vocale peut être fournie par n’importe quel élément de l’ensemble du système de TIC.

Reformulation stylistique

Mise à jour explicative

5.1.3.16 Reçus, billets et sorties transactionnelles

Lorsque les TIC sont restreintes à l’accès visuel et qu’elles fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service, une sortie vocale doit être fournie, comprenant tous les renseignements nécessaires pour conclure ou vérifier la transaction.

Dans le cas des distributeurs automatiques de billets, les copies imprimées des itinéraires et des cartes n’ont pas à être audibles.

REMARQUE : La sortie vocale peut être fournie par n’importe quel élément de l’ensemble du système de TIC.

5.1.3.16 Reçus, billets et sorties transactionnelles

Lorsque les TIC sont restreintes à l’accès visuel et qu’elles fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service, une sortie vocale doit être fournie, comprenant tous les renseignements nécessaires pour conclure ou vérifier la transaction.

Dans le cas des distributeurs automatiques de billets, les copies imprimées des itinéraires et des cartes n’ont pas à être audibles.

REMARQUE : La sortie vocale peut être fournie par n’importe quel élément de l’ensemble du système de TIC.

5.1.3.16 Reçus, billets et sorties transactionnelles

Lorsque les TIC sont restreintes à l’accès visuel et qu’elles fournissent des reçus, des billets ou d’autres produits à la suite d’une transaction en libre-service, une sortie vocale doit être fournie, comprenant tous les renseignements nécessaires pour conclure ou vérifier la transaction.

Dans le cas des distributeurs automatiques de billets, les copies imprimées des itinéraires et des cartes n’ont pas à être audibles.

REMARQUE : La sortie vocale peut être fournie par n’importe quel élément de l’ensemble du système de TIC.

402.2.3 Type de fonctionnement vocal et coordination

La sortie vocale doit être fournie au moyen d’un mécanisme facilement accessible à tous les utilisateurs, y compris, sans toutefois s’y limiter, un connecteur accrédité par l’industrie ou un combiné téléphonique. La sortie vocale doit être enregistrée ou être une voix humaine numérisée, ou synthétisée. La sortie vocale doit être coordonnée avec les renseignements affichés à l’écran.

5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les fonctions sonores doivent être utilisées :

  1. soit directement au moyen d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci;
  2. soit au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

REMARQUE 1 : Les mécanismes intégrés ou fournis peuvent comprendre, mais sans s’y limiter, un haut-parleur, un combiné ou casque intégré ou un autre périphérique accrédité par l’industrie.

REMARQUE 2 : Par connexion accréditée par l’industrie, on entend par exemple une connexion sans fil.

REMARQUE 3 : Certains utilisateurs pourraient tirer parti d’un équipement à boucle inductive.

Reformulation stylistique

Mise à jour explicative

5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les fonctions sonores doivent être utilisées :

  1. soit directement au moyen d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci;
  2. soit au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

REMARQUE 1 : Les mécanismes intégrés ou fournis peuvent comprendre, mais sans s’y limiter, un haut-parleur, un combiné ou casque intégré ou un autre périphérique accrédité par l’industrie.

REMARQUE 2 : Par connexion accréditée par l’industrie, on entend par exemple une connexion sans fil.

REMARQUE 3 : Certains utilisateurs pourraient tirer parti d’un équipement à boucle inductive.

5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les fonctions sonores doivent être utilisées :

  1. soit directement au moyen d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci;
  2. soit au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

REMARQUE 1 : Les mécanismes intégrés ou fournis peuvent comprendre, mais sans s’y limiter, un haut-parleur, un combiné ou casque intégré ou un autre périphérique accrédité par l’industrie.

REMARQUE 2 : Par connexion accréditée par l’industrie, on entend par exemple une connexion sans fil.

REMARQUE 3 : Certains utilisateurs pourraient tirer parti d’un équipement à boucle inductive.

5.1.3.2 Mode de fonctionnement auditif incluant l’usage de la voix

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les fonctions sonores doivent être utilisées :

  1. soit directement au moyen d’un mécanisme d’assistance intégré dans les TIC ou offert avec celles-ci;
  2. soit au moyen d’un casque d’écoute qui peut être branché via une prise audio de 3,5 mm ou une connexion accréditée par l’industrie, et ce, sans exiger l’utilisation de la vision.

REMARQUE 1 : Les mécanismes intégrés ou fournis peuvent comprendre, mais sans s’y limiter, un haut-parleur, un combiné ou casque intégré ou un autre périphérique accrédité par l’industrie.

REMARQUE 2 : Par connexion accréditée par l’industrie, on entend par exemple une connexion sans fil.

REMARQUE 3 : Certains utilisateurs pourraient tirer parti d’un équipement à boucle inductive.

402.2.3 Type de fonctionnement vocal et coordination

La sortie vocale doit être fournie au moyen d’un mécanisme facilement accessible à tous les utilisateurs, y compris, sans toutefois s’y limiter, un connecteur accrédité par l’industrie ou un combiné téléphonique. La sortie vocale doit être enregistrée ou être une voix humaine numérisée, ou synthétisée. La sortie vocale doit être coordonnée avec les renseignements affichés à l’écran.

5.1.3.3 Corrélation de sortie sonore

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que l’information est affichée à l’écran, les TIC doivent fournir des informations auditives qui permettent à l’utilisateur de corréler l’audio avec l’information affichée à l’écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

Reformulation stylistique

Mise à jour explicative

5.1.3.3 Corrélation de sortie sonore

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que l’information est affichée à l’écran, les TIC doivent fournir des informations auditives qui permettent à l’utilisateur de corréler l’audio avec l’information affichée à l’écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

5.1.3.3 Corrélation de sortie sonore

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que l’information est affichée à l’écran, les TIC doivent fournir des informations auditives qui permettent à l’utilisateur de corréler l’audio avec l’information affichée à l’écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

5.1.3.3 Corrélation de sortie sonore

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que l’information est affichée à l’écran, les TIC doivent fournir des informations auditives qui permettent à l’utilisateur de corréler l’audio avec l’information affichée à l’écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio peut être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

402.2.4 Contrôle par l’utilisateur

La sortie vocale de toute fonction unique doit être automatiquement interrompue lorsqu’une transaction est sélectionnée. La sortie vocale doit pouvoir être répétée et mise en pause.

5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit pouvoir être interrompue et répétée à la demande de l’utilisateur, lorsque les exigences de sécurité le permettent.

REMARQUE 1 : Il est préférable de permettre à l’utilisateur de faire une pause plutôt que de simplement interrompre la sortie vocale.

REMARQUE 2 : Il est préférable de permettre à l’utilisateur de ne répéter que la partie la plus récente plutôt que de recommencer depuis le début.

Reformulation stylistique

Mise à jour explicative

5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit pouvoir être interrompue et répétée à la demande de l’utilisateur, lorsque les exigences de sécurité le permettent.

REMARQUE 1 : Il est préférable de permettre à l’utilisateur de faire une pause plutôt que de simplement interrompre la sortie vocale.

REMARQUE 2 : Il est préférable de permettre à l’utilisateur de ne répéter que la partie la plus récente plutôt que de recommencer depuis le début.

5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit pouvoir être interrompue et répétée à la demande de l’utilisateur, lorsque les exigences de sécurité le permettent.

REMARQUE 1 : Il est préférable de permettre à l’utilisateur de faire une pause plutôt que de simplement interrompre la sortie vocale.

REMARQUE 2 : Il est préférable de permettre à l’utilisateur de ne répéter que la partie la plus récente plutôt que de recommencer depuis le début.

5.1.3.4 Contrôle de la sortie vocale par l’utilisateur

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit pouvoir être interrompue et répétée à la demande de l’utilisateur, lorsque les exigences de sécurité le permettent.

REMARQUE 1 : Il est préférable de permettre à l’utilisateur de faire une pause plutôt que de simplement interrompre la sortie vocale.

REMARQUE 2 : Il est préférable de permettre à l’utilisateur de ne répéter que la partie la plus récente plutôt que de recommencer depuis le début.

402.2.4 Contrôle par l’utilisateur

La sortie vocale de toute fonction unique doit être automatiquement interrompue lorsqu’une transaction est sélectionnée. La sortie vocale doit pouvoir être répétée et mise en pause.

5.1.3.5 Interruption automatique de la sortie vocale

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC doivent interrompre la sortie vocale actuelle lorsqu’une action de l’utilisateur se produit et lorsque la nouvelle sortie vocale débute.

REMARQUE : Lorsqu’il est essentiel que l’utilisateur entende l’intégralité du message, par exemple une instruction de sécurité ou un avertissement, les TIC peuvent devoir bloquer toute action de l’utilisateur afin que la parole ne soit pas interrompue.

Reformulation stylistique

Mise à jour explicative

5.1.3.5 Interruption automatique de la sortie vocale

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC doivent interrompre la sortie vocale actuelle lorsqu’une action de l’utilisateur se produit et lorsque la nouvelle sortie vocale débute.

REMARQUE : Lorsqu’il est essentiel que l’utilisateur entende l’intégralité du message, par exemple une instruction de sécurité ou un avertissement, les TIC peuvent devoir bloquer toute action de l’utilisateur afin que la parole ne soit pas interrompue.

5.1.3.5 Interruption automatique de la sortie vocale

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC doivent interrompre la sortie vocale actuelle lorsqu’une action de l’utilisateur se produit et lorsque la nouvelle sortie vocale débute.

REMARQUE : Lorsqu’il est essentiel que l’utilisateur entende l’intégralité du message, par exemple une instruction de sécurité ou un avertissement, les TIC peuvent devoir bloquer toute action de l’utilisateur afin que la parole ne soit pas interrompue.

5.1.3.5 Interruption automatique de la sortie vocale

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC doivent interrompre la sortie vocale actuelle lorsqu’une action de l’utilisateur se produit et lorsque la nouvelle sortie vocale débute.

REMARQUE : Lorsqu’il est essentiel que l’utilisateur entende l’intégralité du message, par exemple une instruction de sécurité ou un avertissement, les TIC peuvent devoir bloquer toute action de l’utilisateur afin que la parole ne soit pas interrompue.

402.2.5 Instructions en braille

Lorsque la sortie vocale est requise par la clause 402.2, des instructions en braille doivent être fournies pour lancer le mode de fonctionnement vocal. Les services en braille doivent être obtenus par contrat et être conformes à la norme 36 CFR partie 1191, annexe D, article 703.3.1.

EXCEPTION : Les dispositifs à usage personnel n’ont pas à être conformes à la clause 402.2.5.

8.5 Indication tactile du mode vocal

Lorsque les TIC sont conçues pour une utilisation partagée et qu’une sortie vocale est disponible, une indication tactile des moyens permettant de lancer le mode de fonctionnement vocal doit être fournie.

REMARQUE : L’indication tactile peut inclure des instructions en braille.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.5 Indication tactile du mode vocal

Lorsque les TIC sont conçues pour une utilisation partagée et qu’une sortie vocale est disponible, une indication tactile des moyens permettant de lancer le mode de fonctionnement vocal doit être fournie.

REMARQUE : L’indication tactile peut inclure des instructions en braille.

8.5 Indication tactile du mode vocal

Lorsque les TIC sont conçues pour une utilisation partagée et qu’une sortie vocale est disponible, une indication tactile des moyens permettant de lancer le mode de fonctionnement vocal doit être fournie.

REMARQUE : L’indication tactile peut inclure des instructions en braille.

8.5 Indication tactile du mode vocal

Lorsque les TIC sont conçues pour une utilisation partagée et qu’une sortie vocale est disponible, une indication tactile des moyens permettant de lancer le mode de fonctionnement vocal doit être fournie.

REMARQUE : L’indication tactile peut inclure des instructions en braille.

402.3.1 Écoute privée

Lorsque les TIC fournissent un mode d’écoute privée, elles doivent fournir un mode de fonctionnement pour contrôler le volume. Lorsque les TIC fournissent une sortie par un transducteur audio qui est normalement tenu à l’oreille, il faut fournir un moyen de couplage magnétique efficace aux technologies auditives.

5.1.3.11 Volume d’écoute privé

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, et ce, par le biais d’un mécanisme d’écoute privée, les TIC doivent prévoir au moins un mode de fonctionnement non visuel pour contrôler le volume.

Reformulation stylistique

Mise à jour explicative

5.1.3.11 Volume d’écoute privé

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, et ce, par le biais d’un mécanisme d’écoute privée, les TIC doivent prévoir au moins un mode de fonctionnement non visuel pour contrôler le volume.

5.1.3.11 Volume d’écoute privé

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, et ce, par le biais d’un mécanisme d’écoute privée, les TIC doivent prévoir au moins un mode de fonctionnement non visuel pour contrôler le volume.

5.1.3.11 Volume d’écoute privé

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, et ce, par le biais d’un mécanisme d’écoute privée, les TIC doivent prévoir au moins un mode de fonctionnement non visuel pour contrôler le volume.

402.3.1 Écoute privée

Lorsque les TIC fournissent un mode d’écoute privée, elles doivent fournir un mode de fonctionnement pour contrôler le volume. Lorsque les TIC fournissent une sortie par un transducteur audio qui est normalement tenu à l’oreille, il faut fournir un moyen de couplage magnétique efficace aux technologies auditives.

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille et qui porte le symbole « T » spécifié dans la norme ETS 300 381, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1.

REMARQUE : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

Reformulation stylistique

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille et qui porte le symbole « T » spécifié dans la norme ETS 300 381 de l’ETSI, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 de l’ETSI et doit porter le symbole « T » spécifié dans la norme ETS 300 381 de l’ETSI.

REMARQUE 1 : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

REMARQUE 2 : Le couplage magnétique est également appelé couplage inductif pour bobine en T.

Reformulation stylistique

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 [2] de l’ETSI et doit porter le symbole « T » spécifié dans la norme ETS 300 381 [1].de l’ETSI.

REMARQUE 1 : Les TIC répondant aux exigences de la norme TIA-1083-A [i.24] sont réputées conformes aux exigences de la présente clause.

REMARQUE 2 : Le couplage magnétique est également appelé couplage inductif pour bobine en T.

402.3.1 Écoute privée

Lorsque les TIC fournissent un mode d’écoute privée, elles doivent fournir un mode de fonctionnement pour contrôler le volume. Lorsque les TIC fournissent une sortie par un transducteur audio qui est normalement tenu à l’oreille, il faut fournir un moyen de couplage magnétique efficace aux technologies auditives.

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

Reformulation stylistique

Mise à jour explicative

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

Mise à jour explicative

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 [3] de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 [i.1] sont réputées conformes aux exigences de la présente clause.

402.3.2 Écoute non privée

Lorsque les TIC fournissent une écoute non privée, une commande de volume incrémentielle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA. Une fonction doit être fournie pour rétablir automatiquement le volume au niveau par défaut après chaque utilisation.

5.1.3.12 Volume de l’enceinte

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et qu’elle est fournie par des haut-parleurs sur les TIC, une commande de volume incrémentielle non visuelle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

REMARQUE : Pour les environnements bruyants, un niveau de 65 dBA peut ne pas être suffisant.

Reformulation stylistique

5.1.3.12 Volume de l’enceinte

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et qu’elle est fournie par des haut-parleurs sur les TIC, une commande de volume incrémentielle non visuelle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

REMARQUE : Pour les environnements bruyants, un niveau de 65 dBA peut ne pas être suffisant.

5.1.3.12 Volume de l’enceinte

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et qu’elle est fournie par des haut-parleurs sur les TIC, une commande de volume incrémentielle non visuelle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

REMARQUE : Pour les environnements bruyants, un niveau de 65 dBA peut ne pas être suffisant.

5.1.3.12 Volume de l’enceinte

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et qu’elle est fournie par des haut-parleurs sur les TIC, une commande de volume incrémentielle non visuelle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA (-29 dBPaA).

REMARQUE : Pour les environnements bruyants, un niveau de 65 dBA peut ne pas être suffisant.

402.3.2 Écoute non privée

Lorsque les TIC fournissent une écoute non privée, une commande de volume incrémentielle doit être fournie avec une amplification de sortie jusqu’à un niveau d’au moins 65 dBA. Une fonction doit être fournie pour rétablir automatiquement le volume au niveau par défaut après chaque utilisation.

5.1.3.13 Réinitialisation du volume

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, une fonction qui réinitialise le volume à un niveau inférieur ou égal à 65 dBA après chaque utilisation doit être fournie, sauf si les TIC sont destinées à un seul utilisateur.

REMARQUE : Une fonction permettant de désactiver la fonction de réinitialisation du volume peut être fournie afin de permettre de respecter l’exception de l’utilisateur unique.

Reformulation stylistique

Mise à jour explicative

5.1.3.13 Réinitialisation du volume

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, une fonction qui réinitialise le volume à un niveau inférieur ou égal à 65 dBA après chaque utilisation doit être fournie, sauf si les TIC sont destinées à un seul utilisateur.

REMARQUE : Une fonction permettant de désactiver la fonction de réinitialisation du volume peut être fournie afin de permettre de respecter l’exception de l’utilisateur unique.

5.1.3.13 Réinitialisation du volume

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, une fonction qui réinitialise le volume à un niveau inférieur ou égal à 65 dBA après chaque utilisation doit être fournie, sauf si les TIC sont destinées à un seul utilisateur.

REMARQUE : Une fonction permettant de désactiver la fonction de réinitialisation du volume peut être fournie afin de permettre de respecter l’exception de l’utilisateur unique.

5.1.3.13 Réinitialisation du volume

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, une fonction qui réinitialise le volume à un niveau inférieur ou égal à 65 dBA après chaque utilisation doit être fournie, sauf si les TIC sont destinées à un seul utilisateur.

REMARQUE 1 : Une fonction permettant de désactiver la fonction de réinitialisation du volume peut être fournie afin de permettre de respecter l’exception de l’utilisateur unique.

402.4 Caractères sur les écrans d’affichage

Au moins un mode de caractères affiché à l’écran doit être dans une police sans empattement. Lorsque les TIC ne prévoient pas de fonction d’agrandissement de l’écran, les caractères doivent avoir une hauteur minimale de 4,8 mm (3/16 po) en fonction de la lettre majuscule « I ». Les caractères doivent se distinguer de leur arrière-plan, soit au moyen de caractères de couleur claire sur fond sombre, soit de caractères de couleur sombre sur fond clair.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE 1 : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE 1 : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

402.5 Caractères sur les panneaux à messages variables

Les caractères sur les panneaux à messages variables doivent être conformes à l’article 703.7 Panneaux à messages variables de l’ICC A117.1-2009 (incorporé par renvoi, voir l’article 702.6.1).

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

Mise à jour explicative

Changement fonctionnel

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;
  • D et H sont exprimés dans les mêmes unités.

REMARQUE : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

5.1.4 Fonction restreinte à l’agrandissement du texte

Lorsqu’une fonction quelconque des TIC est restreinte aux caractéristiques d’agrandissement du texte de la plateforme ou de la technologie d’assistance, les TIC doivent fournir un mode de fonctionnement dans lequel le texte et les images du texte nécessaires à toutes les fonctions sont affichés de telle manière qu’un « H » majuscule non accentué sous-tende un angle d’au moins 0,7 degré à une distance de visualisation spécifiée par le fournisseur.

L’angle sous-tendu, en degrés, peut être calculé à partir de la formule suivante :

Ψ = (180 x H)/(π x D)

Où :

  • ψ est l’angle sous-tendu en degrés;
  • H est la hauteur du texte;
  • D est la distance de visibilité;

  • D et H sont exprimés dans les mêmes unités.

REMARQUE 1 : L’intention est de fournir un mode de fonctionnement où le texte est suffisamment grand pour être utilisé par la plupart des utilisateurs ayant une basse vision.

Liste des tableaux

403 Données biométriques

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

403.1 Généralités

Les données biométriques ne doivent pas être le seul moyen d'identification ou de contrôle de l'utilisateur.

EXCEPTION : Lorsqu’au moins deux options de données biométriques utilisant différentes caractéristiques biologiques sont fournies, les TIC doivent être autorisées à utiliser les données biométriques comme seul moyen d’identification de l’utilisateur ou de contrôle.

5.3 Données biométriques

Lorsque les TIC utilisent des caractéristiques biologiques, elles ne s’appuient pas sur l’utilisation d’une caractéristique biologique particulière comme seul moyen d’identification de l’utilisateur ou de contrôle des TIC.

REMARQUE 1 : D’autres moyens d’identification des utilisateurs ou de contrôle des TIC pourraient être non biométriques ou biométriques.

REMARQUE 2 : Les méthodes biométriques fondées sur des caractéristiques biologiques dissemblables augmentent la probabilité que les personnes handicapées possèdent au moins une des caractéristiques biologiques précisées. Les empreintes digitales, les motifs rétiniens des yeux, la voix et le visage sont des exemples de caractéristiques biologiques dissemblables.

Reformulation stylistique

Mise à jour explicative

5.3 Données biométriques

Lorsque les TIC utilisent des caractéristiques biologiques, elles ne s’appuient pas sur l’utilisation d’une caractéristique biologique particulière comme seul moyen d’identification de l’utilisateur ou de contrôle des TIC.

REMARQUE 1 : D’autres moyens d’identification des utilisateurs ou de contrôle des TIC pourraient être non biométriques ou biométriques.

REMARQUE 2 : Les méthodes biométriques fondées sur des caractéristiques biologiques dissemblables augmentent la probabilité que les personnes handicapées possèdent au moins une des caractéristiques biologiques précisées. Les empreintes digitales, les motifs rétiniens des yeux, la voix et le visage sont des exemples de caractéristiques biologiques dissemblables.

5.3 Données biométriques

Lorsque les TIC utilisent des caractéristiques biologiques, elles ne s’appuient pas sur l’utilisation d’une caractéristique biologique particulière comme seul moyen d’identification de l’utilisateur ou de contrôle des TIC.

REMARQUE 1 : D’autres moyens d’identification des utilisateurs ou de contrôle des TIC pourraient être non biométriques ou biométriques.

REMARQUE 2 : Les méthodes biométriques fondées sur des caractéristiques biologiques dissemblables augmentent la probabilité que les personnes handicapées possèdent au moins une des caractéristiques biologiques précisées. Les empreintes digitales, les motifs rétiniens des yeux, la voix et le visage sont des exemples de caractéristiques biologiques dissemblables.

5.3 Données

biométriques

Lorsque les TIC utilisent des caractéristiques biologiques, elles ne s’appuient pas sur l’utilisation d’une caractéristique biologique particulière comme seul moyen d’identification de l’utilisateur ou de contrôle des TIC.

REMARQUE 1 : D’autres moyens d’identification des utilisateurs ou de contrôle des TIC pourraient être non biométriques ou biométriques.

REMARQUE 2 : Les méthodes biométriques fondées sur des caractéristiques biologiques dissemblables augmentent la probabilité que les personnes handicapées possèdent au moins une des caractéristiques biologiques précisées.

Liste des tableaux

404 Préservation des renseignements fournis pour l’accessibilité

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

404.1 Généralités

Les TIC qui transmettent ou convertissent des renseignements ou des communications ne doivent pas supprimer les renseignements libres fournis aux fins d’accessibilité ou doivent les restaurer à la livraison.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

Reformulation stylistique

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

Liste des tableaux

405 Confidentialité

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021
405.1 Généralités
Le même degré de protection des données d’entrée et de sortie doit être fourni à tous les utilisateurs. Lorsque la sortie vocale requise par la clause 402.2 est activée, l’écran ne doit pas s’éteindre automatiquement.

5.1.3.9 Accès privé aux données personnelles

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que la sortie contient des données considérées comme étant privées conformément à la politique de confidentialité applicable, la sortie sonore correspondante ne peut être fournie que par le biais d’un mécanisme d’écoute privée qui peut être connecté sans nécessiter l’utilisation de la vision, ou par tout autre mécanisme explicitement choisi par l’utilisateur.

REMARQUE 1 : Cette exigence ne s’applique pas dans les cas où les données ne sont pas définies comme étant privées conformément à la politique de confidentialité applicable ou lorsqu’il n’existe aucune politique de confidentialité applicable.

REMARQUE 2 : La sortie non privée peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

Reformulation stylistique

Mise à jour explicative

5.1.3.9 Accès privé aux données personnelles

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que la sortie contient des données considérées comme étant privées conformément à la politique de confidentialité applicable, la sortie sonore correspondante ne peut être fournie que par le biais d’un mécanisme d’écoute privée qui peut être connecté sans nécessiter l’utilisation de la vision, ou par tout autre mécanisme explicitement choisi par l’utilisateur.

REMARQUE 1 : Cette exigence ne s’applique pas dans les cas où les données ne sont pas définies comme étant privées conformément à la politique de confidentialité applicable ou lorsqu’il n’existe aucune politique de confidentialité applicable.

REMARQUE 2 : La sortie non privée peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.9 Accès privé aux données personnelles

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que la sortie contient des données considérées comme étant privées conformément à la politique de confidentialité applicable, la sortie sonore correspondante ne peut être fournie que par le biais d’un mécanisme d’écoute privée qui peut être connecté sans nécessiter l’utilisation de la vision, ou par tout autre mécanisme explicitement choisi par l’utilisateur.

REMARQUE 1 : Cette exigence ne s’applique pas dans les cas où les données ne sont pas définies comme étant privées conformément à la politique de confidentialité applicable ou lorsqu’il n’existe aucune politique de confidentialité applicable.

REMARQUE 2 : La sortie non privée peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.9 Accès privé aux données personnelles

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que la sortie contient des données considérées comme étant privées conformément à la politique de confidentialité applicable, la sortie sonore correspondante ne peut être fournie que par le biais d’un mécanisme d’écoute privée qui peut être connecté sans nécessiter l’utilisation de la vision, ou par tout autre mécanisme explicitement choisi par l’utilisateur.

REMARQUE 1 : Cette exigence ne s’applique pas dans les cas où les données ne sont pas définies comme étant privées conformément à la politique de confidentialité applicable ou lorsqu’il n’existe aucune politique de confidentialité applicable.

REMARQUE 2 : La sortie non privée peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

405.1 Généralités

Le même degré de protection des données d’entrée et de sortie doit être fourni à tous les utilisateurs. Lorsque la sortie vocale requise par la clause 402.2 est activée, l’écran ne doit pas s’éteindre automatiquement.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

Reformulation stylistique

Mise à jour explicative

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

5.1.3.8 Entrée masquée

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte et que les caractères affichés sont des caractères de masquage, la sortie sonore ne doit pas être une version orale des caractères saisis, à moins que l’on sache que la sortie sonore est destinée à être fournie uniquement par le biais d’un mécanisme d’écoute privée, ou que l’utilisateur ait explicitement choisi de permettre une sortie sonore non privée.

REMARQUE 1 : Les caractères de masquage sont habituellement affichés à des fins de sécurité et comprennent, sans toutefois s’y limiter, les astérisques représentant les numéros d’identification personnels.

REMARQUE 2 : La sortie non masquée de caractères peut être préférée lorsque la fonction restreinte est utilisée, par exemple, dans l’intimité de la maison de l’utilisateur. Une mise en garde soulignant les préoccupations relatives à la protection de la vie privée pourrait être appropriée pour s’assurer que l’utilisateur a fait un choix éclairé.

Liste des tableaux

406 Raccordements standard

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

406.1 Généralités

Lorsque des connexions de données utilisées pour l’entrée et la sortie sont fournies, au moins un de chaque type de connexion doit être conforme aux formats standard de l’industrie librement accessibles.

8.1.2 Raccordements standard

Lorsque les TIC fournissent des points de raccordement de dispositif d’entrée ou de sortie à l’utilisateur, elle comprend au moins un raccordement d’entrée ou de sortie conforme à un format standard de l’industrie librement accessible, directement ou au moyen d’adaptateurs offerts sur le marché.

REMARQUE 1 : L’exigence de raccordements standard vise à garantir la compatibilité avec les technologies d’assistance.

REMARQUE 2 : Le terme raccordement s’applique à la fois aux raccordements matériels et sans fil.

REMARQUE 3 : Les raccordements USB et Bluetooth sont des exemples de formats standard de l’industrie librement accessibles.

Reformulation stylistique

Mise à jour explicative

8.1.2 Raccordements standard

Lorsque les TIC fournissent des points de raccordement de dispositif d’entrée ou de sortie à l’utilisateur, elle comprend au moins un raccordement d’entrée ou de sortie conforme à un format standard de l’industrie librement accessible, directement ou au moyen d’adaptateurs offerts sur le marché.

REMARQUE 1 : L’exigence de raccordements standard vise à garantir la compatibilité avec les technologies d’assistance.

REMARQUE 2 : Le terme raccordement s’applique à la fois aux raccordements matériels et sans fil.

REMARQUE 3 : Les raccordements USB et Bluetooth sont des exemples de formats standard de l’industrie librement accessibles.

8.1.2 Raccordements standard

Lorsque les TIC fournissent des points de raccordement de dispositif d’entrée ou de sortie à l’utilisateur, elle comprend au moins un raccordement d’entrée ou de sortie conforme à un format standard de l’industrie librement accessible, directement ou au moyen d’adaptateurs offerts sur le marché.

REMARQUE 1 : L’exigence de raccordements standard vise à garantir la compatibilité avec les technologies d’assistance.

REMARQUE 2 : Le terme raccordement s’applique à la fois aux raccordements matériels et sans fil.

REMARQUE 3 : Les raccordements USB et Bluetooth sont des exemples de formats standard de l’industrie librement accessibles.

8.1.2 Raccordements standard

Lorsque les TIC fournissent des points de raccordement de dispositif d’entrée ou de sortie à l’utilisateur, elle comprend au moins un raccordement d’entrée ou de sortie conforme à un format standard de l’industrie librement accessible, directement ou au moyen d’adaptateurs offerts sur le marché.

REMARQUE 1 : L’exigence de raccordements standard vise à garantir la compatibilité avec les technologies d’assistance.

REMARQUE 2 : Le terme raccordement s’applique à la fois aux raccordements matériels et sans fil.

REMARQUE 3 : Les raccordements USB et Bluetooth sont des exemples de formats standard de l’industrie librement accessibles.

Liste des tableaux

407 Pièces manœuvrables

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

407.3.1 Perceptibles de manière tactile

Les commandes d’entrée doivent être manœuvrables et perceptibles de manière tactile sans activation.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

Reformulation stylistique

Mise à jour explicative

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

407.3.1 Perceptibles de manière tactile

Les commandes d’entrée doivent être manœuvrables et perceptibles de manière tactile sans activation.

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple

Reformulation stylistique

Mise à jour explicative

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple

Mise à jour explicative

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple

407.3.2 Touches alphabétiques

Lorsqu’elles sont fournies, les touches alphabétiques individuelles doivent être disposées selon le clavier QWERTY et les touches « F » et « J » doivent pouvoir se distinguer de manière tactile des autres touches.5

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

Reformulation stylistique

Mise à jour explicative

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

5.5.2 Perceptibilité des pièces manœuvrables

Lorsque les TIC sont dotées de pièces manœuvrables, elles doivent offrir un moyen de percevoir chaque pièce manœuvrable sans recourir à la vision et sans effectuer l’action associée à cette pièce manœuvrable.

REMARQUE : Cette exigence peut être satisfaite en rendant les pièces manœuvrables perceptibles au toucher.

407.3.3 Touches numériques

Lorsqu’elles sont fournies, les touches numériques doivent être disposées selon le format du pavé numérique à 12 touches en ordre ascendant ou descendant. La touche du numéro cinq doit pouvoir se distinguer de manière tactile des autres touches. Lorsque les TIC fournissent un clavier avec superposition des touches alphabétiques sur les touches numériques, les liens entre les lettres et les chiffres doivent être conformes à la Recommandation E.161 de l’UIT-T (incorporée par renvoi, voir l’article 702.7.1).6

8.4.1 Touches numériques

Lorsqu’elles sont fournies, les touches numériques formant un pavé rectangulaire doivent permettre de distinguer le numéro cinq de manière tactile des autres touches du pavé numérique.

REMARQUE : La Recommandation E.161 de l’UIT-T décrit la disposition du clavier du téléphone à 12 touches et fournit des détails supplémentaires sur la forme des marqueurs tactiles.

Reformulation stylistique

Mise à jour explicative

8.4.1 Touches numériques

Lorsqu’elles sont fournies, les touches numériques formant un pavé rectangulaire doivent permettre de distinguer le numéro cinq de manière tactile des autres touches du pavé numérique.

REMARQUE : La Recommandation E.161 de l’UIT-T décrit la disposition du clavier du téléphone à 12 touches et fournit des détails supplémentaires sur la forme des marqueurs tactiles.

8.4.1 Touches numériques

Lorsqu’elles sont fournies, les touches numériques formant un pavé rectangulaire doivent permettre de distinguer le numéro cinq de manière tactile des autres touches du pavé numérique.

REMARQUE : La Recommandation E.161 de l’UIT-T décrit la disposition du clavier du téléphone à 12 touches et fournit des détails supplémentaires sur la forme des marqueurs tactiles.

8.4.1 Touches numériques

Lorsqu’elles sont fournies, les touches numériques formant un pavé rectangulaire doivent permettre de distinguer le numéro cinq de manière tactile des autres touches du pavé numérique.

REMARQUE : La Recommandation E.161 de l’UIT-T décrit la disposition du clavier du téléphone à 12 touches et fournit des détails supplémentaires sur la forme des marqueurs tactiles.

407.4 Répétition des touches

Lorsqu’un clavier doté d’une fonction de répétition des touches est fourni, le délai de répétition des touches doit être établi ou réglé à au moins 2 secondes.

5.7 Répétition des touches

Lorsque des TIC avec fonction de répétition des touches sont fournies et que la fonction de répétition des touches ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. b. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.
Reformulation stylistique

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.
Reformulation stylistique

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.

407.6 Fonctionnement

Au moins un mode de fonctionnement doit être manœuvrable d’une seule main et ne doit pas nécessiter un serrage, un pincement ou une torsion du poignet. La force requise pour activer les pièces manœuvrables doit être au maximum de 5 livres (22,2 N).

5.5.1 Moyens de fonctionnement

Lorsque les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

Reformulation stylistique

Mise à jour explicative

5.5.1 Moyens de fonctionnement

Lorsque les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

5.5.1 Moyens de fonctionnement

Lorsque les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

5.5.1 Moyens de fonctionnement

Lorsque les TIC sont dotées de pièces manœuvrables qui nécessitent un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

407.6 Fonctionnement

Au moins un mode de fonctionnement doit être manœuvrable d’une seule main et ne doit pas nécessiter un serrage, un pincement ou une torsion du poignet. La force requise pour activer les pièces manœuvrables doit être au maximum de 5 livres (22,2 N).

8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

Reformulation stylistique

Mise à jour explicative

8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

8.4.2.1 Moyens de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite un serrage, un pincement ou une torsion du poignet pour fonctionner, un autre moyen de fonctionnement qui n’exige pas de telles actions doit être fourni.

407.6 Fonctionnement

Au moins un mode de fonctionnement doit être manœuvrable d’une seule main et ne doit pas nécessiter un serrage, un pincement ou une torsion du poignet. La force requise pour activer les pièces manœuvrables doit être au maximum de 5 livres (22,2 N).

8.4.2.2 Force de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite une force supérieure à 22,2 N pour fonctionner, un autre moyen de fonctionnement nécessitant une force inférieure à 22,2 N doit être prévu.

Reformulation stylistique

Mise à jour explicative

8.4.2.2 Force de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite une force supérieure à 22,2 N pour fonctionner, un autre moyen de fonctionnement nécessitant une force inférieure à 22,2 N doit être prévu.

8.4.2.2 Force de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite une force supérieure à 22,2 N pour fonctionner, un autre moyen de fonctionnement nécessitant une force inférieure à 22,2 N doit être prévu.

REMARQUE : ISO 21542:2011 : Building Construction - Accessibility and Usability of the Built Environment recommande une valeur comprise entre 2,5 et 5 newtons.

Mise à jour explicative

8.4.2.2 Force de fonctionnement des pièces mécaniques

Lorsqu’une commande nécessite une force supérieure à 22,2 N pour fonctionner, un autre moyen de fonctionnement nécessitant une force inférieure à 22,2 N doit être prévu.

REMARQUE : ISO 21542:2011 [i.34]: Building Construction - Accessibility and Usability of the Built Environment recommande une valeur comprise entre 2,5 et 5 newtons.

407.7 Billets, cartes tarifaires et clés

Lorsque des billets, des cartes tarifaires ou des clés sont fournis, ils doivent avoir une orientation qui peut se distinguer de manière tactile, si l’orientation est importante pour une utilisation ultérieure du billet, de la carte tarifaire ou de la clé.

8.4.3 Clés, billets et cartes tarifaires

Lorsque les TIC fournissent des clés, des billets ou des cartes tarifaires, et que leur orientation est importante pour une utilisation ultérieure, elles doivent avoir une orientation qui est perceptible au toucher.

REMARQUE : La norme ETS 300 767 définit les indications tactiles appropriées pour les cartes plastiques.

Reformulation stylistique

Mise à jour explicative

8.4.3 Clés, billets et cartes tarifaires

Lorsque les TIC fournissent des clés, des billets ou des cartes tarifaires, et que leur orientation est importante pour une utilisation ultérieure, elles doivent avoir une orientation qui est perceptible au toucher.

REMARQUE : La norme ETS 300 767 de l’ETSI définit les indications tactiles appropriées pour les cartes plastiques.

Mise à jour explicative

8.4.3 Clés, billets et cartes tarifaires

Lorsque les TIC fournissent des clés, des billets ou des cartes tarifaires, et que leur orientation est importante pour une utilisation ultérieure, elles doivent avoir une orientation qui est perceptible au toucher.

REMARQUE : La norme ETS 300 767 de l’ETSI définit les indications tactiles appropriées pour les cartes plastiques.

8.4.3 Clés, billets et cartes tarifaires

Lorsque les TIC fournissent des clés, des billets ou des cartes tarifaires, et que leur orientation est importante pour une utilisation ultérieure, elles doivent avoir une orientation qui est perceptible au toucher.

REMARQUE : La norme ETS 300 767 [i.6] de l’ETSI définit les indications tactiles appropriées pour les cartes plastiques.

407.8.1.1 Plan vertical pour portée latérale

Lorsqu’une portée latérale est fournie, le plan de référence vertical doit avoir une longueur minimale de 1 220 mm (48 po).

8.3.2.2 Surface de plancher dégagé et espace au sol

Lorsque l’espace opérationnel fait partie intégrante des TIC, la surface de plancher dégagée devrait avoir les dimensions minimales suivantes.

Un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

Reformulation stylistique

Mise à jour explicative

8.3.2.2 Surface de plancher dégagé et espace au sol

Lorsque l’espace opérationnel fait partie intégrante des TIC, la surface de plancher dégagée devrait avoir les dimensions minimales suivantes.

Un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

8.3.4.2 Surface de plancher dégagé et espace au sol

Lorsque des TIC fixes intègrent un espace opérationnel, elles doivent prévoir une surface de plancher dégagée qui a les dimensions minimales suivantes. Un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.2 Surface de plancher dégagé et espace au sol

Lorsque des TIC fixes intègrent un espace opérationnel, elles doivent prévoir une surface de plancher dégagée qui a les dimensions minimales suivantes. Un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

407.8.1.2 Plan vertical pour portée avant

Lorsqu’une portée avant est fournie, le plan de référence vertical doit avoir une longueur minimale de 760 mm (30 po).

8.3.2.2 Surface de plancher dégagé et espace au sol

Lorsque l’espace opérationnel fait partie intégrante des TIC, la surface de plancher dégagée devrait avoir les dimensions minimales suivantes : un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

Reformulation stylistique

Mise à jour explicative

8.3.2.2 Surface de plancher dégagé et espace au sol

Lorsque l’espace opérationnel fait partie intégrante des TIC, la surface de plancher dégagée devrait avoir les dimensions minimales suivantes : un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

8.3.4.2 Surface de plancher dégagé et espace au sol

Lorsque des TIC fixes intègrent un espace opérationnel, elles doivent prévoir une surface de plancher dégagée qui a les dimensions minimales suivantes : un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.2 Surface de plancher dégagé et espace au sol

Lorsque des TIC fixes intègrent un espace opérationnel, elles doivent prévoir une surface de plancher dégagée qui a les dimensions minimales suivantes : un espace opérationnel des TIC de 760 mm (30 po) par 1 220 mm (48 po).

407.8.2.1 Portée latérale libre

Lorsque la pièce manœuvrable est située à 255 mm (10 po) ou moins au-delà du plan de référence vertical, la pièce manœuvrable doit avoir une hauteur maximale de 1 220 mm (48 po) et une hauteur minimale 380 mm (15 po) au-dessus du plancher.

8.3.3.2.1 Hauteur maximum de la portée latérale libre

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle, et que la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC qui est inférieur à 255 mm (10 po), la hauteur maximum de la portée latérale aux commandes essentielles devrait être inférieure ou égale à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.2.1 Hauteur maximum de la portée latérale libre

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle, et que la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC qui est inférieur à 255 mm (10 po), la hauteur maximum de la portée latérale aux commandes essentielles devrait être inférieure ou égale à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

8.3.3.1 Hauteur maximum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes et qui est inférieur à 255 mm (10 po), la hauteur maximum de la portée latérale d’au moins un de chaque type de pièces manœuvrables devrait être inférieure ou égale à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1 Hauteur maximum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes et qui est inférieur à 255 mm (10 po), la hauteur maximum de la portée latérale d’au moins un de chaque type de pièces manœuvrables devrait être inférieure ou égale à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

407.8.2.1 Portée latérale libre

Lorsque la pièce manœuvrable est située à 255 mm (10 po) ou moins au-delà du plan de référence vertical, la pièce manœuvrable doit avoir une hauteur maximale de 1 220 mm (48 po) et une hauteur minimale 380 mm (15 po) au-dessus du plancher.

8.3.3.2.2 Hauteur minimum de la portée latérale libre

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle, et que la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC qui est inférieur à 255 mm (10 po), la hauteur minimum de la portée latérale aux commandes essentielles devrait être inférieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.2.2 Hauteur minimum de la portée latérale libre

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle, et que la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC qui est inférieur à 255 mm (10 po), la hauteur minimum de la portée latérale aux commandes essentielles devrait être inférieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès.

8.3.3.2 Hauteur minimum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes qui est inférieur à 255 mm (10 po), la hauteur minimum de la portée latérale à au moins un de chaque type de pièces manœuvrables devrait être inférieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

8.3.3.2 Hauteur minimum de la portée latérale libre

Lorsque la portée latérale est libre ou obstruée par un élément faisant partie intégrante des TIC fixes et qui est inférieur à 255 mm (10 po), la hauteur minimum de la portée latérale à au moins un de chaque type de pièces manœuvrables devrait être inférieure ou égale à 380 mm (15 po) au-dessus du plancher de l’espace d’accès.

407.8.2.2 Portée latérale obstruée

Lorsque la pièce manœuvrable est située à plus de 255 mm (10 po), mais à moins de 610 mm (24 po), au-delà du plan de référence vertical, la pièce manœuvrable doit avoir une hauteur maximale de 1 170 mm (46 po) et une hauteur minimale de 380 mm (15 po) au-dessus du plancher. La pièce manœuvrable ne doit pas se trouver à plus de 610 mm (24 po) au-delà du plan de référence vertical.

8.3.3.2.3.1 Portée latérale obstruée (≤ 255 mm) (< 10 po)

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle et présente un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est inférieure ou égale à 255 mm (10 po), la hauteur maximum de la portée latérale aux commandes essentielles ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.2.3.1 Portée latérale obstruée (≤ 255 mm) (< 10 po)

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle et présente un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est inférieure ou égale à 255 mm (10 po), la hauteur maximum de la portée latérale aux commandes essentielles ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

8.3.3.3.1 Portée latérale obstruée (≤ 255 mm) (< 10 po)

Lorsque les TIC fixes présentent un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est inférieure ou égale à 255 mm (10 po), la hauteur maximum de la portée latérale à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.3.1 Portée latérale obstruée (≤ 255 mm) (< 10 po)

Lorsque les TIC fixes présentent un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est inférieure ou égale à 255 mm (10 po), la hauteur maximum de la portée latérale à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du plancher de l’espace d’accès.

407.8.2.2 Portée latérale obstruée

Lorsque la pièce manœuvrable est située à plus de 255 mm (10 po), mais à moins de 610 mm (24 po), au-delà du plan de référence vertical, la pièce manœuvrable doit avoir une hauteur maximale de 1 170 mm (46 po) et une hauteur minimale de 380 mm (15 po) au-dessus du plancher. La pièce manœuvrable ne doit pas se trouver à plus de 610 mm (24 po) au-delà du plan de référence vertical.

8.3.3.2.3.2 Portée latérale obstruée (≤ 610 mm) (< 24 po)

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle et présente un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est supérieure à 255 mm (10 po) et inférieure à 610 mm (24 po), la hauteur maximum de la portée latérale aux commandes essentielles ne doit pas être supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.2.3.2 Portée latérale obstruée (≤ 610 mm) (< 24 po)

Lorsque l’espace d’accès fait partie intégrante des TIC, permet une approche parallèle et présente un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est supérieure à 255 mm (10 po) avec une profondeur maximale de 610 mm (24 po), la hauteur maximum de la portée latérale aux commandes essentielles ne doit pas être supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès.

Reformulation stylistique

8.3.3.3.2 Portée latérale obstruée (≤ 610 mm) (< 24 po)

Lorsque les TIC fixes présentent un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est supérieure à 255 mm (10 po) et inférieure à 610 mm (24 po), la hauteur maximum de la portée latérale à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

8.3.3.3.2 Portée latérale obstruée (≤ 610 mm) (< 24 po)

Lorsque les TIC fixes présentent un obstacle qui fait partie intégrante des TIC, la hauteur de l’obstacle doit être inférieure à 865 mm (34 po). Lorsque la profondeur de l’obstruction est supérieure à 255 mm (10 po) et inférieure à 610 mm (24 po), la hauteur maximum de la portée latérale à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 170 mm (46 po) au-dessus du plancher de l’espace d’accès.

407.8.3 Portée avant

Les pièces manœuvrables des TIC dotées d’une portée avant doivent être conformes à la clause 407.8.3.1 ou 407.8.3.2. Le plan de référence vertical doit être centré et croiser la pièce manœuvrable. Lorsqu’une portée avant permet d’atteindre au-dessus d’une partie des TIC, celle-ci doit être au maximum d’une hauteur de 865 mm (34 po).

8.3.3.1.1 Hauteur maximum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.1 Hauteur maximum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

8.3.2.1 Hauteur maximum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.2.1 Hauteur maximum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

407.8.3 Portée avant

Les pièces manœuvrables des TIC dotées d’une portée avant doivent être conformes à la clause 407.8.3.1 ou 407.8.3.2. Le plan de référence vertical doit être centré et croiser la pièce manœuvrable. Lorsqu’une portée avant permet d’atteindre au-dessus d’une partie des TIC, celle-ci doit être au maximum d’une hauteur de 865 mm (34 po).

8.3.3.1.2 Hauteur minimum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à moins de 380 mm (15 po) du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.2 Hauteur minimum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à moins de 380 mm (15 po) du plancher de l’espace d’accès.

8.3.2.2 Hauteur minimum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à moins de 380 mm (15 po) du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.2.2 Hauteur minimum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à moins de 380 mm (15 po) du plancher de l’espace d’accès.

407.8.3 Portée avant

Les pièces manœuvrables des TIC dotées d’une portée avant doivent être conformes à la clause 407.8.3.1 ou 407.8.3.2. Le plan de référence vertical doit être centré et croiser la pièce manœuvrable. Lorsqu’une portée avant permet d’atteindre au-dessus d’une partie des TIC, celle-ci doit être au maximum d’une hauteur de 865 mm (34 po).

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

407.8.3 Portée avant

Les pièces manœuvrables des TIC dotées d’une portée avant doivent être conformes à la clause 407.8.3.1 ou 407.8.3.2. Le plan de référence vertical doit être centré et croiser la pièce manœuvrable. Lorsqu’une portée avant permet d’atteindre au-dessus d’une partie des TIC, celle-ci doit être au maximum d’une hauteur de 865 mm (34 po).

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

407.8.3.1 Portée avant libre

Lorsque la pièce manœuvrable est située au bord avant de la saillie maximale dans la longueur du plan de référence vertical des TIC, la pièce manœuvrable doit avoir une hauteur maximale de 1 220 mm (48 po) et une hauteur minimale de 380 mm (15 po) pouces (380 mm) au-dessus du plancher.

8.3.3.1.1 Hauteur maximum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.1.1 Hauteur maximum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

8.3.2.1 Hauteur maximum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.2.1 Hauteur maximum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à plus de 1 220 mm (48 po) du plancher de l’espace d’accès.

407.8.3.1 Portée avant libre

Lorsque la pièce manœuvrable est située au bord avant de la saillie maximale dans la longueur du plan de référence vertical des TIC, la pièce manœuvrable doit avoir une hauteur maximale de 1 220 mm (48 po) et une hauteur minimale de 380 mm (15 po) au-dessus du plancher.

8.3.3.1.2 Hauteur minimum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à moins de 380 mm (15 po) du plancher de l’espace d’accès.

Reformulation stylistique

Mise à jour explicative

8.3.3.1.2 Hauteur minimum de la portée avant libre

Lorsque l’espace d’accès fait partie intégrante des TIC et que la portée avant est libre, les commandes essentielles ne doivent pas être situées à moins de 380 mm (15 po) du plancher de l’espace d’accès.

8.3.2.2 Hauteur minimum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à moins de 380 mm (15 po) du plancher de l’espace d’accès.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.2.2 Hauteur minimum de la portée avant libre

Lorsqu’aucune pièce des TIC fixes n’obstrue la portée avant, au moins un de chaque type de pièces manœuvrables ne doit pas être situé à moins de 380 mm (15 po) du plancher de l’espace d’accès.

407.8.3.2 Portée avant obstruée

Lorsque la pièce manœuvrable est située au-delà du bord avant de la saillie maximale dans la longueur du plan de référence vertical des TIC, la pièce manœuvrable doit être conforme à la clause 407.8.3.2. La portée avant maximale autorisée pour une pièce manœuvrable doit être de 635 mm (25 po).

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

407.8.3.2 Portée avant obstruée

Lorsque la pièce manœuvrable est située au-delà du bord avant de la saillie maximale dans la longueur du plan de référence vertical des TIC, la pièce manœuvrable doit être conforme à la clause 407.8.3.2. La portée avant maximale autorisée pour une pièce manœuvrable doit être de 635 mm (25 po).

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

407.8.3.2.1 Hauteur de la pièce manœuvrable pour les TIC avec portée avant obstruée

La hauteur de la pièce manœuvrable doit être conforme au tableau 407.8.3.2.1.

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque l’espace d’accès et l’obstruction font partie intégrante des TIC et que cette dernière est inférieure à 510 mm (20 po), la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.2 Portée avant obstruée (< 510 mm) (< 20 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et étant inférieur à 510 mm (20 pouces), la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 220 mm (48 po) au-dessus du point de contact au sol des TIC.

407.8.3.2.1 Hauteur de la pièce manœuvrable pour les TIC avec portée avant obstruée

La hauteur de la pièce manœuvrable doit être conforme au tableau 407.8.3.2.1.

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.3.1.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque l’espace d’accès fait partie intégrante des TIC et que l’obstruction fait partie intégrante des TIC et qu’elle est supérieure à 510 mm (20 po) et inférieure à 635 mm (25 po) au plus, la portée avant aux commandes essentielles ne devrait pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.3.3 Portée avant obstruée (< 635 mm) (< 25 po)

Lorsque les TIC fixes présentent un obstacle faisant partie intégrante des TIC et qu’il n’est pas inférieur à 510 mm (20 pouces) mais est inférieur à 635 mm (25 pouces) au plus, la portée avant à au moins un de chaque type de pièces manœuvrables ne doit pas être supérieure à 1 120 mm (44 po) au-dessus du point de contact au sol des TIC.

407.8.3.2.2 Espace pour les genoux et les pieds sous les TIC avec portée avant obstruée

L’espace pour les genoux et les pieds sous les TIC doit avoir une hauteur minimum de 685 mm (27 po), une profondeur maximum de 635 mm (25 po) et doit être dégagé de tout obstacle.

EXCEPTIONS :

  1. L’espace pour les pieds doit fournir une hauteur dégagée de 230 mm (9 po) au-dessus du plancher et une profondeur maximale dégagée de 150 mm (6 po) du plan de référence vertical vers le bord avant des TIC.
  2. Avec une profondeur maximale de 150 mm (6 po) du plan de référence vertical au bord avant des TIC, l’espace entre le minimum de 230 mm (9 po) et de 685 mm (27 po) au-dessus du plancher doit pouvoir être réduit à un taux de 25 mm (1 po) de profondeur pour chaque 150 mm (6 po) de hauteur.7

8.3.2.4 Largeur libre pour les genoux et les pieds

Lorsque l’espace sous un obstacle faisant partie intégrante des TIC fait partie de l’espace d’accès, la largeur libre devrait être d’au moins 760 mm (30 po).

Reformulation stylistique

Mise à jour explicative

8.3.2.4 Largeur libre pour les genoux et les pieds

Lorsque l’espace sous un obstacle faisant partie intégrante des TIC fait partie de l’espace d’accès, la largeur libre devrait être d’au moins 760 mm (30 po).

8.3.2.4 Largeur libre pour les genoux et les pieds

Lorsque l’espace sous un obstacle faisant partie intégrante des TIC fixes fait partie de l’espace d’accès, la largeur libre doit être d’au moins 760 mm (30 po).

Reformulation stylistique

Changement fonctionnel

8.3.2.4 Largeur libre pour les genoux et les pieds

Lorsque l’espace sous un obstacle faisant partie intégrante des TIC fixes fait partie de l’espace d’accès, la largeur libre doit être d’au moins 760 mm (30 po).

407.8.3.2.2 Espace pour les genoux et les pieds sous les TIC avec portée avant obstruée

L’espace pour les genoux et les pieds sous les TIC doit avoir une hauteur minimum de 685 mm (27 po), une profondeur maximum de 635 mm (25 po), une largeur de 760 mm (30 po) et doit être dégagé de tout obstacle.

EXCEPTIONS :

  1. L’espace pour les pieds doit fournir une hauteur dégagée de 230 mm (9 po) au-dessus du plancher et une profondeur maximale dégagée de 150 mm (6 po) du plan de référence vertical vers le bord avant des TIC.
  2. Avec une profondeur maximale de 150 mm (6 po) du plan de référence vertical au bord avant des TIC, l’espace entre le minimum de 230 mm (9 po) et de 685 mm (27 po) au-dessus du plancher doit pouvoir être réduit à un taux de 25 mm (1 po) de profondeur pour chaque 150 mm (6 po) de hauteur.7b

8.3.2.5 Espace libre pour les pieds

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle d’au moins 230 mm (9 po) au-dessus du plancher est considéré comme un espace libre pour les pieds et il devrait :

  1. avoir une largeur d’au plus 635 mm (25 po) sous tout l’obstacle;
  2. fournir un espace d’au moins 430 mm (17 po) de profondeur et 230 mm (9 po) au-dessus du plancher sous l’obstacle;
  3. être à une distance d’au plus 150 mm (6 po) de toute obstruction à 230 mm (9 po) au-dessus du plancher.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.5 Espace libre pour les pieds

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle d’au moins 230 mm (9 po) au-dessus du plancher est considéré comme un espace libre pour les pieds et il devrait :

  1. avoir une largeur d’au plus 635 mm (25 po) sous tout l’obstacle;
  2. procurer un espace d’au moins 430 mm (17 po) de profondeur et 230 mm (9 po) au-dessus du plancher sous l’obstacle;
  3. être à une distance d’au plus 150 mm (6 po) de toute obstruction à 230 mm (9 po) au-dessus du plancher.

8.3.2.5 Espace libre pour les pieds

Lorsqu’un obstacle fait partie intégrante des TIC fixes, un espace sous l’obstacle d’au moins 230 mm (9 po) au-dessus du plancher est considéré comme un espace libre pour les pieds et il doit :

  1. avoir une largeur d’au plus 635 mm (25 po) sous tout l’obstacle;
  2. procurer un espace d’au moins 430 mm (17 po) de profondeur et 230 mm (9 po) au-dessus du plancher sous l’obstacle;
  3. être à une distance d’au plus 150 mm (6 po) de toute obstruction à 230 mm (9 po) au-dessus du plancher.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

8.3.2.5 Espace libre pour les pieds

Lorsqu’un obstacle fait partie intégrante des TIC fixes, un espace sous l’obstacle d’au moins 230 mm (9 po) au-dessus du plancher est considéré comme un espace libre pour les pieds et il doit :

  1. avoir une largeur d’au plus 635 mm (25 po) sous tout l’obstacle;
  2. procurer un espace d’au moins 430 mm (17 po) de profondeur et 230 mm (9 po) au-dessus du plancher sous l’obstacle;
  3. être à une distance d’au plus 150 mm (6 po) de toute obstruction à 230 mm (9 po) au-dessus du plancher.

407.8.3.2.2 Espace pour les genoux et les pieds sous les TIC avec portée avant obstruée

L’espace pour les genoux et les pieds sous les TIC doit avoir une hauteur minimum de 685 mm (27 po), une profondeur maximum de 635 mm (25 po) et doit être dégagé de tout obstacle.

EXCEPTIONS :

  1. L’espace pour les pieds doit fournir une hauteur dégagée de 230 mm (9 po) au-dessus du plancher et une profondeur maximale dégagée de 150 mm (6 po) du plan de référence vertical vers le bord avant des TIC.
  2. Avec une profondeur maximale de 150 mm (6 po) du plan de référence vertical au bord avant des TIC, l’espace entre le minimum de 230 mm (9 po) et de 685 mm (27 po) au-dessus du plancher doit pouvoir être réduit à un taux de 25 mm (1 po) de profondeur pour chaque 150 mm (6 po) de hauteur.8

8.3.2.6 Espace libre pour les genoux

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (27 po) au-dessus du plancher est considéré comme un espace libre pour les genoux et il devrait :

  1. être à une distance pas plus de 635 mm (25 po) sous toute obstruction à 230 mm (9 po) de hauteur au-dessus du plancher;
  2. avoir une largeur d’au moins 280 mm (11 po) sous l’obstacle et une hauteur de 230 mm (9 po) au-dessus du plancher;
  3. avoir une largeur d’au moins 205 mm (8 po) sous l’obstacle et une hauteur de 685 mm (27 po) au-dessus du plancher;

se situer entre 230 mm (9 po) et 685 mm (27 po) au-dessus du plancher pour pouvoir être réduit à une profondeur de 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.6 Espace libre pour les genoux

Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (27 po) au-dessus du plancher est considéré comme un espace libre pour les genoux et il devrait :

  1. être à une distance pas plus de 635 mm (25 po) sous toute obstruction à 230 mm (9 po) de hauteur au-dessus du plancher;
  2. avoir une largeur d’au moins 280 mm (11 po) sous l’obstacle et une hauteur de 230 mm (9 po) au-dessus du plancher;
  3. avoir une largeur d’au moins 205 mm (8 po) sous l’obstacle et une hauteur de 685 mm (27 po) au-dessus du plancher;
  4. pouvoir être réduit à une profondeur de 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.
Reformulation stylistique

8.3.2.6 Espace libre pour les genoux

Lorsqu’un obstacle fait partie intégrante des TIC fixes, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po)9 au-dessus du plancher est considéré comme un espace libre pour les genoux et il doit :

  1. être à une distance pas plus de 635 mm (25 po) sous toute obstruction à 230 mm (9 po) de hauteur au-dessus du plancher;
  2. avoir une largeur d’au moins 280 mm (11 po) sous l’obstacle et une hauteur de 230 mm (9 po) au-dessus du plancher;
  3. avoir une largeur d’au moins 205 mm (8 po) sous l’obstacle et une hauteur de 685 mm (27 po) au-dessus du plancher;
  4. pouvoir être réduit à une profondeur de 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.2.6 Espace libre pour les genoux

Lorsqu’un obstacle fait partie intégrante des TIC fixes, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po)10 au-dessus du plancher est considéré comme un espace libre pour les genoux et il doit :

  1. être à une distance pas plus de 635 mm (25 po) sous toute obstruction à 230 mm (9 po) de hauteur au-dessus du plancher;
  2. avoir une largeur d’au moins 280 mm (11 po) sous l’obstacle et une hauteur de 230 mm (9 po) au-dessus du plancher;
  3. avoir une largeur d’au moins 205 mm (8 po) sous l’obstacle et une hauteur de 685 mm (27 po) au-dessus du plancher;
  4. pouvoir être réduit à une profondeur de 25 mm (1 po) pour chaque 150 mm (6 po) de hauteur.

Liste des tableaux

408 Écran d’affichage

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

408.2 Visibilité

Lorsque des TIC fixes sont dotées d’un ou de plusieurs écrans d’affichage, au moins un de chaque type d’écran d’affichage doit être visible d’un point situé à 1 015 mm (40 po) au-dessus de l’espace au plancher à partir d’où l’écran d’affichage est visionné.

8.3.4 Visibilité

Lorsque l’espace opérationnel fait partie intégrante des TIC et qu’un écran d’affichage est fourni, l’information à l’écran doit être lisible à partir d’un point situé à 1 015 mm (40 po) au-dessus du centre du plancher de l’espace opérationnel (à la clause 8.3.2.2).

REMARQUE : Cette disposition vise à ce que l’information à l’écran soit lisible par des utilisateurs ayant une vision normale et des compétences linguistiques appropriées, lorsqu’ils sont assis dans un fauteuil roulant.

Reformulation stylistique

Mise à jour explicative

8.3.4 Visibilité

Lorsque l’espace opérationnel fait partie intégrante des TIC et qu’un écran d’affichage est fourni, l’information à l’écran doit être lisible à partir d’un point situé à 1 015 mm (40 po) au-dessus du centre du plancher de l’espace opérationnel (à la clause 8.3.2.2).

REMARQUE : Cette disposition vise à ce que l’information à l’écran soit lisible par des utilisateurs ayant une vision normale et des compétences linguistiques appropriées, lorsqu’ils sont assis dans un fauteuil roulant.

8.3.5 Visibilité

Lorsque les TIC fixes fournissent un ou plusieurs écrans d’affichage, au moins un de chaque type d’écran d'affichage doit être positionné de telle sorte que les renseignements à l'écran soient lisibles depuis un point situé à 1 015 mm (40 pouces) au-dessus du centre du plancher de l’espace opérationnel.

REMARQUE : Cette exigence vise à ce que l’information à l’écran soit lisible par des utilisateurs ayant une vision normale et des compétences linguistiques appropriées, lorsqu’ils sont assis dans un fauteuil roulant.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.5 Visibilité

Lorsque les TIC fixes fournissent un ou plusieurs écrans d’affichage, au moins un de chaque type d’écran d'affichage doit être positionné de telle sorte que les renseignements à l'écran soient lisibles depuis un point situé à 1 015 mm (40 pouces) au-dessus du centre du plancher de l’espace opérationnel.

REMARQUE : Cette exigence vise à ce que l’information à l’écran soit lisible par des utilisateurs ayant une vision normale et des compétences linguistiques appropriées, lorsqu’ils sont assis dans un fauteuil roulant.

Liste des tableaux

409 Indicateurs d’état

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

409.1 Généralités

Lorsqu’ils sont fournis, les indicateurs d’état doivent être perceptibles visuellement ainsi que de manière tactile ou auditive.

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

Reformulation stylistique

Mise à jour explicative

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

Mise à jour explicative

5.6.1 État tactile ou auditif

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de cette commande se présente visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement dans lequel l’état de la commande peut être déterminé de manière tactile ou auditive sans qu’il soit nécessaire d’actionner la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. La touche de volume d’un téléphone public, qui peut être réglé à un volume normal, fort ou très fort, en est un autre exemple.

409.1 Généralités

Lorsqu’ils sont fournis, les indicateurs d’état doivent être perceptibles visuellement ainsi que de manière tactile ou auditive.

5.6.2 État visuel

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que la commande ne se présente pas visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement permettant de déterminer visuellement l’état de la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. Un indicateur visuel d’état sur un clavier est un exemple de détermination de l’état d’une commande.

Reformulation stylistique

Mise à jour explicative

5.6.2 État visuel

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que la commande ne se présente pas visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement permettant de déterminer visuellement l’état de la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. Un indicateur visuel d’état sur un clavier est un exemple de détermination de l’état d’une commande.

5.6.2 État visuel

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de la commande ne se présente pas visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement permettant de déterminer visuellement l’état de la commande.

Mise à jour explicative

5.6.2 État visuel

Lorsque les TIC sont dotées d’une commande de verrouillage ou de basculement et que l’état de la commande ne se présente pas visuellement à l’utilisateur, les TIC doivent fournir au moins un mode de fonctionnement permettant de déterminer visuellement l’état de la commande.

REMARQUE 1 : Les commandes de verrouillage ou de basculement sont celles qui ne peuvent comporter que deux ou trois états et qui conservent leur état pendant l’utilisation.

REMARQUE 2 : La touche « VERR MAJ » de la plupart des claviers est un exemple de commande de verrouillage ou de basculement. Un indicateur visuel d’état sur un clavier est un exemple de détermination de l’état d’une commande.

Liste des tableaux

410 Codage par couleurs

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

410.1 Généralités

Lorsqu’ils sont fournis, les codes de couleurs ne doivent pas être utilisés comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

8.1.3 Couleur

Lorsque les TIC sont dotées d’aspects matériels utilisant la couleur, la couleur n’est pas utilisée comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

Reformulation stylistique

8.1.3 Couleur

Lorsque les TIC sont dotées d’aspects matériels utilisant la couleur, la couleur n’est pas utilisée comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

8.1.3 Couleur

Lorsque les TIC sont dotées d’aspects matériels utilisant la couleur, la couleur n’est pas utilisée comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

8.1.3 Couleur

Lorsque les TIC sont dotées d’aspects matériels utilisant la couleur, la couleur n’est pas utilisée comme la seule façon de véhiculer de l’information, d’indiquer une action, de solliciter une réponse ou de distinguer un élément visuel.

Liste des tableaux

412 TIC avec communication vocale bidirectionnelle

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

412.2.1 Gain de volume pour les téléphones filaires

Un gain de volume conforme à la norme 47 CFR 68.317 doit être fourni sur les téléphones filaires analogiques et numériques.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

Reformulation stylistique

Mise à jour explicative

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

412.2.1 Gain de volume pour les téléphones filaires

Un gain de volume conforme à la norme 47 CFR 68.317 doit être fourni sur les téléphones filaires analogiques et numériques.11

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

412.2.2 Gain de volume pour les TIC non filaires

Une méthode d’augmentation du volume doit être fournie pour les TIC non filaires.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

8.2.1.1 Gamme de volume de la parole

Lorsque le matériel de TIC est doté d’une sortie vocale, elles doivent permettre d’ajuster le niveau de volume de la sortie vocale sur une gamme d’au moins 18 dB.

REMARQUE : Les combinés et casques d’écoute de téléphonie fixe qui satisfont aux exigences de la norme ANSI/TIA-4965 sont réputés conformes à cette exigence.

412.2.2 Gain de volume pour les TIC non filaires

Une méthode d’augmentation du volume doit être fournie pour les TIC non filaires.12

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

8.2.1.2 Réglage incrémentiel du volume

Lorsque le matériel de TIC est doté d’une sortie vocale et d’un réglage additionnel du volume, elles doivent fournir au moins un niveau intermédiaire de gain de 12 dB au-dessus du réglage de volume le plus bas.

412.3.1 Combinés sans fil

Les TIC sous forme de combinés sans fil doivent être conformes à la norme ANSI/IEEE C63.19-2011 (incorporée par renvoi, voir l’article 702.5.1).13

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

Reformulation stylistique

Mise à jour explicative

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

Mise à jour explicative

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

8.2.2.2 Dispositifs de communication sans fil

Lorsque le matériel de TIC est un dispositif de communication sans fil avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique aux technologies auditives qui répond aux exigences ES 200 381-2 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme ANSI/IEEE C63.19 sont réputées conformes aux exigences de la présente clause.

412.3.2 Combinés filaires

Les TIC sous forme de combinés filaires, y compris les combinés sans fil, doivent être conformes à la norme TIA-1083-B (incorporée par renvoi, voir l’article 702.9.1).14

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille et qui porte le symbole « T » spécifié dans la norme ETS 300 381, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1.

REMARQUE : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

Reformulation stylistique

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille et qui porte le symbole « T » spécifié dans la norme ETS 300 381 de l’ETSI, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 de l’ETSI.

REMARQUE : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 de l’ETSI et doit porter le symbole « T » spécifié dans la norme ETS 300 381 de l’ETSI.

REMARQUE 1 : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

REMARQUE 2 : Le couplage magnétique est également appelé couplage inductif pour bobine en T.

Reformulation stylistique

Mise à jour explicative

8.2.2.1 Dispositifs de téléphonie fixe

Lorsque le matériel de TIC est un dispositif de communication fixe avec sortie vocale qui est normalement tenu à l’oreille, il doit fournir un moyen de couplage magnétique qui répond aux exigences de la norme ES 200 381-1 de l’ETSI et doit porter le symbole « T » spécifié dans la norme ETS 300 381 de l’ETSI.

REMARQUE 1 : Les TIC répondant aux exigences de la norme TIA-1083-A sont réputées conformes aux exigences de la présente clause.

REMARQUE 2 : Le couplage magnétique est également appelé couplage inductif pour bobine en T.

412.4 Codage numérique de la parole

Les TIC contenues dans des réseaux IP doivent transmettre et recevoir des messages vocaux codés de façon numérique de la manière spécifiée par la Recommandation G.722.2 de l’UTI-T (incorporée par référence, voir l’article 702.7.2) ou par la norme RFC 6716 de l’IETF (incorporée par renvoi, voir l’article 702.8.1).15

6.1 Largeur de bande sonore pour la parole (recommandation informative)

Lorsque les TIC permettent la communication vocale bidirectionnelle, pour offrir une bonne qualité sonore, elles devraient pouvoir coder et décoder la communication vocale bidirectionnelle selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

REMARQUE 1 : aux fins de l’interopérabilité, la Recommandation G.722 de l’UIT-T est largement utilisée.

REMARQUE 2 : lorsqu’il y a négociation de codecs, d’autres codecs normalisés tels que la Recommandation G.722.2 de l’UIT-T sont parfois utilisés afin d’éviter le transcodage.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.1 Largeur de bande sonore pour la parole

Lorsque les TIC permettent la communication vocale bidirectionnelle, pour offrir une bonne qualité sonore, elles doivent pouvoir coder et décoder la communication vocale bidirectionnelle selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

REMARQUE 1 : aux fins de l’interopérabilité, la Recommandation G.722 de l’UIT-T est largement utilisée.

REMARQUE 2 : lorsqu’il y a négociation de codecs, d’autres codecs normalisés tels que la Recommandation G.722.2 de l’UIT-T sont parfois utilisés afin d’éviter le transcodage.

Changement fonctionnel

6.1 Largeur de bande sonore pour la parole

Lorsque les TIC permettent la communication vocale bidirectionnelle, pour offrir une bonne qualité sonore, elles doivent pouvoir coder et décoder la communication vocale bidirectionnelle selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

REMARQUE 1 : aux fins de l’interopérabilité, la Recommandation G.722 de l’UIT-T est largement utilisée.

REMARQUE 2 : lorsqu’il y a négociation de codecs, d’autres codecs normalisés tels que la Recommandation G.722.2 de l’UIT-T sont parfois utilisés afin d’éviter le transcodage.

6.1 Largeur de bande sonore pour la parole

Lorsque les TIC permettent la communication vocale bidirectionnelle, pour offrir une bonne qualité sonore, elles doivent pouvoir coder et décoder la communication vocale bidirectionnelle selon une audiofréquence dont la limite supérieure est d’au moins 7 kHz.

REMARQUE 1 : aux fins de l’interopérabilité, la Recommandation G.722 de l’UIT-T est largement utilisée.

REMARQUE 2 : lorsqu’il y a négociation de codecs, d’autres codecs normalisés tels que la Recommandation G.722.2 de l’UIT-T sont parfois utilisés afin d’éviter le transcodage.

412.5 Fonctionnalité texte en temps réel

[Réservé].16

Voir les exigences relatives au TTR dans EN 301 549 V1.1.1 (2014), chapitre 6, ci-dessous.Voir les exigences relatives au TTR dans EN 301 549 V2.1.2 (2018), chapitre 6, ci-dessous.Voir les exigences relatives au TTR dans EN 301 549 V3.1.1 (2019), chapitre 6, ci-dessous.Voir les exigences relatives au TTR dans EN 301 549 V3.2.1 (2021), chapitre 6, ci-dessous.

412.6 Identification de l’appelant

Lorsqu’elle est fournie, la fonction d’identification de l’appelant ou de télécommunications similaire doit être visible et audible.17

6.3 Identification de l’appelant

Lorsque les TIC sont dotées de la fonction d’identification de l’appelant ou sont d’une fonction de télécommunications similaire, la fonction d’identification de l’appelant ou de télécommunications similaire doit être offerte en mode textuel et dans au moins un autre mode.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.3 Identification de l’appelant

Lorsque les TIC sont dotées de la fonction d’identification de l’appelant ou sont d’une fonction de télécommunications similaire, la fonction d’identification de l’appelant ou de télécommunications similaire doit être offerte en mode textuel et dans au moins un autre mode.

6.3 Identification de l’appelant

Lorsque les TIC sont dotées de la fonction d’identification de l’appelant ou sont d’une fonction de télécommunications similaire, la fonction d’identification de l’appelant ou de télécommunications similaire doit être offerte en mode textuel

ainsi qu’être déterminable par un programme informatique, à moins que la fonction ne soit restreinte.

Changement fonctionnel

6.3 Identification de l’appelant

Lorsque les TIC sont dotées de la fonction d’identification de l’appelant ou sont d’une fonction de télécommunications similaire, la fonction d’identification de l’appelant ou de télécommunications similaire doit être offerte en mode textuel ainsi qu’être déterminable par un programme informatique, à moins que la fonction ne soit restreinte.

412.7 Communication vidéo

Lorsque les TIC sont dotées d’une fonctionnalité vidéo en temps réel, la qualité de la vidéo doit être suffisante pour prendre en charge la communication au moyen du langage des signes.18

6.5.1 Généralités (information)

La clause 6.5 (Communication vidéo) décrit les exigences fonctionnelles prenant en charge les utilisateurs qui communiquent en langage gestuel et en lecture labiale. À cette fin, une résolution de CIF (Common Intermediate Format), une vitesse de défilement d’au moins 20 images par seconde et un écart entre le son et la vidéo de 100 ms ou moins permettent d’obtenir une bonne exploitabilité.

Lorsque la résolution passe au format QCIF (Quarter Common Intermediate Format) et que la vitesse de défilement baisse à 12 images par seconde, la communication est encore possible avec certaines restrictions.

La baisse de résolution perturbe moins la perception du langage gestuel et de la lecture labiale que la baisse de la vitesse de défilement des images.

Le retard peut être un problème lié à la communication vidéo. Des valeurs d’écart inférieur à 0,4 s avec une augmentation allant jusqu’à 0,1 s sont préférables. Des valeurs d’écart supérieures à 0,8 s peuvent nuire à la conversation gestuelle. L’écart global dépend de plusieurs facteurs, dont le délai de transmission du réseau et de traitement vidéo. Voilà pourquoi il est impossible d’établir une exigence testable des valeurs minimales d’écart global.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.5.1 Généralités (information)

La clause 6.5 (Communication vidéo) décrit les exigences fonctionnelles prenant en charge les utilisateurs qui communiquent en langage gestuel et en lecture labiale. À cette fin, une résolution de CIF (Common Intermediate Format), une vitesse de défilement d’au moins 20 images par seconde et un écart entre le son et la vidéo de 100 ms ou moins permettent d’obtenir une bonne exploitabilité.

Lorsque la résolution passe au format QCIF (Quarter Common Intermediate Format) et que la vitesse de défilement baisse à 12 images par seconde, la communication est encore possible avec certaines restrictions.

La baisse de résolution perturbe moins la perception du langage gestuel et de la lecture labiale que la baisse de la vitesse de défilement des images.

Le retard peut être un problème lié à la communication vidéo. Des valeurs d’écart inférieur à 0,4 s avec une augmentation allant jusqu’à 0,1 s sont préférables. Des valeurs d’écart supérieures à 0,8 s peuvent nuire à la conversation gestuelle. L’écart global dépend de plusieurs facteurs, dont le délai de transmission du réseau et de traitement vidéo. Voilà pourquoi il est impossible d’établir une exigence testable des valeurs minimales d’écart global.

6.5.1 Généralités (information)

La clause 6.5 (Communication vidéo) décrit les exigences fonctionnelles prenant en charge les utilisateurs qui communiquent en langage gestuel et en lecture labiale. Pour ces utilisateurs, une résolution au moins QVGA (320 x 240), une vitesse de défilement d’au moins 20 images par seconde et un écart entre le son et la vidéo de 100 ms ou moins permettent d’obtenir une bonne exploitabilité.

L'augmentation de la résolution et de la vitesse de défilement des images améliore encore plus le langage des signes (en particulier l'épellation digitale) et la lecture labiale, la vitesse de défilement des images étant plus importante que la résolution.

Les écarts temporels entre l’audio et la vidéo (asynchronicité) peuvent avoir un impact important sur la lecture labiale - une vidéo en retard sur l’audio ayant un effet négatif plus important. La latence de bout en bout peut être un problème dans la communication vidéo (des signes). Des valeurs d’écart inférieur à 400 ms avec une augmentation allant jusqu’à 100 ms sont préférables. L’écart global dépend de plusieurs facteurs, dont le délai de transmission du réseau et de traitement vidéo. Voilà pourquoi il est impossible d’établir une exigence testable des valeurs minimales d’écart global. REMARQUE : La Recommandation UIT-T F.703 définit et donne les exigences relatives à la conversation totale qui a trait à l’intégration de l’audio, au TTR et à la vidéo dans une connexion d'utilisateur unique.

Changement fonctionnel

Mise à jour explicative

Reformulation stylistique

6.5.1 Généralités (information)

La clause 6.5 (Communication vidéo) décrit les exigences fonctionnelles prenant en charge les utilisateurs qui communiquent en langage gestuel et en lecture labiale. Pour ces utilisateurs, une résolution au moins QVGA (320 x 240), une vitesse de défilement d’au moins 20 images par seconde et un écart entre le son et la vidéo de 100 ms ou moins permettent d’obtenir une bonne exploitabilité.

L'augmentation de la résolution et de la vitesse de défilement des images améliore encore le langage des signes (en particulier l'épellation digitale) et la lecture labiale, la vitesse de défilement des images étant plus importante que la résolution.

Les écarts temporels entre l’audio et la vidéo (asynchronicité) peuvent avoir un impact important sur la lecture labiale - une vidéo en retard sur l’audio ayant un effet négatif plus important. La latence de bout en bout peut être un problème dans la communication vidéo (des signes). Des valeurs d’écart inférieur à 400 ms avec une augmentation allant jusqu’à 100 ms sont préférables. L’écart global dépend de plusieurs facteurs, dont le délai de transmission du réseau et de traitement vidéo. Voilà pourquoi il est impossible d’établir une exigence testable des valeurs minimales d’écart global.
REMARQUE : La Recommandation UIT-T F.703 définit et donne les exigences relatives à la conversation totale qui a trait à l’intégration de l’audio, au TTR et à la vidéo dans une connexion d'utilisateur unique.

412.7 Communication vidéo

Lorsque les TIC sont dotées d’une fonctionnalité vidéo en temps réel, la qualité de la vidéo doit être suffisante pour prendre en charge la communication au moyen du langage des signes.19

6.5.2 Résolution

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge au moins la résolution QCIF;
  2. doivent de préférence prendre en charge au moins la résolution CIF.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.5.2 Résolution

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge au moins la résolution QCIF;
  2. doivent de préférence prendre en charge au moins la résolution CIF.

6.5.2 Résolution

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge au moins la résolution QVGA;
  2. doivent de préférence prendre en charge au moins la résolution VGA.
Changement fonctionnel

6.5.2 Résolution

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge au moins la résolution QVGA;
  2. doivent de préférence prendre en charge au moins la résolution VGA.

412.7 Communication vidéo

Lorsque les TIC sont dotées d’une fonctionnalité vidéo en temps réel, la qualité de la vidéo doit être suffisante pour prendre en charge la communication au moyen du langage des signes.20

6.5.3 Vitesse de défilement des images

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge une vitesse de défilement d’au moins 12 images par seconde (IPS);
  2. doivent de préférence prendre en charge une vitesse de défilement d’au moins 20 images par seconde (IPS) avec ou sans langage gestuel dans le flux vidéo.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.5.3 Vitesse de défilement des images

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge une vitesse de défilement d’au moins 12 images par seconde (IPS);
  2. doivent de préférence prendre en charge une vitesse de défilement d’au moins 20 images par seconde (IPS) avec ou sans langage gestuel dans le flux vidéo.

6.5.3 Vitesse de défilement des images

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge une vitesse de défilement d’au moins 20 images par seconde (IPS);
  2. doivent de préférence prendre en charge une vitesse de défilement d’au moins 30 images par seconde (IPS) avec ou sans langage gestuel dans le flux vidéo.
Changement fonctionnel

6.5.3 Vitesse de défilement des images

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles :

  1. doivent prendre en charge une vitesse de défilement d’au moins 20 images par seconde (IPS);
  2. doivent de préférence prendre en charge une vitesse de défilement d’au moins 30 images par seconde (IPS) avec ou sans langage gestuel dans le flux vidéo.
Reformulation stylistique

412.7 Communication vidéo

Lorsque les TIC sont dotées d’une fonctionnalité vidéo en temps réel, la qualité de la vidéo doit être suffisante pour prendre en charge la communication au moyen du langage des signes.21

6.5.4 Synchronisation entre le son et la vidéo

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles devraient présenter à l’utilisateur un écart temporel maximal de 100 ms entre la parole et la vidéo.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.5.4 Synchronisation entre le son et la vidéo

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles devraient présenter à l’utilisateur un écart temporel maximal de 100 ms entre la parole et la vidéo.

6.5.4 Synchronisation entre le son et la vidéo

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles doivent présenter à l’utilisateur un écart temporel maximal de 100 ms entre la parole et la vidéo. REMARQUE : Des recherches récentes montrent que si l’audio mène la vidéo, l’intelligibilité en souffre beaucoup plus que dans le cas inverse.

Changement fonctionnel

Mise à jour explicative

6.5.4 Synchronisation entre le son et la vidéo

Lorsque les TIC permettant la communication vocale bidirectionnelle comprennent une fonctionnalité vidéo en temps réel, elles doivent présenter à l’utilisateur un écart temporel maximal de 100 ms entre la parole et la vidéo. REMARQUE : Des recherches récentes montrent que si l’audio mène la vidéo, l’intelligibilité en souffre beaucoup plus que dans le cas inverse.

Liste des tableaux

413 Technologies de traitement des sous-titres codés

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

413.1.1 Décodage et affichage des sous-titres codés

Les lecteurs et les écrans doivent décoder les sous-titres et prendre en charge l’affichage des sous-titres.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

Reformulation stylistique

Mise à jour explicative

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

Changement fonctionnel

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

REMARQUE 3 : La clause 7.1.1 fait référence à la capacité du lecteur d’afficher des sous-titres. Les clauses 9.1.2.2, 10.1.2.2 et 11.1.2.2 font référence à la fourniture de sous-titres pour le contenu (la vidéo).

Mise à jour explicative

413.1.2 Transmission des données de sous-titres codés

Les données des sous-titres doivent passer par le câblage et l’équipement auxiliaire.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

5.4 Préservation des renseignements sur l’accessibilité pendant la conversion

Lorsque les TIC convertissent des renseignements ou des communications, elles préservent tous les renseignements libres documentés fournis aux fins d’accessibilité, dans la mesure où ces renseignements peuvent être contenus ou pris en charge dans le format de destination.

413.1.2 Transmission des données de sous-titres codés

Les données des sous-titres doivent passer par le câblage et l’équipement auxiliaire.

7.1.3 Préservation du sous-titrage

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

D’autres aspects d’affichage du texte (p. ex. le positionnement à l’écran, la couleur et le style du texte ainsi que la police de caractères) peuvent être significatifs selon les conventions régionales. La modification de ces aspects pourrait en changer le sens et devrait être évitée dans la mesure du possible.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

7.1.3 Préservation du sous-titrage

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

D’autres aspects d’affichage du texte (p. ex. le positionnement à l’écran, la couleur et le style du texte ainsi que la police de caractères) peuvent être significatifs selon les conventions régionales. La modification de ces aspects pourrait en changer le sens et devrait être évitée dans la mesure du possible.

7.1.3 Préservation du sous-titrage

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

D’autres aspects d’affichage du texte (p. ex. le positionnement à l’écran, la couleur et le style du texte ainsi que la police de caractères) peuvent être significatifs selon les conventions régionales. La modification de ces aspects pourrait en changer le sens et devrait être évitée dans la mesure du possible.

7.1.3 Préservation du sous-titrage

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver les sous-titres de manière à ce qu’ils puissent être affichés conformément aux clauses 7.1.1 et 7.1.2.

D’autres aspects d’affichage du texte (p. ex. le positionnement à l’écran, la couleur et le style du texte ainsi que la police de caractères) peuvent être significatifs selon les conventions régionales. La modification de ces aspects pourrait en changer le sens et devrait être évitée dans la mesure du possible.

Liste des tableaux

414 Technologies de traitement de la description audio

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

414.1.1 Syntoniseurs de télévision numérique

Les syntoniseurs de télévision numérique doivent prévoir un traitement de la description audio conforme à la partie 5 de la norme de télévision numérique ATSC A/53 (2014) (incorporée par renvoi, voir l’article 702.2.1). Les syntoniseurs de télévision numérique doivent traiter la description audio lorsqu’elle est codée comme un service audio associé aux malvoyants qui est fourni sous forme de combinaison complète de programmes contenant une description audio conformément à la norme ATSC A/53.22

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

414.1.2 Autres TIC

Les TIC autres que les syntoniseurs de télévision numérique doivent prévoir un traitement de la description audio.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

Reformulation stylistique

Mise à jour explicative

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

7.2.3 Préservation de la description audio

Lorsque les TIC transmettent, convertissent ou enregistrent de la vidéo avec synchronisation sonore, elles doivent préserver la description audio de manière à ce qu’elle puisse être lue conformément aux clauses 7.2.1 et 7.2.2.

Liste des tableaux

415 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

415.1.1 Commandes pour les sous-titres

Lorsque les TIC sont dotées de pièces manœuvrables pour le réglage du volume, elles doivent aussi être dotées de pièces manœuvrables pour la sélection des sous-titres.23

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Reformulation stylistique

Mise à jour explicative

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

415.1.2 Commandes pour les descriptions audio

Lorsque les TIC sont dotées de pièces manœuvrables pour la sélection des programmes, elles doivent aussi être dotées de pièces manœuvrables pour la sélection de la description audio.24

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour contrôler les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Reformulation stylistique

Mise à jour explicative

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour contrôler les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour contrôler les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour contrôler les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Liste des tableaux

Chapitre 5 - Logiciels

501 Généralités

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

501.1 Portée

Les exigences du chapitre 5 s’appliquent aux logiciels lorsque l’exige le chapitre 2 de la norme 508 (Exigences relatives à la portée), le chapitre 2 des directives 255 (Exigences relatives à la portée), et lorsqu’il en est fait mention autrement dans tout autre chapitre de la norme 508 révisée ou des directives 255 révisées.

EXCEPTION : Lorsque des applications Web n’ont pas accès aux services d’accessibilité de la plateforme et n’incluent pas les composants qui ont accès aux services d’accessibilité de la plateforme, ils n’ont pas être conformes à la clause 502 ou 503, à condition qu’ils soient conformes aux critères de succès de niveau A et de niveau AA et aux exigences de conformité dans les WCAG 2.0 (incorporées par renvoi, voir l’article 702.10.1).

Les chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.0 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).

Mise à jour explicative

Reformulation stylistique

Les chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).Changement fonctionnelLes chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).Les chapitres 9, 10, 11 appliquent les critères de succès des WCAG 2.1 Niveau A et Niveau AA au contenu Web (chapitre 9), aux documents (chapitre 10) et aux logiciels non Web (chapitre 11).

Liste des tableaux

502 Interopérabilité avec technologie d’assistance

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

502.2.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Les logiciels de la plateforme doivent permettre à l’utilisateur de contrôler les caractéristiques de la plateforme qui sont définies dans la documentation de celle-ci comme étant des caractéristiques d’accessibilité.

11.4.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Lorsque le logiciel est une plateforme, il doit offrir des modes de fonctionnement suffisants permettant à l’utilisateur de contrôler les caractéristiques d’accessibilité de la plateforme documentées comme étant destinées aux utilisateurs.

Reformulation stylistique

11.6.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Lorsque le logiciel est une plateforme, il doit offrir des modes de fonctionnement suffisants permettant à l’utilisateur de contrôler les caractéristiques d’accessibilité de la plateforme documentées comme étant destinées aux utilisateurs.

Changement de numérotation

11.6.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Lorsque le logiciel est une plateforme, il doit offrir des modes de fonctionnement suffisants permettant à l’utilisateur de contrôler les caractéristiques d’accessibilité de la plateforme documentées comme étant destinées aux utilisateurs.

11.6.1 Contrôle par l’utilisateur des caractéristiques d’accessibilité

Lorsque le logiciel est une plateforme, il doit offrir des modes de fonctionnement suffisants permettant à l’utilisateur de contrôler les caractéristiques d’accessibilité de la plateforme documentées comme étant destinées aux utilisateurs.

502.2.2 Aucune perturbation des caractéristiques d'accessibilité

Les logiciels ne doivent pas perturber les caractéristiques de la plateforme qui sont définies dans la documentation de celle-ci comme étant des caractéristiques d’accessibilité.

11.4.2 Aucune perturbation des caractéristiques d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, elle ne doit pas perturber les caractéristiques d’accessibilité documentées qui sont définies dans la documentation de la plateforme, sauf si l’utilisateur en fait la demande pendant le fonctionnement du logiciel.

Reformulation stylistique

Mise à jour explicative

11.6.2 Aucune perturbation des caractéristiques d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, elle ne doit pas perturber les caractéristiques d’accessibilité documentées qui sont définies dans la documentation de la plateforme, sauf si l’utilisateur en fait la demande pendant le fonctionnement du logiciel.

Changement de numérotation

11.6.2 Aucune perturbation des caractéristiques d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, elle ne doit pas perturber les caractéristiques d’accessibilité documentées qui sont définies dans la documentation de la plateforme, sauf si l’utilisateur en fait la demande pendant le fonctionnement du logiciel.

11.6.2 Aucune perturbation des caractéristiques d’accessibilité

Lorsque le logiciel fournit une interface utilisateur, elle ne doit pas perturber les caractéristiques d’accessibilité documentées qui sont définies dans la documentation de la plateforme, sauf si l’utilisateur en fait la demande pendant le fonctionnement du logiciel.

502.3 Services d’accessibilité

Les logiciels et les outils logiciels de la plateforme fournis par le développeur de celle-ci doivent fournir un ensemble documenté de services d’accessibilité qui prennent en charge les applications exécutées sur la plateforme pour interagir avec la technologie d’assistance et doivent être conformes à la clause 502.3. Les applications qui sont également des plateformes doivent exposer les services d’accessibilité de la plateforme sous-jacents ou mettre en œuvre d’autres services d’accessibilité documentés.

11.3.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur

Les logiciels de plateforme doivent fournir un ensemble de services de plateforme documentés qui permettent aux logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme d’interagir avec la technologie d’assistance.

Le logiciel de la plateforme doit prendre en charge les exigences 11.3.2.5 à 11.3.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.3.2.5 à 11.3.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.3.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Elles définissent la fonctionnalité minimale des logiciels fournissant des interfaces utilisateur lors de l’utilisation des services de la plateforme.

REMARQUE 2 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 3 : Les services d’interface utilisateur qui fournissent par défaut un soutien à l’accessibilité sont considérés comme faisant partie des services fournis pour se conformer à cette clause (par exemple, le service de création d’un nouvel élément d’interface utilisateur fournit un rôle, un état, une limite, un nom et une description).

REMARQUE 4 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

REMARQUE 5 : Dans des environnements de programme informatique particuliers, les attributs techniques associés aux propriétés de l’interface utilisateur décrites dans les clauses 11.3.2.5 à 11.3.2.17 peuvent avoir des noms différents de ceux utilisés dans ces clauses.

Reformulation stylistique

Mise à jour explicative

11.5.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur

Les logiciels de plateforme doivent fournir un ensemble de services de plateforme documentés qui permettent aux logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme d’interagir avec la technologie d’assistance.

Le logiciel de la plateforme doit prendre en charge les exigences 11.5.2.5 à 11.5.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Elles définissent la fonctionnalité minimale des logiciels fournissant des interfaces utilisateur lors de l’utilisation des services de la plateforme.

REMARQUE 2 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 3 : Les services d’interface utilisateur qui fournissent par défaut un soutien à l’accessibilité sont considérés comme faisant partie des services fournis pour se conformer à cette clause (par exemple, le service de création d’un nouvel élément d’interface utilisateur fournit un rôle, un état, une limite, un nom et une description).

REMARQUE 4 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

REMARQUE 5 : Dans des environnements d’un programme informatique particuliers, les attributs techniques associés aux propriétés de l’interface utilisateur décrites dans les clauses 11.5.2.5 à 11.5.2.17 peuvent avoir des noms différents de ceux utilisés dans ces clauses.

Changement de numérotation

Reformulation stylistique

11.5.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur

Les logiciels de plateforme doivent fournir un ensemble de services de plateforme documentés qui permettent aux logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme d’interagir avec la technologie d’assistance.

Lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 est pris en charge au sein de l’environnement logiciel, le logiciel de la plateforme devrait prendre en charge cette exigence. Par exemple, les attributs de sélection de 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Elles définissent la fonctionnalité minimale des logiciels fournissant des interfaces utilisateur lors de l’utilisation des services de la plateforme.

REMARQUE 2 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 3 : Les services d’interface utilisateur qui fournissent par défaut un soutien à l’accessibilité sont considérés comme faisant partie des services fournis pour se conformer à cette clause (par exemple, le service de création d’un nouvel élément d’interface utilisateur fournit un rôle, un état, une limite, un nom et une description).

REMARQUE 4 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

REMARQUE 5 : Dans des environnements d’un programme informatique particuliers, les attributs techniques associés aux propriétés de l’interface utilisateur décrites dans les clauses 11.5.2.5 à 11.5.2.17 peuvent avoir des noms différents de ceux utilisés dans ces clauses.

Reformulation stylistique

11.5.2.1 Soutien pour le service d’accessibilité aux plateformes pour les logiciels qui fournissent une interface utilisateur

Les logiciels de plateforme doivent fournir un ensemble de services de plateforme documentés qui permettent aux logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme d’interagir avec la technologie d’assistance.

Lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 est pris en charge au sein de l’environnement logiciel, le logiciel de la plateforme devrait prendre en charge cette exigence. Par exemple, les attributs de sélection de la clause 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Elles définissent la fonctionnalité minimale des logiciels fournissant des interfaces utilisateur lors de l’utilisation des services de la plateforme.

REMARQUE 2 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 3 : Les services d’interface utilisateur qui fournissent par défaut un soutien à l’accessibilité sont considérés comme faisant partie des services fournis pour se conformer à cette clause (par exemple, le service de création d’un nouvel élément d’interface utilisateur fournit un rôle, un état, une limite, un nom et une description).

REMARQUE 4 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

REMARQUE 5 : Dans des environnements d’un programme informatique particuliers, les attributs techniques associés aux propriétés de l’interface utilisateur décrites dans les clauses 11.5.2.5 à 11.5.2.17 peuvent avoir des noms différents de ceux utilisés dans ces clauses.

502.3 Services d’accessibilité

Les logiciels et les outils logiciels de la plateforme fournis par le développeur de celle-ci doivent fournir un ensemble documenté de services d’accessibilité qui prennent en charge les applications exécutées sur la plateforme pour interagir avec la technologie d’assistance et doivent être conformes à la clause 502.3. Les applications qui sont également des plateformes doivent exposer les services d’accessibilité de la plateforme sous-jacents ou mettre en œuvre d’autres services d’accessibilité documentés.

11.3.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Le logiciel de la plateforme doit fournir un ensemble de services d’accessibilité documentés qui permettent à la technologie d’assistance d’interagir avec les logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme.

Le logiciel de plateforme doit prendre en charge les exigences 11.3.2.5 à 11.3.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.3.2.5 à 11.3.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.3.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Celles-ci définissent les fonctions minimales disponibles pour les technologies d’assistance lors de l’utilisation des services de plateforme.

REMARQUE 2 : La définition de plateforme dans 3.1 s’applique aux logiciels qui fournissent des services à d’autres logiciels, y compris, mais sans s’y limiter, les systèmes d’exploitation, les navigateurs Internet et les machines virtuelles.

REMARQUE 3 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 4 : Généralement, ces services appartiennent au même ensemble de services qui sont décrits dans la clause 11.3.2.1.

REMARQUE 5 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

Reformulation stylistique

Mise à jour explicative

11.5.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Le logiciel de la plateforme doit fournir un ensemble de services d’accessibilité documentés qui permettent à la technologie d’assistance d’interagir avec les logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme.

Le logiciel de plateforme doit prendre en charge les exigences 11.5.2.5 à 11.5.2.17, sauf que, lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 ne s’applique pas à l’environnement logiciel, ces exigences ne sont pas applicables. Par exemple, les attributs de sélection de 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Celles-ci définissent les fonctions minimales disponibles pour les technologies d’assistance lors de l’utilisation des services de plateforme.

REMARQUE 2 : La définition de plateforme dans la clause 3.1 s’applique aux logiciels qui fournissent des services à d’autres logiciels, y compris, mais sans s’y limiter, les systèmes d’exploitation, les navigateurs Web et les machines virtuelles.

REMARQUE 3 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 4 : Généralement, ces services appartiennent au même ensemble de services qui sont décrits dans la clause 11.5.2.1.

REMARQUE 5 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

Changement de numérotation

Reformulation stylistique

11.5.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Le logiciel de la plateforme doit fournir un ensemble de services d’accessibilité documentés qui permettent à la technologie d’assistance d’interagir avec les logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme.

Lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 est pris en charge au sein de l’environnement logiciel, le logiciel de la plateforme devrait prendre en charge cette exigence. Par exemple, les attributs de sélection de 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Celles-ci définissent les fonctions minimales disponibles pour les technologies d’assistance lors de l’utilisation des services de plateforme.

REMARQUE 2 : La définition de plateforme dans la clause 3.1 s’applique aux logiciels qui fournissent des services à d’autres logiciels, y compris, mais sans s’y limiter, les systèmes d’exploitation, les navigateurs Web et les machines virtuelles.

REMARQUE 3 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 4 : Généralement, ces services appartiennent au même ensemble de services qui sont décrits dans la clause 11.5.2.1.

REMARQUE 5 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

Reformulation stylistique

11.5.2.2 Soutien pour le service d’accessibilité aux plateformes pour les technologies d’assistance

Le logiciel de la plateforme doit fournir un ensemble de services d’accessibilité documentés qui permettent à la technologie d’assistance d’interagir avec les logiciels qui fournissent une interface utilisateur fonctionnant sur le logiciel de plateforme.

Lorsqu’un concept d’interface utilisateur correspondant à l’une des clauses 11.5.2.5 à 11.5.2.17 est pris en charge au sein de l’environnement logiciel, le logiciel de la plateforme devrait prendre en charge cette exigence. Par exemple, les attributs de sélection de la clause 11.5.2.14 (Modification du focus et des attributs de sélection) pourraient ne pas exister dans les environnements qui ne permettent pas la sélection, qui est le plus souvent associée au copier-coller.

REMARQUE 1 : Celles-ci définissent les fonctions minimales disponibles pour les technologies d’assistance lors de l’utilisation des services de plateforme.

REMARQUE 2 : La définition de plateforme dans la clause 3.1 s’applique aux logiciels qui fournissent des services à d’autres logiciels, y compris, mais sans s’y limiter, les systèmes d’exploitation, les navigateurs Web et les machines virtuelles.

REMARQUE 3 : Dans certaines plateformes, ces services peuvent être appelés services d’accessibilité, mais dans d’autres plateformes, ces services peuvent être fournis dans le cadre des services d’interface utilisateur.

REMARQUE 4 : Généralement, ces services appartiennent au même ensemble de services qui sont décrits dans la clause 11.5.2.1.

REMARQUE 5 : Pour se conformer à cette exigence, le logiciel de la plateforme peut fournir son propre ensemble de services ou exposer les services fournis par ses couches de plateforme sous-jacentes, si ces services sont conformes à cette exigence.

502.3.1 Renseignements sur les objets

Le rôle, les états, les propriétés, les limites, le nom et la description des objets doivent être déterminables par un programme informatique.

11.3.2.5 Renseignements sur les objets

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, permettre au rôle, aux états, à la limite, au nom et à la description des éléments d’interface utilisateur d’être déterminés par un programme informatique au moyen de technologies d’assistance.

Reformulation stylistique

Mise à jour explicative

11.5.2.5 Renseignements sur les objets

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre au rôle, aux états, à la limite, au nom et à la description des éléments d’interface utilisateur d’être déterminés par un programme informatique au moyen de technologies d’assistance.

Changement de numérotation

11.5.2.5 Renseignements sur les objets

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre au rôle, aux états, à la limite, au nom et à la description des éléments d’interface utilisateur d’être déterminés par un programme informatique au moyen de technologies d’assistance.

11.5.2.5 Renseignements sur les objets

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre au rôle, aux états, à la limite, au nom et à la description des éléments d’interface utilisateur d’être déterminés par un programme informatique au moyen de technologies d’assistance.

502.3.2 Modification des renseignements sur les objets

Les états et les propriétés qui peuvent être définis par l’utilisateur doivent pouvoir être définis par un programme informatique, y compris par une technologie d’assistance.

11.3.2.16 Modifications d’états ou de propriétés

Lorsque les exigences de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.3.2.3, permettre aux technologies d’assistance de modifier par un programme informatique les états et propriétés des éléments d’interface utilisateur grâce auxquels l’utilisateur peut modifier ces articles.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.5.2.16 Modifications d’états ou de propriétés

Où les exigences de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique les états et propriétés des éléments d’interface utilisateur grâce auxquels l’utilisateur peut modifier ces articles.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Changement de numérotation

Reformulation stylistique

11.5.2.16 Modifications d’états ou de propriétés

Lorsque les exigences de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique les états et propriétés des éléments d’interface utilisateur grâce auxquels l’utilisateur peut modifier ces articles.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

11.5.2.16 Modifications d’états ou de propriétés

Lorsque les exigences de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique les états et propriétés des éléments d’interface utilisateur grâce auxquels l’utilisateur peut modifier ces articles.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

502.3.3 Ligne, colonne et en-têtes

Si un objet se trouve dans une table de données, les lignes et colonnes occupées, ainsi que les en-têtes associés à celles-ci, doivent être déterminables par un programme informatique.

11.3.2.6 Ligne, colonne et en-têtes

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, rendre la ligne et la colonne de chaque cellule d’un tableau de données, y compris les en-têtes de la ligne et de la colonne, le cas échéant, déterminables par un programme informatique au moyen de technologies d’assistance.

Reformulation stylistique

Mise à jour explicative

11.5.2.6 Ligne, colonne et en-têtes

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la ligne et la colonne de chaque cellule d’un tableau de données, y compris les en-têtes de la ligne et de la colonne, le cas échéant, déterminables par un programme informatique au moyen de technologies d’assistance.

Changement de numérotation

11.5.2.6 Ligne, colonne et en-têtes

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la ligne et la colonne de chaque cellule d’un tableau de données, y compris les en-têtes de la ligne et de la colonne, le cas échéant, déterminables par un programme informatique au moyen de technologies d’assistance.

11.5.2.6 Ligne, colonne et en-têtes

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la ligne et la colonne de chaque cellule d’un tableau de données, y compris les en-têtes de la ligne et de la colonne, le cas échéant, déterminables par un programme informatique au moyen de technologies d’assistance.

502.3.4 Valeurs

Toute valeur actuelle, ainsi que toute série ou plage de valeurs admissibles associée à un objet, doit être déterminable par un programme informatique.

11.3.2.7 Valeurs

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, rendre la valeur actuelle d’un élément d’interface utilisateur et toute valeur minimale ou maximale de la plage, si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, pouvant être déterminées par un programme informatique par des technologies d’assistance.

Reformulation stylistique

Mise à jour explicative

11.5.2.7 Valeurs

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la valeur actuelle d’un élément d’interface utilisateur et toute valeur minimale ou maximale de la plage, si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, pouvant être déterminées par un programme informatique par des technologies d’assistance.

Changement de numérotation

11.5.2.7 Valeurs

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la valeur actuelle d’un élément d’interface utilisateur et toute valeur minimale ou maximale de la plage, si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, pouvant être déterminées par un programme informatique par des technologies d’assistance.

11.5.2.7 Valeurs

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre la valeur actuelle d’un élément d’interface utilisateur et toute valeur minimale ou maximale de la plage, si l’élément d’interface utilisateur fournit des informations sur une plage de valeurs, pouvant être déterminées par un programme informatique par des technologies d’assistance.

502.3.5 Modification des valeurs

Les valeurs pouvant être définies par l’utilisateur doivent pouvoir être établies par un programme informatique, y compris au moyen d’une technologie d’assistance.

11.3.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à 11.3.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recours aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.5.2.17 Modifications des valeurs et du texte

Où les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recours aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Changement de numérotation

Reformulation stylistique

11.5.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recours aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

11.5.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recours aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

502.3.6 Liens entre les étiquettes

Tout lien qu’entretient un composant en tant qu’étiquette pour un autre composant, ou en tant que composant étiqueté par un autre composant, doit être déterminable par un programme informatique.

11.3.2.8 Liens entre les étiquettes

Lorsque le logiciel fournit une interface utilisateur, il expose le lien qu’entretient un élément d’interface utilisateur en tant qu’étiquette pour un autre élément ou en tant qu’élément étiqueté par un autre élément, en utilisant les services décrits dans la clause 11.3.2.3, de sorte que ces informations puissent être déterminées par un programme informatique par des technologies d’assistance.

Reformulation stylistique

Mise à jour explicative

11.5.2.8 Liens entre les étiquettes

Lorsque le logiciel fournit une interface utilisateur, il expose le lien qu’entretient un élément d’interface utilisateur en tant qu’étiquette pour un autre élément ou en tant qu’élément étiqueté par un autre élément, en utilisant les services décrits dans la clause 11.5.2.3, de sorte que ces informations puissent être déterminées par un programme informatique par des technologies d’assistance.

Changement de numérotation

11.5.2.8 Liens entre les étiquettes

Lorsque le logiciel fournit une interface utilisateur, il expose le lien qu’entretient un élément d’interface utilisateur en tant qu’étiquette pour un autre élément ou en tant qu’élément étiqueté par un autre élément, en utilisant les services décrits dans la clause 11.5.2.3, de sorte que ces informations puissent être déterminées par un programme informatique par des technologies d’assistance.

11.5.2.8 Liens entre les étiquettes

Lorsque le logiciel fournit une interface utilisateur, il expose le lien qu’entretient un élément d’interface utilisateur en tant qu’étiquette pour un autre élément ou en tant qu’élément étiqueté par un autre élément, en utilisant les services décrits dans la clause 11.5.2.3, de sorte que ces informations puissent être déterminées par un programme informatique par des technologies d’assistance.

502.3.7 Relations hiérarchiques

Toute relation hiérarchique (parent-enfant) qu’entretient un composant en tant que conteneur d’un autre composant, ou en tant que composant contenu par un composant, doit être déterminable par un programme informatique.

11.3.2.9 Relations parents-enfants

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, la relation entre un élément d’interface utilisateur et tout élément parent ou enfant.

Reformulation stylistique

Mise à jour explicative

11.5.2.9 Relations parents-enfants

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, la relation entre un élément d’interface utilisateur et tout élément parent ou enfant.

Changement de numérotation

11.5.2.9 Relations parents-enfants

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, la relation entre un élément d’interface utilisateur et tout élément parent ou enfant.

11.5.2.9 Relations parents-enfants

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, la relation entre un élément d’interface utilisateur et tout élément parent ou enfant.

502.3.8 Texte

Le contenu des objets textuels, les attributs textuels et la limite du texte affiché à l’écran doivent être déterminables par un programme informatique.

11.3.2.10 Texte

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, le contenu textuel, les attributs textuels et la limite du texte rendu à l’écran.

Reformulation stylistique

Mise à jour explicative

11.5.2.10 Texte

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, le contenu textuel, les attributs textuels et la limite du texte rendu à l’écran.

Changement de numérotation

11.5.2.10 Texte

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, le contenu textuel, les attributs textuels et la limite du texte rendu à l’écran.

11.5.2.10 Texte

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, le contenu textuel, les attributs textuels et la limite du texte rendu à l’écran.

502.3.9 Modification du texte

Le texte pouvant être défini par l’utilisateur doit pouvoir être établi par un programme informatique, y compris au moyen d’une technologie d’assistance.

11.3.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à 11.3.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recourir aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.5.2.17 Modifications des valeurs et du texte

Où les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recourir aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Changement de numérotation

Reformulation stylistique

11.5.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recourir aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

11.5.2.17 Modifications des valeurs et du texte

Lorsque les exigences en matière de sécurité l’autorisent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier les valeurs et le texte des éléments d’interface utilisateur en se servant des méthodes de saisie de la plateforme grâce auxquelles un utilisateur peut changer ces éléments sans recourir aux technologies d’assistance.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être nécessaires pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

502.3.10 Liste des actions

Une liste de toutes les actions pouvant être exécutées sur un objet doit être déterminable par un programme informatique.

11.3.2.11 Liste des actions disponibles

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, une liste des actions disponibles qui peuvent être exécutées sur un élément d’interface utilisateur.

Reformulation stylistique

Mise à jour explicative

11.5.2.11 Liste des actions disponibles

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, une liste des actions disponibles qui peuvent être exécutées sur un élément d’interface utilisateur.

Changement de numérotation

11.5.2.11 Liste des actions disponibles

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, une liste des actions disponibles qui peuvent être exécutées sur un élément d’interface utilisateur.

11.5.2.11 Liste des actions disponibles

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, permettre de déterminer, par un programme informatique au moyen de technologies d’assistance, une liste des actions disponibles qui peuvent être exécutées sur un élément d’interface utilisateur.

502.3.11 Actions sur les objets

Les applications doivent permettre à la technologie d’assistance d’exécuter par un programme informatique les actions disponibles sur les objets.

11.3.2.12 Exécution des actions disponibles

Lorsque les exigences de sécurité le permettent, le logiciel qui fournit une interface utilisateur doit, en utilisant les services décrits à la clause 11.3.2.3, permettre l’exécution programmatique des actions exposées, au moyen des technologies d’assistance, conformément à la clause 11.3.2.11.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.5.2.12 Exécution des actions disponibles

Où les exigences de sécurité le permettent, le logiciel qui fournit une interface utilisateur doit, en utilisant les services décrits à la clause 11.5.2.3, permettre l’exécution programmatique des actions exposées, au moyen des technologies d’assistance, conformément à la clause 11.5.2.11.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Changement de numérotation

Reformulation stylistique

11.5.2.12 Exécution des actions disponibles

Lorsque les exigences de sécurité le permettent, le logiciel qui fournit une interface utilisateur doit, en utilisant les services décrits à la clause 11.5.2.3, permettre l’exécution programmatique des actions exposées, au moyen des technologies d’assistance, conformément à la clause 11.5.2.11.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

11.5.2.12 Exécution des actions disponibles

Lorsque les exigences de sécurité le permettent, le logiciel qui fournit une interface utilisateur doit, en utilisant les services décrits à la clause 11.5.2.3, permettre l’exécution programmatique des actions exposées, au moyen des technologies d’assistance, conformément à la clause 11.5.2.11.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Les technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

502.3.12 Curseur du focus

Les applications doivent exposer les informations et les mécanismes nécessaires pour faire le suivi du focus, du point d’insertion du texte et des attributs de sélection des composants de l’interface utilisateur.

11.3.2.13 Suivi du focus et des attributs de sélection

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.3.2.3, rendre l’information et les mécanismes nécessaires au suivi de le focus, du point d’insertion du texte et des attributs de sélection des éléments d’interface utilisateur, déterminables par un programme informatique par les technologies d’assistance.

Reformulation stylistique

Mise à jour explicative

11.5.2.13 Suivi du focus et des attributs de sélection

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre l’information et les mécanismes nécessaires au suivi du focus, du point d’insertion du texte et des attributs de sélection des éléments d’interface utilisateur, déterminables par un programme informatique par les technologies d’assistance.

Changement de numérotation

11.5.2.13 Suivi du focus et des attributs de sélection

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre l’information et les mécanismes nécessaires au suivi du focus, du point d’insertion du texte et des attributs de sélection des éléments d’interface utilisateur, déterminables par un programme informatique par les technologies d’assistance.

11.5.2.13 Suivi du focus et des attributs de sélection

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, rendre l’information et les mécanismes nécessaires au suivi du focus, du point d’insertion du texte et des attributs de sélection des éléments d’interface utilisateur, déterminables par un programme informatique par les technologies d’assistance.

502.3.13 Modification du curseur du focus

Le focus, le point d’insertion du texte et les attributs de sélection qui peuvent être définis par l’utilisateur doivent pouvoir être définis par un programme informatique, y compris au moyen de l’utilisation d’une technologie d’assistance.

11.3.2.14 Modification du focus et des attributs de sélection

Lorsque les exigences de sécurité le permettent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.3.2.3, permettre aux technologies d’assistance de modifier par un programme informatique le focus, le point d’insertion de texte et les attributs de sélection des éléments d’interface utilisateur où l’utilisateur peut modifier ces éléments.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.5.2.14 Modification du focus et des attributs de sélection

Où les exigences de sécurité le permettent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique le focus, le point d’insertion de texte et les attributs de sélection des éléments d’interface utilisateur où l’utilisateur peut modifier ces éléments.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

Changement de numérotation

Reformulation stylistique

11.5.2.14 Modification du focus et des attributs de sélection

Lorsque les exigences de sécurité le permettent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique le focus, le point d’insertion de texte et les attributs de sélection des éléments d’interface utilisateur où l’utilisateur peut modifier ces éléments.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

11.5.2.14 Modification du focus et des attributs de sélection

Lorsque les exigences de sécurité le permettent, les logiciels qui fournissent une interface utilisateur doivent, en utilisant les services décrits à la clause 11.5.2.3, permettre aux technologies d’assistance de modifier par un programme informatique le focus, le point d’insertion de texte et les attributs de sélection des éléments d’interface utilisateur où l’utilisateur peut modifier ces éléments.

REMARQUE 1 : Dans certains cas, les exigences de sécurité imposées à un logiciel peuvent interdire à un logiciel externe d’interférer avec le produit de TIC et cette exigence ne s’applique donc pas. À titre d’exemple de systèmes soumis à des exigences strictes en matière de sécurité, mentionnons les systèmes qui traitent des activités de renseignement, des activités cryptologiques liées à la sécurité nationale, du commandement et du contrôle des forces militaires.

REMARQUE 2 : Des technologies d’assistance peuvent être requises pour maintenir le même niveau de sécurité que les mécanismes de saisie standard pris en charge par la plateforme.

502.3.14 Avis d’événements

La technologie d’assistance doit avoir accès aux avis d’événements liés aux interactions de l’utilisateur, y compris, sans toutefois s’y limiter, les changements aux états, à la valeur, au nom, à la description et à la limite du composant.

11.3.2.15 Avis de modification

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à 11.3.2.3, aviser les technologies d’assistance des changements apportés aux attributs des éléments d’interface utilisateur pouvant être déterminés par un programme informatique qui sont mentionnés dans les exigences 11.3.2.5 à 11.3.2.11 et 11.3.2.13.

Reformulation stylistique

Mise à jour explicative

11.5.2.15 Avis de modification

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, aviser les technologies d’assistance des changements apportés aux attributs des éléments d’interface utilisateur pouvant être déterminés par un programme informatique qui sont mentionnés dans les exigences 11.5.2.5 à 11.5.2.11 et 11.5.2.13.

Changement de numérotation

Reformulation stylistique

11.5.2.15 Avis de modification

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, aviser les technologies d’assistance des changements apportés aux attributs des éléments d’interface utilisateur pouvant être déterminés par un programme informatique qui sont mentionnés dans les exigences 11.5.2.5 à 11.5.2.11 et 11.5.2.13.

11.5.2.15 Avis de modification

Lorsque le logiciel fournit une interface utilisateur, il doit, en utilisant les services décrits à la clause 11.5.2.3, aviser les technologies d’assistance des changements apportés aux attributs des éléments d’interface utilisateur pouvant être déterminés par un programme informatique qui sont mentionnés dans les exigences 11.5.2.5 à 11.5.2.11 et 11.5.2.13.

502.4 Caractéristiques d’accessibilité de la plateforme

Les plateformes et les logiciels de plateforme doivent être conformes aux exigences de la norme ANSI/HFES 200.2, Human Factors Engineering of Software User interfaces — Part 2: Accessibility (2008) (incorporée par renvoi, voir l’article 702.4.1) énumérées ci-dessous :

Voir A-G, ci-dessous.Voir A-G, ci-dessous.Voir A-G, ci-dessous.Voir A-G, ci-dessous.
  1. L’article 9.3.3 permet la saisie séquentielle de plusieurs touches (avec accord) ;25

5.9 Actions simultanées de la part de l’utilisateur

Lorsque les TIC requièrent des actions simultanées de la part de l’utilisateur pour fonctionner, ces TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas d’actions simultanées de la part de l’utilisateur pour fonctionner.

REMARQUE : L’utilisation des deux mains pour ouvrir le couvercle d’un ordinateur portable, la pression simultanée de deux ou plusieurs touches ou le contact d’une surface avec plus d’un doigt sont des exemples d’actions simultanées de la part de l’utilisateur.

Reformulation stylistique

Mise à jour explicative

5.9 Actions simultanées de la part de l’utilisateur

Lorsque les TIC requièrent des actions simultanées de la part de l’utilisateur pour fonctionner, ces TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas d’actions simultanées de la part de l’utilisateur pour fonctionner.

REMARQUE : L’utilisation des deux mains pour ouvrir le couvercle d’un ordinateur portable, la pression simultanée de deux ou plusieurs touches ou le contact d’une surface avec plus d’un doigt sont des exemples d’actions simultanées de la part de l’utilisateur.

5.9 Actions simultanées de la part de l’utilisateur

Lorsque les TIC ont un mode de fonctionnement exigeant des actions simultanées de la part de l’utilisateur pour fonctionner, ces TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas d’actions simultanées de la part de l’utilisateur pour fonctionner.

REMARQUE : L’utilisation des deux mains pour ouvrir le couvercle d’un ordinateur portable, la pression simultanée de deux ou plusieurs touches ou le contact d’une surface avec plus d’un doigt sont des exemples d’actions simultanées de la part de l’utilisateur.

Reformulation stylistique

5.9 Actions simultanées de la part de l’utilisateur

Lorsque les TIC ont un mode de fonctionnement exigeant des actions simultanées de la part de l’utilisateur pour fonctionner, ces TIC doivent fournir au moins un mode de fonctionnement qui ne requiert pas d’actions simultanées de la part de l’utilisateur pour fonctionner.

REMARQUE : L’utilisation des deux mains pour ouvrir le couvercle d’un ordinateur portable, la pression simultanée de deux ou plusieurs touches ou le contact d’une surface avec plus d’un doigt sont des exemples d’actions simultanées de la part de l’utilisateur.

  1. L’article 9.3.4 prévoit l’ajustement du délai avant l’acceptation de la frappe;

5.7 Répétition des touches

Lorsque des TIC avec fonction de répétition des touches sont fournies et que la fonction de répétition des touches ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.

Reformulation stylistique

Mise à jour explicative

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.
Reformulation stylistique

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.

5.7 Répétition des touches

Lorsque les TIC sont dotées d’une fonction de répétition des touches qui ne peut pas être désactivée :

  1. le délai de répétition des touches doit être réglable à au moins 2 secondes;
  2. la fréquence de répétition des touches doit être réglable à un caractère par 2 secondes.
  1. L’article 9.3.5 prévoit l’ajustement de l’acceptation de la double frappe de la même touche;26

5.8 Acceptation de la double frappe

Lorsqu’un clavier ou un pavé numérique sont fournis, le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la frappe précédente, doit être réglable jusqu’à au moins 0,5 seconde.

Reformulation stylistique

Mise à jour explicative

5.8 Acceptation de la double frappe

Lorsque les TIC sont dotées d’un clavier ou d’un pavé numérique, le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la frappe précédente, doit être réglable jusqu’à au moins 0,5 seconde.

Reformulation stylistique

5.8 Acceptation de la double frappe

Lorsque les TIC sont dotées d’un clavier ou d’un pavé numérique, le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la frappe précédente, doit être réglable jusqu’à au moins 0,5 seconde.

5.8 Acceptation de la double frappe

Lorsque les TIC sont dotées d’un clavier ou d’un pavé numérique, le délai après chaque frappe, pendant lequel une pression supplémentaire sur une touche ne sera pas acceptée si elle est identique à la frappe précédente, doit être réglable jusqu’à au moins 0,5 seconde.

  1. L’article 10.7.1 prévoit l’affichage des sous-titres fournis.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est fourni, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

Reformulation stylistique

Mise à jour explicative

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

Changement fonctionnel

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

REMARQUE 3 : La clause 7.1.1 fait référence à la capacité du lecteur d’afficher des sous-titres. Les clauses 9.1.2.2, 10.1.2.2 et 11.1.2.2 font référence à la fourniture de sous-titres pour le contenu (la vidéo).

Changement explicatif

Liste des tableaux

503 Applications

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

503.2 Préférences de l’utilisateur

Les applications doivent autoriser les réglages de la plateforme, en ce qui concerne la couleur, le contraste, le type et la taille de police ainsi que le curseur du focus, en fonction des préférences de l’utilisateur.

EXCEPTION : Les applications conçues pour être isolées de leur logiciel de plateforme sous-jacent, y compris les applications Web, n’ont pas à être conformes à la clause 503.2.

11.5 Préférences de l’utilisateur

Lorsque le logiciel fournit une interface utilisateur, il doit fournir suffisamment de modes de fonctionnement se servant des préférences de l’utilisateur pour les réglages de la plateforme en ce qui concerne la couleur, le contraste, le type et la taille de police et le curseur du focus, sauf s’il s’agit de logiciels conçus pour être isolés de leur plateforme sous-jacente.

REMARQUE : Les logiciels isolés de leur plateforme sous-jacente n’ont pas accès aux paramètres de l’utilisateur de la plateforme et ne peuvent donc pas respecter cette clause.

Reformulation stylistique

Mise à jour explicative

11.7 Préférences de l’utilisateur

Lorsque le logiciel fournit une interface utilisateur, il doit fournir suffisamment de modes de fonctionnement se servant des préférences de l’utilisateur pour les réglages de la plateforme en ce qui concerne la couleur, le contraste, le type et la taille de police et le curseur du focus, sauf s’il s’agit de logiciels conçus pour être isolés de leur plateforme sous-jacente.

REMARQUE : Les logiciels isolés de leur plateforme sous-jacente n’ont pas accès aux paramètres de l’utilisateur de la plateforme et ne peuvent donc pas respecter cette clause.

Changement de numérotation

11.7 Préférences de l’utilisateur

Lorsque le logiciel n’est pas conçu pour être isolé de sa plateforme et qu’il fournit une interface utilisateur, cette interface utilisateur doit respecter les valeurs des préférences de l’utilisateur pour les réglages de la plateforme en ce qui concerne les unités de mesure, la couleur, le contraste, le type et la taille de police et le curseur du focus, sauf s’ils sont remplacés par l’utilisateur.

REMARQUE 1 : Les logiciels isolés de leur plateforme sous-jacente n’ont pas accès aux paramètres de l’utilisateur de la plateforme et ne peuvent donc pas respecter cette clause.

REMARQUE 2 : Pour le contenu Web, la plateforme sous-jacente est l’agent utilisateur.

REMARQUE 3 : Cela n’empêche pas le logiciel d’avoir des valeurs supplémentaires pour un paramètre, tant qu’il existe un mode dans lequel l’application suivra les paramètres du système, même s’ils sont plus restreints.

Reformulation stylistique

Changement fonctionnel

11.7 Préférences de l’utilisateur

Lorsque le logiciel n’est pas conçu pour être isolé de sa plateforme et qu’il fournit une interface utilisateur, cette interface utilisateur doit respecter les valeurs des préférences de l’utilisateur pour les réglages de la plateforme en ce qui concerne les unités de mesure, la couleur, le contraste, le type et la taille de police et le curseur du focus, sauf s’ils sont remplacés par l’utilisateur.
REMARQUE 1 :

Les logiciels isolés de leur plateforme sous-jacente n’ont pas accès aux paramètres de l’utilisateur de la plateforme et ne peuvent donc pas respecter cette clause.

REMARQUE 2 : Pour le contenu Web, la plateforme sous-jacente est l’agent utilisateur.

REMARQUE 3 : Cela n’empêche pas le logiciel d’avoir des valeurs supplémentaires pour un paramètre, tant qu’il existe un mode dans lequel l’application suivra les paramètres du système, même s’ils sont plus restreints.

503.3 Autres interfaces utilisateurs

Lorsqu’une application prévoit une autre interface utilisateur qui fonctionne comme une technologie d’assistance, l’application doit utiliser une plateforme et d’autres services d’accessibilité standard de l’industrie.

11.3.2.4 Technologie d’assistance

Lorsque la TIC est une technologie d’assistance, elle doit utiliser les services d’accessibilité documentés de la plateforme.

REMARQUE : L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.3.2.1 et 11.3.2.2.

REMARQUE 2 : Les technologies d’assistance peuvent également utiliser d’autres services d’accessibilité documentés.

Reformulation stylistique

Mise à jour explicative

11.5.2.4 Technologie d’assistance

Lorsque la TIC est une technologie d’assistance, elle doit utiliser les services d’accessibilité documentés de la plateforme.

REMARQUE : L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.5.2.1 et 11.5.2.2.

REMARQUE 2 : Les technologies d’assistance peuvent également utiliser d’autres services d’accessibilité documentés.

Changement de numérotation

11.5.2.4 Technologie d’assistance

Lorsque la TIC est une technologie d’assistance, elle doit utiliser les services d’accessibilité documentés de la plateforme.

REMARQUE : L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.5.2.1 et 11.5.2.2.

REMARQUE 2 : Les technologies d’assistance peuvent également utiliser d’autres services d’accessibilité documentés.

11.5.2.4 Technologie d’assistance

Lorsque la TIC est une technologie d’assistance, elle doit utiliser les services d’accessibilité documentés de la plateforme.

REMARQUE : L’expression « services documentés d’accessibilité de la plateforme » désigne l’ensemble des services fournis par la plateforme conformément aux clauses 11.5.2.1 et 11.5.2.2.

REMARQUE 2 : Les technologies d’assistance peuvent également utiliser d’autres services d’accessibilité documentés.

503.4 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent des vidéos avec synchronisation sonore, elles doivent permettre à l’utilisateur de contrôler les sous-titres et les descriptions audio conformes à la clause 503.4.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est fourni, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

Reformulation stylistique

Mise à jour explicative

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

Changement fonctionnel

7.1.1 Lecture du sous-titrage

Lorsque les TIC affichent le son synchronisé à la vidéo, elles doivent offrir un mode d’affichage des sous-titres accessibles. Lorsque le sous-titrage du contenu est accessible, les TIC doivent permettre à l’utilisateur d’afficher les sous-titres.

REMARQUE 1 : Les sous-titres peuvent contenir des renseignements sur l’heure, la couleur et le positionnement. Les sous-titres sont importants pour les utilisateurs qui en ont besoin. L’heure sert à la synchronisation des sous-titres. La couleur peut servir à identifier le locuteur. Le positionnement peut servir à éviter l’obstruction de renseignements importants.

REMARQUE 2 : Si un convertisseur en braille est connecté, les TIC devraient fournir une option pour afficher les sous-titres sur celui-ci.

REMARQUE 3 : la clause 7.1.1 fait référence à la capacité du lecteur d’afficher des sous-titres. Les clauses 9.1.2.2, 10.1.2.2 et 11.1.2.2 font référence à la fourniture de sous-titres pour le contenu (la vidéo).

Mise à jour explicative

503.4.1 Commandes pour les sous-titres

Lorsque des commandes sont fournies à l’utilisateur pour régler le volume, les commandes de l’utilisateur pour sélectionner les sous-titres doivent être fournies par les TIC au même niveau de menu que les commandes de l’utilisateur pour le réglage du volume ou la sélection des programmes.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Reformulation stylistique

Mise à jour explicative

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

503.4.2 Commandes pour les descriptions audio

Lorsque des commandes sont fournies à l’utilisateur pour sélectionner les programmes, les commandes de l’utilisateur pour sélectionner les descriptions audios doivent être fournies par les TIC au même niveau de menu que les commandes de l’utilisateur pour le réglage du volume ou la sélection des programmes.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Reformulation stylistique

Mise à jour explicative

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

7.3 Commandes de l’utilisateur pour les sous-titres et les descriptions audio

Lorsque les TIC affichent principalement du contenu vidéo et du contenu sonore associé, les commandes de l’utilisateur pour activer le sous-titrage et la description audio doivent être fournies à l’utilisateur au même niveau d’interaction (c.-à-d. le nombre d’étapes pour accomplir la tâche) que les principales commandes médias.

REMARQUE 1 : Les principales commandes médias sont celles dont se sert l’utilisateur le plus souvent pour activer les médias.

REMARQUE 2 : Les produits dotés d’une commande matérielle générale de volume, comme un téléphone ou un ordinateur portable qui peuvent être configurés pour afficher de la vidéo à l’aide d’un logiciel, mais dont ce n’est pas la fonction principale, n’auraient pas besoin de commandes matérielles précisément pour les sous-titres et les descriptions sonores; toutefois, les commandes logicielles ou les commandes matérielles cartographiées par logiciel doivent être au même niveau d’interaction.

REMARQUE 3 : Il est recommandé d’ajouter des commandes permettant à l’utilisateur d’activer ou désactiver les sous-titres et les descriptions audio par défaut.

Liste des tableaux

504 Outils-auteurs

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

504.1 Généralités

Lorsqu’une application est un outil-auteur, l’application doit être conforme à la clause 504 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format de destination.

11.6.1 Technologie du contenu

Les outils-auteurs doivent être conformes aux clauses 11.6.2 à 11.6.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

Reformulation stylistique

11.8.1 Technologie du contenu

Les outils-auteurs doivent être conformes aux clauses 11.8.2 à 11.8.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

Changement de numérotation

11.8.1 Technologie du contenu

Les outils-auteurs doivent être conformes aux clauses 11.8.2 à 11.8.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

11.8.1 Technologie du contenu

Les outils-auteurs doivent être conformes aux clauses 11.8.2 à 11.8.5 dans la mesure où les renseignements requis pour l’accessibilité sont pris en charge par le format utilisé pour les extrants de l’outil-auteur.

504.2 Création ou modification de contenu

Les outils-auteurs doivent prévoir un mode de fonctionnement permettant de créer ou de modifier du contenu qui est conforme aux critères de succès de niveau A et de niveau AA ainsi qu’aux exigences de conformité dans les WCAG 2.0 (incorporées par renvoi, voir l’article 702.10.1) pour toutes les caractéristiques prises en charge et, le cas échéant, aux formats de fichier pris en charge par l’outil-auteur. Les outils-auteurs doivent permettre aux auteurs de remplacer les renseignements requis pour l’accessibilité.

EXCEPTION : Les outils-auteurs n’ont pas à être conformes à la clause 504.2 lorsqu’ils sont utilisés pour modifier directement le code source en texte brut.

11.6.2 Création de contenu accessible

Les outils-auteurs doivent permettre et orienter la production de contenu conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

REMARQUE : Les outils-auteurs peuvent s’appuyer sur des outils supplémentaires lorsqu’il n’est pas possible de respecter des exigences spécifiques avec un seul outil. Par exemple, un outil de montage vidéo peut permettre la création de fichiers vidéo aux fins de diffusion via la télévision et le Web, mais la création de fichiers de sous-titres pour des formats multiples peut être assurée par un outil différent.

Reformulation stylistique

Mise à jour explicative

11.8.2 Création de contenu accessible

Les outils-auteurs doivent permettre et orienter la production de contenu conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

REMARQUE : Les outils-auteurs peuvent s’appuyer sur des outils supplémentaires lorsqu’il n’est pas possible de respecter des exigences spécifiques avec un seul outil. Par exemple, un outil de montage vidéo peut permettre la création de fichiers vidéo aux fins de diffusion via la télévision et le Web, mais la création de fichiers de sous-titres pour des formats multiples peut être assurée par un outil différent.

Changement de numérotation

11.8.2 Création de contenu accessible

Les outils-auteurs doivent permettre et orienter la production de contenu conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

REMARQUE : Les outils-auteurs peuvent s’appuyer sur des outils supplémentaires lorsqu’il n’est pas possible de respecter des exigences spécifiques avec un seul outil. Par exemple, un outil de montage vidéo peut permettre la création de fichiers vidéo aux fins de diffusion via la télévision et le Web, mais la création de fichiers de sous-titres pour des formats multiples peut être assurée par un outil différent.

11.8.2 Création de contenu accessible

Les outils-auteurs doivent permettre et orienter la production de contenu conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas.

REMARQUE : Les outils-auteurs peuvent s’appuyer sur des outils supplémentaires lorsqu’il n’est pas possible de respecter des exigences spécifiques avec un seul outil. Par exemple, un outil de montage vidéo peut permettre la création de fichiers vidéo aux fins de diffusion via la télévision et le Web, mais la création de fichiers de sous-titres pour des formats multiples peut être assurée par un outil différent.

504.2.1 Préservation des renseignements fournis aux fins d’accessibilité dans le cadre de la conversion de format

Les outils-auteurs doivent, lors de la conversion de contenu d’un format à un autre ou de l’enregistrement de contenu dans plusieurs formats, préserver les renseignements requis pour l’accessibilité dans la mesure où ceux-ci sont pris en charge par le format de destination.

11.6.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Lorsque l’outil-auteur fournit des transformations de restructuration ou de recodage, les renseignements sur l’accessibilité doivent alors être préservés dans l’extrant s’il existe des mécanismes équivalents dans la technologie du contenu de l’extrant.

REMARQUE 1 : Les transformations de restructuration sont des transformations dans le cadre desquelles la technologie du contenu reste identique, mais les caractéristiques structurelles du contenu sont modifiées (par exemple, linéarisation des tableaux, division d’un document en pages).

REMARQUE 2 : Les transformations de recodage sont des transformations dans le cadre desquelles la technologie utilisée pour coder le contenu est modifiée.

Reformulation stylistique

Mise à jour explicative

11.8.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Lorsque l’outil-auteur fournit des transformations de restructuration ou de recodage, les renseignements sur l’accessibilité doivent alors être préservés dans l’extrant s’il existe des mécanismes équivalents dans la technologie du contenu de l’extrant.

REMARQUE 1 : Les transformations de restructuration sont des transformations dans le cadre desquelles la technologie du contenu reste identique, mais les caractéristiques structurelles du contenu sont modifiées (par exemple, linéarisation des tableaux, division d’un document en pages).

REMARQUE 2 : Les transformations de recodage sont des transformations dans le cadre desquelles la technologie utilisée pour coder le contenu est modifiée.

Changement de numérotation

11.8.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Lorsque l’outil-auteur fournit des transformations de restructuration ou de recodage, les renseignements sur l’accessibilité doivent alors être préservés dans l’extrant s’il existe des mécanismes équivalents dans la technologie du contenu de l’extrant.

REMARQUE 1 : Les transformations de restructuration sont des transformations dans le cadre desquelles la technologie du contenu reste identique, mais les caractéristiques structurelles du contenu sont modifiées (par exemple, linéarisation des tableaux, division d’un document en pages).

REMARQUE 2 : Les transformations de recodage sont des transformations dans le cadre desquelles la technologie utilisée pour coder le contenu est modifiée.

11.8.3 Préservation des renseignements sur l’accessibilité dans le cadre de transformations

Lorsque l’outil-auteur fournit des transformations de restructuration ou de recodage, les renseignements sur l’accessibilité doivent alors être préservés dans l’extrant s’il existe des mécanismes équivalents dans la technologie du contenu de l’extrant.

REMARQUE 1 : Les transformations de restructuration sont des transformations dans le cadre desquelles la technologie du contenu reste identique, mais les caractéristiques structurelles du contenu sont modifiées (par exemple, linéarisation des tableaux, division d’un document en pages).

REMARQUE 2 : Les transformations de recodage sont des transformations dans le cadre desquelles la technologie utilisée pour coder le contenu est modifiée.

504.3 Invites

Les outils-auteurs doivent prévoir un mode de fonctionnement qui invite les auteurs à créer du contenu qui est conforme aux critères de succès de niveau A et de niveau AA ainsi qu’aux exigences de conformité dans les WCAG 2.0 (incorporées par renvoi, voir l’article 702.10.1) pour les caractéristiques prises en charge et, le cas échéant, aux formats de fichier pris en charge par l’outil-auteur.

11.6.4 Aide à la réparation

Si la fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (documents), selon le cas, alors l’outil-auteur doit formuler des suggestions en matière de réparation.

REMARQUE : Cela n’exclut pas les réparations automatisées ou semi-automatisées qui sont possibles (et recommandées) pour de nombreux types de problèmes d’accessibilité du contenu.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

11.8.4 Aide à la réparation

Si la fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, alors l’outil-auteur doit formuler des suggestions en matière de réparation.

REMARQUE : Cela n’exclut pas les réparations automatisées ou semi-automatisées qui sont possibles (et recommandées) pour de nombreux types de problèmes d’accessibilité du contenu.

Changement de numérotation

Reformulation stylistique

11.8.4 Aide à la réparation

Si la fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, alors l’outil-auteur doit formuler des suggestions en matière de réparation.

REMARQUE : Cela n’exclut pas les réparations automatisées ou semi-automatisées qui sont possibles (et recommandées) pour de nombreux types de problèmes d’accessibilité du contenu.

11.8.4 Aide à la réparation

Si la fonctionnalité de vérification de l’accessibilité d’un outil-auteur peut détecter que le contenu n’est pas conforme aux clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, alors l’outil-auteur doit formuler des suggestions en matière de réparation.

REMARQUE : Cela n’exclut pas les réparations automatisées ou semi-automatisées qui sont possibles (et recommandées) pour de nombreux types de problèmes d’accessibilité du contenu.

504.4 Modèles

Lorsque des modèles sont fournis, des modèles permettant la création de contenu qui est conforme aux critères de succès de niveau A et de niveau AA ainsi qu’aux exigences de conformité dans les WCAG 2.0 (incorporées par renvoi, voir l’article 702.10.1) doivent être fournis aux fins d’une gamme d’applications des modèles pour les caractéristiques prises en charge et, le cas échéant, aux formats de fichier pris en charge par l’outil de création.

11.6.5 Modèles

Lorsque l’outil-auteur fournit des modèles, au moins l’un des modèles qui prend en charge la création de contenu conforme aux exigences des clauses 9 (contenu Web) ou 10 (documents), selon le cas, doit être disponible et identifié en tant que tel.

Reformulation stylistique

Mise à jour explicative

11.8.5 Modèles

Lorsque l’outil-auteur fournit des modèles, au moins l’un des modèles qui prend en charge la création de contenu conforme aux exigences des clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, doit être disponible et identifié en tant que tel.

Changement de numérotation

Reformulation stylistique

11.8.5 Modèles

Lorsque l’outil-auteur fournit des modèles, au moins l’un des modèles qui prend en charge la création de contenu conforme aux exigences des clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, doit être disponible et identifié en tant que tel.

11.8.5 Modèles

Lorsque l’outil-auteur fournit des modèles, au moins l’un des modèles qui prend en charge la création de contenu conforme aux exigences des clauses 9 (contenu Web) ou 10 (contenu autre que le contenu Web), selon le cas, doit être disponible et identifié en tant que tel.

Liste des tableaux

Chapitre 6 – Documentation et services de soutien

602 Documentation de soutien

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

602.2 Caractéristiques d’accessibilité et de compatibilité

La documentation doit énumérer et expliquer comment utiliser les caractéristiques d’accessibilité et de compatibilité exigées par les chapitres 4 et 5. La documentation doit inclure les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

12.1.1 Caractéristiques d’accessibilité et de compatibilité

La documentation du produit fournie avec les TIC, qu’elle soit fournie séparément ou intégrée aux TIC doit énumérer et expliquer les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

Reformulation stylistique

Mise à jour explicative

12.1.1 Caractéristiques d’accessibilité et de compatibilité

La documentation du produit fournie avec les TIC, qu’elle soit fournie séparément ou intégrée aux TIC doit énumérer et expliquer les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

12.1.1 Caractéristiques d’accessibilité et de compatibilité

La documentation du produit fournie avec les TIC, qu’elle soit fournie séparément ou intégrée aux TIC doit énumérer et expliquer les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

REMARQUE 2 : Une pratique exemplaire consiste à utiliser WebSchemas / Accessibility 2.0 pour fournir des métadonnées sur l’accessibilité des TIC.

REMARQUE 3 : L’énoncé sur l'accessibilité et les pages d’aide sont deux exemples de diffusion de renseignements sur les produits.

Changement fonctionnel

12.1.1 Caractéristiques d’accessibilité et de compatibilité

La documentation du produit fournie avec les TIC, qu’elle soit fournie séparément ou intégrée aux TIC doit énumérer et expliquer les modes d’utilisation des caractéristiques d’accessibilité et de compatibilité des TIC.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

REMARQUE 2 : Une pratique exemplaire consiste à utiliser WebSchemas / Accessibility 2.0 [i.38] pour fournir des métadonnées sur l’accessibilité des TIC.

REMARQUE 3 : L’énoncé sur l'accessibilité et les pages d’aide sont deux exemples de diffusion de renseignements sur les produits.

602.3 Documentation de soutien électronique

La documentation au format électronique, y compris le soutien en libre-service sur le Web, doit être conforme aux critères de succès de niveau A et de niveau AA ainsi qu’aux exigences de conformité dans les WCAG 2.0 (incorporées par renvoi, voir l’article 702.10.1).

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3 : Lorsque la documentation fait partie intégrante des TIC, elle est fournie par l’intermédiaire de l’interface utilisateur qui est accessible.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

Reformulation stylistique

Mise à jour explicative

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3 : Lorsque la documentation fait partie intégrante des TIC, elle est fournie par l’intermédiaire de l’interface utilisateur qui est accessible.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant des capacités cognitives, linguistiques et d'apprentissage limitées).

REMARQUE 3 : Lorsque la documentation est intégrée dans les TIC, elle est soumise aux exigences d’accessibilité du présent document.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

Changement fonctionnel

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant des capacités cognitives, linguistiques et d'apprentissage limitées).

REMARQUE 3 : Lorsque la documentation est intégrée dans les TIC, elle est soumise aux exigences d’accessibilité du présent document.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

602.4 Autres formats pour la documentation de soutien non électronique

Lorsque la documentation de soutien est uniquement fournie dans des formats non électroniques, d’autres formats utilisables par les personnes handicapées doivent être fournis sur demande.

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3 : Lorsque la documentation fait partie intégrante des TIC, elle est fournie par l’intermédiaire de l’interface utilisateur qui est accessible.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

Reformulation stylistique

Mise à jour explicative

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant une déficience cognitive).

REMARQUE 3 : Lorsque la documentation fait partie intégrante des TIC, elle est fournie par l’intermédiaire de l’interface utilisateur qui est accessible.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant des capacités cognitives, linguistiques et d'apprentissage limitées).

REMARQUE 3 : Lorsque la documentation est intégrée dans les TIC, elle est soumise aux exigences d’accessibilité du présent document.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

Changement fonctionnel

12.1.2 Documentation accessible

La documentation du produit fournie avec les TIC doit être disponible dans au moins un des formats électroniques suivants :

  1. un format Web conforme aux exigences de la clause 9;
  2. un format autre qu’un format Web conforme aux exigences de la clause 10.

REMARQUE 1 : Cela n’exclut pas la possibilité de fournir également la documentation du produit dans d’autres formats (électroniques ou papier) non accessibles.

REMARQUE 2 : Cela n’exclut pas non plus la possibilité de fournir des formats différents répondant aux besoins d’un type précis d’utilisateurs (p. ex. des documents en braille pour les personnes aveugles ou des renseignements faciles à lire pour les personnes ayant des capacités cognitives, linguistiques et d'apprentissage limitées).

REMARQUE 3 : Lorsque la documentation est intégrée dans les TIC, elle est soumise aux exigences d’accessibilité du présent document.

REMARQUE 4 : Un agent utilisateur prenant en charge la conversion automatique des médias serait bénéfique pour améliorer l’accessibilité.

Liste des tableaux

603 Services de soutien

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

603.1 Généralités

Les services de soutien en matière de TIC, y compris, mais sans s’y limiter, les centres d’assistance, les centres d’appel, les services de formation et le soutien technique automatisé en libre-service, doivent être conformes à la clause 603.

12.2.1 Généralités (information)

Les services d’appui en matière de TIC comprennent, sans s’y limiter, les centres d’assistance, les centres d’appel, le soutien technique, les services de relais et les services de formation.

Reformulation stylistique

12.2.1 Généralités (information)

Les services d’appui en matière de TIC comprennent, sans s’y limiter, les centres d’assistance, les centres d’appel, le soutien technique, les services de relais et les services de formation.

12.2.1 Généralités (information)

Les services d’appui en matière de TIC comprennent, sans s’y limiter, les centres d’assistance, les centres d’appel, le soutien technique, les services de relais et les services de formation.

12.2.1 Généralités (information)

Les services d’appui en matière de TIC comprennent, sans s’y limiter, les centres d’assistance, les centres d’appel, le soutien technique, les services de relais et les services de formation.

603.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent inclure des renseignements sur les caractéristiques d’accessibilité et de compatibilité exigées par la clause 602.2.

12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent fournir des renseignements sur les caractéristiques d’accessibilité et de compatibilité inclus dans la documentation du produit.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

Reformulation stylistique

Mise à jour explicative

12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent fournir des renseignements sur les caractéristiques d’accessibilité et de compatibilité inclus dans la documentation du produit.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent fournir des renseignements sur les caractéristiques d’accessibilité et de compatibilité inclus dans la documentation du produit.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

12.2.2 Renseignements sur les caractéristiques d’accessibilité et de compatibilité

Les services de soutien en matière de TIC doivent fournir des renseignements sur les caractéristiques d’accessibilité et de compatibilité inclus dans la documentation du produit.

REMARQUE : Les caractéristiques d’accessibilité et de compatibilité comprennent les caractéristiques d’accessibilité intégrées et celles qui assurent la compatibilité avec la technologie d’assistance.

603.3 Adaptation des besoins en communication

Les services de soutien doivent être fournis directement à l’utilisateur ou par l’intermédiaire d’une référence à un point de contact. Ces services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées.

12.2.3 Communication efficace

Les services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

Reformulation stylistique

Mise à jour explicative

12.2.3 Communication efficace

Les services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

12.2.3 Communication efficace

Les services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

12.2.3 Communication efficace

Les services de soutien en matière de TIC doivent répondre aux besoins en communication des personnes handicapées, soit directement, soit par l’intermédiaire d’un point de référence.

Liste des tableaux

Dispositions non mises en correspondance

Article 508 révisé

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

402.3 Volume

Les TIC qui transmettent du son, y compris la sortie vocale exigée par la clause 402.2, doivent permettre de régler le volume et l’amplification de sortie conformément à la clause 402.3.

EXCEPTION : Les TIC conformes à la clause 412.2 n’ont pas à être conformes à la clause 402.3.

407.1 Généralités

Le cas échéant, les pièces manœuvrables utilisées dans le fonctionnement normal des TIC doivent être conformes à la clause 407.

407.2 Contraste

Le cas échéant, les touches et les commandes doivent se distinguer avec netteté des surfaces en arrière-plan. Les caractères et les symboles doivent se distinguer avec netteté des surfaces en arrière-plan, soit au moyen de caractères ou de symboles de couleur claire sur fond sombre, soit de caractères ou de symboles de couleur sombre sur fond clair.

407.3 Commandes d’entrée

Au moins une commande d’entrée conforme à la clause 407.3 doit être fournie pour chaque fonction.

EXCEPTION : Les dispositifs à usage personnel avec commandes d’entrée que l’on peut distinguer de manière audible sans activation et qui fonctionnent de manière tactile n’ont pas à être conformes à la clause 407.3.

407.5 Réponse minutée

Lorsqu’une réponse minutée est requise, l’utilisateur doit être averti visuellement, ainsi que de manière tactile et auditive, et il doit avoir la possibilité d’indiquer qu’il a besoin de plus de temps.27

407.8 Hauteur et profondeur de portée

Au moins un de chaque type de pièce manœuvrable des TIC fixes doit être à une hauteur conforme à la clause 407.8.2 ou 407.8.3 selon sa position établie par le plan de référence vertical spécifié à la clause 407.8.1 pour une portée latérale ou une portée avant. Les pièces manœuvrables utilisées avec sortie vocale qui sont requises par la clause 402.2 ne doivent pas être le seul type de pièce manœuvrable conforme à la clause 407.8, sauf si la pièce est la seule pièce manœuvrable de son type.28

407.8.1 Plan de référence vertical

Les pièces manœuvrables doivent être positionnées pour une portée latérale ou une portée avant déterminée par rapport à un plan de référence vertical. Le plan de référence vertical doit être situé conformément à la clause 407.8.2 ou 407.8.3.

407.8.2 Portée latérale

Les pièces manœuvrables des TIC dotées d’une portée latérale doivent être conformes à la clause 407.8.2.1 ou 407.8.2.2. Le plan de référence vertical doit être centré sur la pièce manœuvrable et placé sur le bord avant de la saillie maximale des TIC, dans la longueur du plan de référence vertical. Lorsqu’une portée latérale exige d’atteindre au-dessus d’une partie des TIC, la hauteur de cette partie des TIC doit être au maximum de 865 mm (34 po).

408.1 Généralités

Lorsqu’ils sont fournis, les écrans d’affichage doivent être conformes à la norme 408.

408.3 Clignotement

Lorsque les TIC émettent des lumières sous forme de flash, il ne doit pas y avoir plus de trois flashs dans un intervalle d’une seconde.

EXCEPTION : Les flashs qui ne dépassent pas le seuil de flash générique et le seuil de flash rouge définis dans les WCAG 2.0 (incorporés par renvoi, voir l’article 702.10.1) n’ont pas à être conformes à la clause 408.3. 29

411.1 Généralités

Lorsqu’ils sont fournis, les signaux ou indices sonores ne doivent pas être utilisés comme seul moyen de véhiculer de l’information, d’indiquer une action ou de solliciter une réponse.30

412.1 Généralités

Les TIC qui permettent une communication vocale bidirectionnelle doivent être conformes à la clause 412.

412.2 Gain de volume

Les TIC qui permettent une communication vocale bidirectionnelle doivent être conformes à la clause 412.2.1 ou 412.2.2.

412.3 Réduction des interférences et couplage magnétique

Lorsque les TIC fournissent une sortie par un combiné ou un autre type de transducteur audio qui est normalement tenu à l’oreille, elles doivent réduire les interférences avec les technologies auditives et fournir un moyen efficace de couplage magnétique sans fil conformément à la clause 412.3.1 ou 412.3.2.

412.8 Prise en charge d’ATS existant

L’équipement ou les systèmes des TIC avec communication vocale bidirectionnelle qui ne fournissent pas eux-mêmes la fonctionnalité ATS doivent être conformes à la clause 412.8.

412.8.1 Connexion ATS

Les TIC doivent inclure un point de connexion non acoustique standard pour les ATS.

412.8.2 Transmission vocale et auditive

Les TIC doivent fournir un microphone qui peut être activé et désactivé pour permettre à l’utilisateur de combiner la capacité vocale avec l’utilisation d’un ATS.

412.8.3 Compatibilité du signal

Les TIC doivent prendre en charge tous les protocoles de signaux ATS standard librement accessibles et couramment utilisés par différents fabricants lorsque le système interagit avec le réseau téléphonique commuté (RTC).

412.8.4 Messagerie vocale et autres systèmes de messagerie

Lorsqu’ils sont fournis, les systèmes de messagerie vocale, de réception automatique, de réponse vocale interactive et d’identification de l’appelant doivent être utilisables avec un ATS.

413.1 Généralités

Lorsque les TIC affichent ou traitent des vidéos avec synchronisation sonore, elles doivent fournir une technologie de traitement des sous-titres codés conforme à la clause 413.1.1 ou 413.1.2.

414.1 Généralités

Lorsque les TIC affichent ou traitent des vidéos avec synchronisation sonore, elles doivent fournir une technologie de traitement des descriptions audio conforme à la clause 414.1.1 ou 414.1.2.

415.1 Généralités

Lorsque les TIC affichent des vidéos avec synchronisation sonore, elles doivent permettre à l’utilisateur de contrôler les sous-titres et les descriptions audio conformes à la clause 415.1.

EXCEPTION : Les dispositifs à usage personnel n’ont pas à être conformes à la clause 415.1 à condition que les sous-titres et les descriptions audio puissent être activés par les paramètres de la plateforme à l’échelle du système.

502.1 Généralités

Le logiciel doit interagir avec la technologie d’assistance et être conforme à la clause 502.

EXCEPTION : Les TIC conformes à la clause 402 n’ont pas à être conformes à la clause 502.

502.4 Caractéristiques d’accessibilité de la plateforme

Les plateformes et les logiciels de plateforme doivent être conformes aux exigences de la norme ANSI/HFES 200.2, Human Factors Engineering of Software User interfaces — Part 2: Accessibility (2008) (incorporée par renvoi, voir l’article 702.4.1) énumérées ci-dessous :

  1. L’article 10.6.7 permet aux utilisateurs de choisir un équivalent visuel pour la sortie audio.31

502.4 Caractéristiques d’accessibilité de la plateforme

Les plateformes et les logiciels de plateforme doivent être conformes aux exigences de la norme ANSI/HFES 200.2, Human Factors Engineering of Software User interfaces — Part 2: Accessibility (2008) (incorporée par renvoi, voir l’article 702.4.1) énumérées ci-dessous :

  1. L’article 10.6.8 synchronise les équivalents audios pour les événements visuels.32

502.4 Caractéristiques d’accessibilité de la plateforme

Les plateformes et les logiciels de plateforme doivent être conformes aux exigences de la norme ANSI/HFES 200.2, Human Factors Engineering of Software User interfaces — Part 2: Accessibility (2008) (incorporée par renvoi, voir l’article 702.4.1) énumérées ci-dessous :

  1. L’article 10.6.9 fournit des services de sortie vocale.33

504.2.2 Exportation de fichier PDF

Les outils-auteurs capables d’exporter des fichiers PDF qui sont conformes à la norme ISO 32000-1:2008 (PDF 1.7) doivent également pouvoir exporter des fichiers PDF conformes à la norme ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1) (incorporée par renvoi, voir l’article 702.3.1).34

Liste des tableaux

EN 301 549

Article 508 réviséEN 301 549 V1.1.1 (2014)508 à 2014EN 301 549 V2.1.2 (2018)2014 à 2018EN 301 549 V3.1.1 (2019)2018 à 2019EN 301 549 V3.2.1 (2021)2019 à 2021

4.2.11 Confidentialité

Lorsque les TIC fournissent des fonctions d’accessibilité, elles préservent la vie privée des utilisateurs de ces fonctions au même niveau que celle des autres utilisateurs.

REMARQUE : Permettre la connexion de casques d’écoute personnels pour une écoute privée, ne pas fournir une version parlée des caractères masqués et permettre à l’utilisateur de contrôler les données juridiques, financières et personnelles sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

4.2.11 Confidentialité

Lorsque les TIC fournissent des fonctions d’accessibilité, elles préservent la vie privée des utilisateurs de ces fonctions au même niveau que celle des autres utilisateurs.

REMARQUE : Permettre la connexion de casques d’écoute personnels pour une écoute privée, ne pas fournir une version parlée des caractères masqués et permettre à l’utilisateur de contrôler les données juridiques, financières et personnelles sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

4.2.11 Confidentialité

Lorsque les TIC fournissent des fonctions d’accessibilité, elles préservent la vie privée des utilisateurs de ces fonctions au même niveau que celle des autres utilisateurs.

REMARQUE : Permettre la connexion de casques d’écoute personnels pour une écoute privée, ne pas fournir une version parlée des caractères masqués et permettre à l’utilisateur de contrôler les données juridiques, financières et personnelles sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

4.2.11 Confidentialité

Lorsque les TIC fournissent des fonctions d’accessibilité, elles préservent la vie privée des utilisateurs de ces fonctions au même niveau que celle des autres utilisateurs.

REMARQUE : Permettre la connexion de casques d’écoute personnels pour une écoute privée, ne pas fournir une version parlée des caractères masqués et permettre à l’utilisateur de contrôler les données juridiques, financières et personnelles sont des exemples de caractéristiques de conception qui peuvent contribuer au respect de cette clause.

4.2.9 Réduction au minimum du risque de provoquer des crises photosensibles

Lorsque les TIC prévoient des modes de fonctionnement visuels, elles fournissent au moins un mode de fonctionnement qui réduit au minimum le risque de provoquer des crises photosensibles.

REMARQUE : La limitation de la zone et du nombre de flashs par seconde peut contribuer au respect de cette clause.

4.2.9 Réduction au minimum du risque de provoquer des crises photosensibles

Lorsque les TIC prévoient des modes de fonctionnement visuels, elles fournissent au moins un mode de fonctionnement qui réduit au minimum le risque de provoquer des crises photosensibles.

REMARQUE : La limitation de la zone et du nombre de flashs par seconde peut contribuer au respect de cette clause.

4.2.9 Réduction au minimum du risque de provoquer des crises photosensibles

Lorsque les TIC prévoient des modes de fonctionnement visuels, elles fournissent au moins un mode de fonctionnement qui réduit au minimum le risque de provoquer des crises photosensibles. Ceci est essentiel pour les utilisateurs chez qui des crises photosensibles peuvent être déclenchées.

REMARQUE : La limitation de la zone et du nombre de flashs par seconde peut contribuer au respect de cette clause.

4.2.9 Réduction au minimum du risque de provoquer des crises photosensibles

Lorsque les TIC prévoient des modes de fonctionnement visuels, elles fournissent au moins un mode de fonctionnement qui réduit au minimum le risque de provoquer des crises photosensibles. Ceci est essentiel pour les utilisateurs chez qui des crises photosensibles peuvent être déclenchées.

REMARQUE : La limitation de la zone et du nombre de flashs par seconde peut contribuer au respect de cette clause.

5.1.2.1 Fonctions restreintes

Lorsque les TIC ont des fonctions restreintes, elles doivent satisfaire aux exigences énoncées dans les clauses 5.2 à 13, selon le cas.

REMARQUE 1 : Les TIC peuvent restreindre certaines de ses fonctions, mais pas toutes. Seules les fonctions restreintes doivent se conformer aux exigences de la clause 5.1.

REMARQUE 2 : Les exigences de la présente clause remplacent celles des clauses 5.2 à 13 qui indiquent expressément qu’elles ne s’appliquent pas aux fonctions restreintes. Cela peut être dû au fait qu’elles concernent la compatibilité avec les technologies d’assistance ou la capacité de l’utilisateur de régler les paramètres d’accessibilité du système dans les produits aux fonctions restreintes (p. ex. les produits qui empêchent l’accès au panneau de commande des paramètres du système).

5.1.2.1 Fonctions restreintes

Lorsque les TIC ont des fonctions restreintes, elles doivent satisfaire aux exigences énoncées dans les clauses 5.2 à 13, selon le cas.

REMARQUE 1 : Les TIC peuvent restreindre certaines de ses fonctions, mais pas toutes. Seules les fonctions restreintes doivent se conformer aux exigences de la clause 5.1.

REMARQUE 2 : Les exigences de la présente clause remplacent celles des clauses 5.2 à 13 qui indiquent expressément qu’elles ne s’appliquent pas aux fonctions restreintes. Cela peut être dû au fait qu’elles concernent la compatibilité avec les technologies d’assistance ou la capacité de l’utilisateur de régler les paramètres d’accessibilité du système dans les produits aux fonctions restreintes (p. ex. les produits qui empêchent l’accès au panneau de commande des paramètres du système).

5.1.2.1 Fonctions restreintes

Lorsque les TIC ont des fonctions restreintes, elles doivent satisfaire aux exigences énoncées dans les clauses 5.2 à 13, selon le cas.

REMARQUE 1 : Les TIC peuvent restreindre certaines de ses fonctions, mais pas toutes. Seules les fonctions restreintes doivent se conformer aux exigences de la clause 5.1.

REMARQUE 2 : Les exigences de la présente clause remplacent celles des clauses 5.2 à 13 qui indiquent expressément qu’elles ne s’appliquent pas aux fonctions restreintes. Cela peut être dû au fait qu’elles concernent la compatibilité avec les technologies d’assistance ou la capacité de l’utilisateur de régler les paramètres d’accessibilité du système dans les produits aux fonctions restreintes (p. ex. les produits qui empêchent l’accès au panneau de commande des paramètres du système).

5.1.3.10 Sortie sonore non interférente

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC ne doivent pas lire automatiquement, en même temps, toute sortie audible interférente d’une durée supérieure à trois secondes.

5.1.3.10 Sortie sonore non interférente

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC ne doivent pas lire automatiquement, en même temps, toute sortie audible interférente d’une durée supérieure à trois secondes.

5.1.3.10 Sortie sonore non interférente

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC ne doivent pas lire automatiquement, en même temps, toute sortie audible interférente d’une durée supérieure à trois secondes.

5.1.3.10 Sortie sonore non interférente

Lorsque la sortie sonore est fournie en tant qu’accès non visuel à une fonction restreinte, les TIC ne doivent pas lire automatiquement, en même temps, toute sortie audible interférente d’une durée supérieure à trois secondes.

5.1.3.14 Langues parlées

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit être dans la même langue humaine que le contenu affiché fourni, sauf :

  1. pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement;
  2. lorsque le contenu est généré à l’extérieur et n’est pas sous le contrôle du fournisseur de TIC, La clause 5.1.3.14 n’est pas tenue de s’appliquer aux langues non prises en charge par le synthétiseur vocal de TIC;
  3. pour les langues affichées qui ne peuvent pas être sélectionnées à l’aide d’un accès non visuel;
  4. lorsque l’utilisateur choisit explicitement une langue vocale différente de la langue du contenu affiché.

5.1.3.14 Langues parlées

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit être dans la même langue humaine que le contenu affiché fourni, sauf :

  1. pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement;
  2. lorsque le contenu est généré à l’extérieur et n’est pas sous le contrôle du fournisseur de TIC, La clause 5.1.3.14 n’est pas tenue de s’appliquer aux langues non prises en charge par le synthétiseur vocal de TIC;
  3. pour les langues affichées qui ne peuvent pas être sélectionnées à l’aide d’un accès non visuel;
  4. lorsque l’utilisateur choisit explicitement une langue vocale différente de la langue du contenu affiché.

5.1.3.14 Langues parlées

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit être dans la même langue humaine que le contenu affiché fourni, sauf :

  1. pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement;
  2. lorsque le contenu est généré à l’extérieur et n’est pas sous le contrôle du fournisseur de TIC, la présente clause 5.1.3.14 n’est pas tenue de s’appliquer aux langues non prises en charge par le synthétiseur vocal de TIC;
  3. pour les langues affichées qui ne peuvent pas être sélectionnées à l’aide d’un accès non visuel;
  4. lorsque l’utilisateur choisit explicitement une langue vocale différente de la langue du contenu affiché.
Reformulation stylistique

5.1.3.14 Langues parlées

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte, la sortie vocale doit être dans la même langue humaine que le contenu affiché fourni, sauf :

  1. pour les noms propres, les termes techniques, les mots d’une langue indéterminée et les mots ou expressions qui font maintenant partie de la langue vernaculaire du texte qui les entoure immédiatement;
  2. lorsque le contenu est généré à l’extérieur et n’est pas sous le contrôle du fournisseur de TIC, la présente clause 5.1.3.14 n’est pas tenue de s’appliquer aux langues non prises en charge par le synthétiseur vocal de TIC;
  3. pour les langues affichées qui ne peuvent pas être sélectionnées à l’aide d’un accès non visuel;
  4. lorsque l’utilisateur choisit explicitement une langue vocale différente de la langue du contenu affiché.

5.1.3.15 Détermination non visuelle des erreurs

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte et qu’une erreur de saisie est automatiquement détectée, la sortie vocale doit identifier et décrire l’élément qui est en erreur.

5.1.3.15 Détermination non visuelle des erreurs

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte et qu’une erreur de saisie est automatiquement détectée, la sortie vocale doit identifier et décrire l’élément qui est en erreur.

5.1.3.15 Détermination non visuelle des erreurs

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte et qu’une erreur de saisie est automatiquement détectée, la sortie vocale doit identifier et décrire l’élément qui est en erreur.

5.1.3.15 Détermination non visuelle des erreurs

Lorsque la sortie vocale est fournie en tant qu’accès non visuel à une fonction restreinte et qu’une erreur de saisie est automatiquement détectée, la sortie vocale doit identifier et décrire l’élément qui est en erreur.

5.1.5 Sortie visuelle pour renseignement audio

Lorsque des renseignements audio préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, les TIC doivent fournir des renseignements visuels équivalents aux résultats sonores préenregistrés.

REMARQUE : Ce renseignement visuel peut prendre la forme de sous-titre ou de transcriptions textuelles.

5.1.5 Sortie visuelle pour renseignement audio

Lorsque des renseignements audio préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, les TIC doivent fournir des renseignements visuels équivalents aux résultats sonores préenregistrés.

REMARQUE : Ce renseignement visuel peut prendre la forme de sous-titre ou de transcriptions textuelles.

5.1.5 Sortie visuelle pour renseignement audio

Où des renseignements audio sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, les TIC doivent fournir des renseignements visuels équivalents aux résultats sonores.

REMARQUE : Ce renseignement visuel peut prendre la forme de sous-titre ou de transcriptions textuelles.

Reformulation stylistique

5.1.5 Sortie visuelle pour renseignement audio

Où des renseignements audio sont nécessaires pour permettre l’utilisation de fonctions restreintes des TIC, les TIC doivent fournir des renseignements visuels équivalents aux résultats sonores.

REMARQUE : Ce renseignement visuel peut prendre la forme de sous-titre ou de transcriptions textuelles.

5.1.6.1 Fonction restreinte

Lorsque la fonction des TIC est restreinte aux claviers ou aux interfaces clavier, toutes les fonctions doivent pouvoir fonctionner sans vision, comme l’exige la clause 5.1.3.

5.1.6.1 Fonction restreinte

Lorsque la fonction des TIC est restreinte aux claviers ou aux interfaces clavier, toutes les fonctions doivent pouvoir fonctionner sans vision, comme l’exige la clause 5.1.3.

5.1.6.1 Fonction restreinte

Lorsque la fonction des TIC est restreinte aux claviers ou aux interfaces clavier, toutes les fonctions doivent pouvoir fonctionner sans vision, comme l’exige la clause 5.1.3.

5.1.6.1 Fonction restreinte

Lorsque la fonction des TIC est restreinte aux claviers ou aux interfaces clavier, toutes les fonctions doivent pouvoir fonctionner sans vision, comme l’exige la clause 5.1.3.

5.1.6.2 Focus de la saisie

Lorsque la fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier et que le focus de la saisie peut être déplacé vers un élément d’interface utilisateur, il doit être possible d’éloigner le focus de la saisie de cet élément en utilisant le même mécanisme, afin d’éviter de piéger le focus de la saisie.

5.1.6.2 Focus de la saisie

Lorsque la fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier et que le focus de la saisie peut être déplacé vers un élément d’interface utilisateur, il doit être possible d’éloigner le focus de la saisie de cet élément en utilisant le même mécanisme, afin d’éviter de piéger le focus de la saisie.

5.1.6.2 Focus de la saisie

Lorsque la fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier et que le focus de la saisie peut être déplacé vers un élément d’interface utilisateur, il doit être possible d’éloigner le focus de la saisie cet élément en utilisant le même mécanisme, afin d’éviter de piéger le focus de la saisie.

5.1.6.2 Focus de la saisie

Lorsque la fonctionnalité des TIC est restreinte aux claviers ou aux interfaces clavier et que le focus de la saisie peut être déplacé vers un élément d’interface utilisateur, il doit être possible d’éloigner le focus de la saisie de cet élément en utilisant le même mécanisme, afin d’éviter de piéger le focus de la saisie.

55.1.7 Accès sans capacité vocale

Lorsque la capacité vocale est nécessaire pour faire fonctionner des fonctions restreintes des TIC, celles-ci doivent prévoir au moins un mode de fonctionnement utilisant un autre mécanisme de saisie ne nécessitant pas la capacité vocale.

Nouvelle exigence

55.1.7 Accès sans capacité vocale

Lorsque la capacité vocale est nécessaire pour faire fonctionner des fonctions restreintes des TIC, celles-ci doivent prévoir au moins un mode de fonctionnement utilisant un autre mécanisme de saisie ne nécessitant pas la capacité vocale.

6.2.1.1 Communication par TTR

Lorsque les TIC permettent la communication vocale bidirectionnelle pour un contexte d’utilisation particulière, les TIC permettent à un utilisateur de communiquer avec un autre utilisateur par TTR.

REMARQUE 1 : La capacité de TTR peut être réglée par défaut ou ajoutée.

REMARQUE 2 : La fourniture des communications par TTR peut nécessiter des services, du matériel ou des logiciels supplémentaires qui peuvent être fournis séparément ou ensemble.

6.2.1.1 Communication par TTR

Lorsque les TIC permettent la communication vocale bidirectionnelle pour un contexte d’utilisation particulière, les TIC permettent à un utilisateur de communiquer avec un autre utilisateur par TTR.

REMARQUE 1 : La capacité de TTR peut être réglée par défaut ou ajoutée.

REMARQUE 2 : La fourniture des communications par TTR peut nécessiter des services, du matériel ou des logiciels supplémentaires qui peuvent être fournis séparément ou ensemble.

6.2.1.1 Communication par TTR

Lorsque le mode des TIC prévoit un moyen de communication vocale bidirectionnelle, les TIC doivent fournir un moyen de communication vocale bidirectionnelle par TTR, sauf si cela nécessite des modifications de conception pour ajouter du matériel d'entrée ou de sortie aux TIC.

REMARQUE 1 : Cette exigence inclut les produits qui ne sont pas dotés de fonctionnalités d’affichage physique ou de saisie de texte mais qui ont la capacité de se connecter à des périphériques qui possèdent de telles fonctionnalités. Elle inclut également les TIC intermédiaires situés entre les points finaux de la communication.

REMARQUE 2 : Il n’est pas nécessaire d’ajouter : un écran matériel, un clavier matériel ou du matériel pour permettre de se connecter à un écran ou à un clavier, filaire ou sans fil, si ce matériel n’est normalement pas fourni.

REMARQUE 3 : Aux fins de l’interopérabilité, la Recommandation T.140 de l’UIT-T est largement utilisée.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

6.2.1.1 Communication par TTR

Lorsque le mode des TIC prévoit un moyen de communication vocale bidirectionnelle, les TIC doivent fournir un moyen de communication vocale bidirectionnelle par TTR, sauf si cela nécessite des modifications de conception pour ajouter du matériel d'entrée ou de sortie aux TIC.

REMARQUE 1 : Cette exigence inclut les produits qui ne sont pas dotés de fonctionnalités d’affichage physique ou de saisie de texte mais qui ont la capacité de se connecter à des périphériques qui possèdent de telles fonctionnalités. Elle inclut également les TIC intermédiaires situés entre les points finaux de la communication.

REMARQUE 2 : Il n’est pas nécessaire d’ajouter : un écran matériel, un clavier matériel ou du matériel pour permettre de se connecter à un écran ou à un clavier, filaire ou sans fil, si ce matériel n’est normalement pas fourni.

REMARQUE 3 : Aux fins de l’interopérabilité, la Recommandation T.140 de l’UIT-T est largement utilisée.

6.2.1.2 Voix et texte simultanés

Lorsque les TIC permettent la communication vocale bidirectionnelle pour un contexte d’utilisation particulière et permettent à un utilisateur de communiquer avec un autre utilisateur par TTR, elles prévoient un mécanisme permettant de choisir un mode de fonctionnement qui permet la communication vocale et textuelle simultanée.

REMARQUE : le fonctionnement simultané de la communication vocale et de la communication par TTR peut permettre que la communication par TTR remplace ou prenne en charge la communication vocale et d’autres renseignements tels que les numéros, les montants en devises et l’épellation des noms.

6.2.1.2 Voix et texte simultanés

Lorsque les TIC permettent la communication vocale bidirectionnelle pour un contexte d’utilisation particulière et permettent à un utilisateur de communiquer avec un autre utilisateur par TTR, elles prévoient un mécanisme permettant de choisir un mode de fonctionnement qui permet la communication vocale et textuelle simultanée.

REMARQUE : le fonctionnement simultané de la communication vocale et de la communication par TTR peut permettre que la communication par TTR remplace ou prenne en charge la communication vocale et d’autres renseignements tels que les numéros, les montants en devises et l’épellation des noms.

6.2.1.2 Voix et texte simultanés

Lorsque les TIC prévoient un moyen de communication vocale bidirectionnelle et permettent aux utilisateurs de communiquer par TTR, elles doivent permettre la communication vocale et textuelle simultanément par l’intermédiaire d’une connexion utilisateur unique.

REMARQUE 1 : Dans le cas d’une communication entre plusieurs participants, comme dans un système de conférence, il est permis (mais pas obligatoire ou nécessairement recommandé) que le TTR soit traité dans un champ d’affichage unique et que « la prise de parole à tour de rôle » soit nécessaire afin d’éviter toute confusion (de la même manière que la prise de parole à tour de rôle est requise pour ceux qui présentent ou parlent moyennant une capacité vocale).

REMARQUE 2 : Dans le cas d’une communication entre plusieurs participants, la pratique exemplaire consiste à lever la main pour que les utilisateurs de capacité vocale et les utilisateurs du TTR soient traités de la même manière, afin que les utilisateurs de capacité vocale et de TTR soient placés dans la même file d’attente.

REMARQUE 3 : Dans le cas d’un système de conférence entre plusieurs participants dont l’une des fonctions est le clavardage – le TTR (tout comme la capacité vocale) est généralement séparé de la fonction de clavardage pour que celle-ci n’interfère pas avec le TTR (c.-à-d. les personnes peuvent envoyer des messages dans la zone de clavardage pendant qu’une personne présente des renseignements ou parle avec le TTR – de la même manière que les personnes s’envoient des messages en utilisant la fonction de clavardage pendant que des personnes utilisent la capacité vocale pour parler). Les utilisateurs de TTR utiliseraient alors le TTR pour présenter des renseignements et la fonction de clavardage pour envoyer des messages pendant que les autres présentent des renseignements (par la capacité vocale ou le TTR).

REMARQUE 4 : La possibilité de faire fonctionner la capacité vocale et le TTR simultanément (et séparément de la fonction de clavardage) peut également permettre à la zone de TTR de prendre en charge le sous-titrage lorsque quelqu’un parle (et elle n’est donc pas utilisée pour le TTR puisque ce n’est pas au tour de l’utilisateur du TTR de prendre la parole).

REMARQUE 5 : Lorsque le logiciel côté serveur tout comme le matériel et les logiciels locaux sont nécessaires pour fournir la communication vocale, mais qu’aucune partie ne peut prendre en charge la communication vocale sans l’autre et qu’elles sont vendues comme une seule unité pour la fonction de communication vocale, les composants des logiciels locaux et du serveur sont considérés comme un seul produit.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

6.2.1.2 Voix et texte simultanés

Lorsque les TIC prévoient un moyen de communication vocale bidirectionnelle et permettent aux utilisateurs de communiquer par TTR, elles doivent permettre la communication vocale et textuelle simultanément par l’intermédiaire d’une connexion utilisateur unique.

REMARQUE 1 : Dans le cas d’une communication entre plusieurs participants, comme dans un système de conférence, il est permis (mais pas obligatoire ou nécessairement recommandé) que le TTR soit traité dans un champ d’affichage unique et que « la prise de parole à tour de rôle » soit nécessaire afin d’éviter toute confusion (de la même manière que la prise de parole à tour de rôle est requise pour ceux qui présentent ou parlent moyennant une capacité vocale).

REMARQUE 2 : Dans le cas d’une communication entre plusieurs participants, la pratique exemplaire consiste à lever la main pour que les utilisateurs de capacité vocale et les utilisateurs du TTR soient traités de la même manière, afin que les utilisateurs de capacité vocale et de TTR soient placés dans la même file d’attente.

REMARQUE 3 : Dans le cas d’un système de conférence entre plusieurs participants dont l’une des fonctions est le clavardage – le TTR (tout comme la capacité vocale) est généralement séparé de la fonction de clavardage pour que celle-ci n’interfère pas avec le TTR (c.-à-d. les personnes peuvent envoyer des messages dans la zone de clavardage pendant qu’une personne présente des renseignements ou parle avec le TTR – de la même manière que les personnes s’envoient des messages en utilisant la fonction de clavardage pendant que des personnes utilisent la capacité vocale pour parler). Les utilisateurs de TTR utiliseraient alors le TTR pour présenter des renseignements et la fonction de clavardage pour envoyer des messages pendant que les autres présentent des renseignements (par la capacité vocale ou le TTR).

REMARQUE 4 : La possibilité de faire fonctionner la capacité vocale et le TTR simultanément (et séparément de la fonction de clavardage) peut également permettre à la zone de TTR de prendre en charge le sous-titrage lorsque quelqu’un parle (et elle n’est donc pas utilisée pour le TTR puisque ce n’est pas au tour de l’utilisateur du TTR de prendre la parole).

REMARQUE 5 : Lorsque le logiciel côté serveur tout comme le matériel et les logiciels locaux sont nécessaires pour fournir la communication vocale, mais qu’aucune partie ne peut prendre en charge la communication vocale sans l’autre et qu’elles sont vendues comme une seule unité pour la fonction de communication vocale, les composants des logiciels locaux et du serveur sont considérés comme un seul produit.

6.2.2.1 Affichage visuellement reconnaissable

Lorsque les TIC sont dotées de capacités d’envoi et de réception de TTR, l’affichage du texte envoyé doit être visuellement différenciable et séparé de l’affichage du texte reçu.

6.2.2.1 Affichage visuellement reconnaissable

Lorsque les TIC sont dotées de capacités d’envoi et de réception de TTR, l’affichage du texte envoyé doit être visuellement différenciable et séparé de l’affichage du texte reçu.

6.2.2.1 Affichage visuellement reconnaissable

Lorsque les TIC sont dotées de capacités d’envoi et de réception de TTR, l’affichage du texte envoyé doit être visuellement différenciable et séparé de l’affichage du texte reçu.

REMARQUE : La possibilité pour l’utilisateur de choisir entre l’affichage du texte d’envoi et de réception sur une ligne ou séparément, et avec des options de sélection, permet aux utilisateurs d’afficher le TTR dans le format qui leur convient le mieux. Cela permettrait aux utilisateurs de texte en braille d’utiliser un seul champ et d’intervenir à tour de rôle, mais aussi de faire apparaître le texte de la manière séquentielle dont ils peuvent avoir besoin ou qu’ils préfèrent.

Mise à jour explicative

6.2.2.1 Affichage visuellement reconnaissable

Lorsque les TIC sont dotées de capacités d’envoi et de réception de TTR, l’affichage du texte envoyé doit être visuellement différenciable et séparé de l’affichage du texte reçu.

REMARQUE : La possibilité pour l’utilisateur de choisir entre l’affichage du texte d’envoi et de réception sur une ligne ou séparément, et avec des options de sélection, permet aux utilisateurs d’afficher le TTR dans le format qui leur convient le mieux. Cela permettrait aux utilisateurs de texte en braille d’utiliser un seul champ et d’intervenir à tour de rôle, mais aussi de faire apparaître le texte de la manière séquentielle dont ils peuvent avoir besoin ou qu’ils préfèrent.

6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Lorsque les TIC présentent des capacités d’envoi et de réception de TTR, la direction de l’envoi et de la réception du texte doit pouvoir être déterminée par un programme informatique, à moins que la fonction de TTR soit une fonctionnalité restreinte.

REMARQUE : Le but de la clause 6.2.2.2 est de permettre aux lecteurs d’écran de différencier le texte entrant du texte sortant lorsque la fonction de TTR est utilisée.

6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Lorsque les TIC présentent des capacités d’envoi et de réception de TTR, la direction de l’envoi et de la réception du texte doit pouvoir être déterminée par un programme informatique, à moins que la fonction de TTR soit une fonctionnalité restreinte.

REMARQUE : Le but de cette clause est de permettre aux lecteurs d’écran de différencier le texte entrant du texte sortant lorsque la fonction de TTR est utilisée.

Reformulation stylistique

6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Lorsque les TIC présentent des capacités d’envoi et de réception de TTR, la direction de l’envoi et de la réception du texte doit pouvoir être déterminée par un programme informatique, à moins que la fonction de TTR soit mise en œuvre en tant que fonctionnalité restreinte.

REMARQUE : Cette clause permet aux lecteurs d’écran de différencier le texte entrant du texte sortant lorsque la fonction de TTR est utilisée.

Changement fonctionnel

Reformulation stylistique

6.2.2.2 Direction d’envoi et de réception déterminable par un programme informatique

Lorsque les TIC présentent des capacités d’envoi et de réception de TTR, la direction de l’envoi et de la réception du texte doit pouvoir être déterminée par un programme informatique, à moins que la fonction de TTR soit mise en œuvre en tant que fonctionnalité restreinte.

REMARQUE : Cette clause permet aux lecteurs d’écran de différencier le texte entrant du texte sortant lorsque la fonction de TTR est utilisée.

6.2.2.3 Identification des interlocuteurs

Lorsque les TIC sont dotées de capacités de TTR et offrent l’identification des interlocuteurs par capacité vocale, elles doivent fournir l’identification des interlocuteurs pour le TTR.

REMARQUE : Cela est nécessaire pour permettre aux participants utilisant la fonction de capacité vocale comme ceux utilisant la fonction de TTR de savoir qui communique à un moment donné, que ce soit par TTR ou capacité vocale.

Nouvelle exigence

6.2.2.3 Identification des interlocuteurs

Lorsque les TIC sont dotées de capacités de TTR et offrent l’identification des interlocuteurs par capacité vocale, elles doivent fournir l’identification des interlocuteurs pour le TTR.

REMARQUE : Cela est nécessaire pour permettre aux participants utilisant la fonction de capacité vocale comme ceux utilisant la fonction de TTR de savoir qui communique à un moment donné, que ce soit par TTR ou capacité vocale.

6.2.2.4 Indicateur visuel de l’audio avec TTR

Lorsque les TIC prévoient une communication vocale bidirectionnelle et qu’elles sont dotées de capacités de TTR, elles doivent fournir un indicateur visuel en temps réel de l’activité audio à l’écran.

REMARQUE 1 : L’indicateur visuel peut être une position de caractère simple sur l’écran qui clignote pour refléter l’activité audio, ou la présentation des renseignements d’une autre manière qui peut être à la fois visible par les utilisateurs voyants et transmis aux utilisateurs sourds-aveugles qui utilisent un écran braille.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

Nouvelle exigence

6.2.2.4 Indicateur visuel de l’audio avec TTR

Lorsque les TIC prévoient une communication vocale bidirectionnelle et qu’elles sont dotées de capacités de TTR, elles doivent fournir un indicateur visuel en temps réel de l’activité audio à l’écran.

REMARQUE 1 : L’indicateur visuel peut être une position de caractère simple sur l’écran qui clignote pour refléter l’activité audio, ou la présentation des renseignements d’une autre manière qui peut être à la fois visible par les utilisateurs voyants et transmis aux utilisateurs sourds-aveugles qui utilisent un écran braille.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

6.2.3 Interopérabilité

Lorsque les TIC dotées d’une fonction de TTR fonctionnent avec d’autres TIC dotées d’une fonction de TTR (comme l’exige 6.2.1.1), elles doivent prendre en charge au moins un des quatre mécanismes d’interopérabilité de TTR décrits ci-dessous :

  1. l’interopérabilité des TIC sur le réseau téléphonique commuté (RTC), avec d’autres TIC qui se raccordent directement au RTC, comme le décrit la Recommandation V.18 de l’UIT-T ou l’une de ses annexes pour les signaux de téléphonie texte à l’interface du RTC;
  2. l’interopérabilité des TIC avec d’autres TIC à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initiation de session (SIP) et du texte en temps réel conforme à RFC 4103;
  3. l’interopérabilité des TIC avec d’autres TIC dotées de TTR conformes aux protocoles du sous-système multimédia IP (IMS) conformément aux spécifications TS 126 114, TS 122 173 et TS 134 229;
  4. l’interopérabilité des TIC avec d’autres TIC utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible. Cette spécification commune comprend une méthode permettant d’indiquer la perte ou la corruption de caractères.

6.2.3 Interopérabilité

Lorsque les TIC dotées d’une fonction de TTR fonctionnent avec d’autres TIC dotées d’une fonction de TTR (comme l’exige la clause 6.2.1.1), elles doivent prendre en charge au moins un des quatre mécanismes d’interopérabilité de TTR décrits ci-dessous :

  1. l’interopérabilité des TIC sur le réseau téléphonique commuté (RTC), avec d’autres TIC qui se raccordent directement au RTC, comme le décrit la Recommandation V.18 de l’UIT-T ou l’une de ses annexes pour les signaux de téléphonie texte à l’interface du RTC;
  2. l’interopérabilité des TIC avec d’autres TIC à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initiation de session (SIP) et du texte en temps réel conforme à RFC 4103 de l’IETF;
  3. l’interopérabilité des TIC avec d’autres TIC dotées de TTR conformes aux protocoles du sous-système multimédia IP (IMS) conformément aux spécifications TS 126 114, TS 122 173 et TS 134 229 de l’ETSI;
  4. l’interopérabilité des TIC avec d’autres TIC utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible. Cette spécification commune comprend une méthode permettant d’indiquer la perte ou la corruption de caractères.

Reformulation stylistique

Mise à jour explicative

6.2.3 Interopérabilité

Lorsque les TIC dotées d’une fonction de TTR fonctionnent avec d’autres TIC dotées d’une fonction de TTR (comme l’exige la clause 6.2.1.1), elles doivent prendre en charge au moins un des quatre mécanismes d’interopérabilité de TTR applicables décrits ci-dessous :

  1. l’interopérabilité des TIC avec d’autres TIC raccordées directement au réseau téléphonique commuté (RTC), utilisant la Recommandation V.18 de l’UIT-T ou l’une de ses annexes pour les signaux de téléphonie texte à l’interface du RTC;
  2. l’interopérabilité des TIC avec d’autres TIC à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initiation de session (SIP) et du TTR en temps réel conforme à RFC 4103. Pour l’interopérabilité des TIC avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, l’ensemble des protocoles spécifiés dans TS 126 114, TS 122 173 et TS 134 229 de l’ETSI décrivent la façon dont RFC 4103 de l’IETF s’appliquerait;
  3. l’interopérabilité des TIC avec d’autres TIC utilisant des technologies autres que a ou b, ci-dessus, utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible pour les environnements dans lesquels ils fonctionneront. Cette spécification commune comprend une méthode permettant d’indiquer la perte ou la corruption de caractères.
  4. l’interopérabilité des TIC avec d’autres TIC utilisant une norme pour TTR qui a été mise en place aux fins d’utilisation dans un des environnements susmentionnés, et qui est compatible avec toutes les autres TIC actives qui prennent en charge la capacité vocale et le TTR dans l’environnement en question.

REMARQUE 1 : En pratique, de nouvelles normes sont mises en place comme un autre codec ou protocole, pris en charge parallèlement à la norme commune existante et utilisé lorsqu’il est compatible avec tous les composants de bout en bout, lorsque le développement technologique, associé à d’autres raisons, dont le développement sociétal et la rentabilité, peut rendre d’autres normes obsolètes.

REMARQUE 2 : Lorsque plusieurs technologies sont utilisées pour fournir la communication vocale, plusieurs mécanismes d’interopérabilité peuvent être nécessaires pour garantir que tous les utilisateurs peuvent utiliser le TTR.

EXEMPLE : Un système de conférence prenant en charge la communication vocale par une connexion Internet peut fournir une communication par TTR par une connexion Internet au moyen d’une méthode TTR exclusive (option c). Toutefois, que la méthode TTR soit libre ou exclusive, si le système de conférence offre aussi la communication par téléphone, il devra également prendre en charge les options a ou b pour garantir que le TTR est pris en charge par la connexion par téléphone.

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

6.2.3 Interopérabilité

Lorsque les TIC dotées d’une fonction de TTR fonctionnent avec d’autres TIC dotées d’une fonction de TTR (comme l’exige la clause 6.2.1.1), elles doivent prendre en charge au moins un des quatre mécanismes d’interopérabilité de TTR applicables décrits ci-dessous :

  1. l’interopérabilité des TIC avec d’autres TIC raccordées directement au réseau téléphonique commuté (RTC), utilisant la Recommandation V.18 de l’UIT-T [i.23] ou l’une de ses annexes pour les signaux de téléphonie texte à l’interface du RTC;
  2. l’interopérabilité des TIC avec d’autres TIC à l’aide de la technologie Voix sur IP (VoIP) dotée du protocole d’initiation de session (SIP) et du TTR en temps réel conforme à RFC 4103 [i.13] . Pour l’interopérabilité des TIC avec d’autres TIC utilisant le sous-système multimédia IP (IMS) pour mettre en œuvre VoIP, l’ensemble des protocoles spécifiés dans TS 126 114 [i.10], TS 122 173 [i.11] et TS 134 229 [i.12] de l’ETSI décrivent la façon dont RFC 4103 [i.13] de l’IETF s’appliquerait;
  3. l’interopérabilité des TIC avec d’autres TIC utilisant des technologies autres que a ou b, ci-dessus, utilisant une spécification commune pertinente et applicable pour les échanges de TTR qui est publiée et accessible pour les environnements dans lesquels ils fonctionneront. Cette spécification commune comprend une méthode permettant d’indiquer la perte ou la corruption de caractères;
  4. l’interopérabilité des TIC avec d’autres TIC utilisant une norme pour TTR qui a été mise en place aux fins d’utilisation dans un des environnements susmentionnés, et qui est compatible avec toutes les autres TIC actives qui prennent en charge la capacité vocale et le TTR dans l’environnement en question.

REMARQUE 1 : En pratique, de nouvelles normes sont mises en place comme un autre codec ou protocole, pris en charge parallèlement à la norme commune existante et utilisé lorsqu’il est compatible avec tous les composants de bout en bout, lorsque le développement technologique, associé à d’autres raisons, dont le développement sociétal et la rentabilité, peut rendre d’autres normes obsolètes.

REMARQUE 2 : Lorsque plusieurs technologies sont utilisées pour fournir la communication vocale, plusieurs mécanismes d’interopérabilité peuvent être nécessaires pour garantir que tous les utilisateurs peuvent utiliser le TTR.

EXEMPLE : Un système de conférence prenant en charge la communication vocale par une connexion Internet peut fournir une communication par TTR par une connexion Internet au moyen d’une méthode TTR exclusive (option c). Toutefois, que la méthode TTR soit libre ou exclusive, si le système de conférence offre aussi la communication par téléphone, il devra également prendre en charge les options a ou b pour garantir que le TTR est pris en charge par la connexion par téléphone.

6.2.4 Réactivité du texte en temps réel

Lorsque les TIC permettent la saisie de TTR, cette saisie est transmise au réseau des TIC prenant en charge le TTR dans un délai d’une seconde après la saisie.

REMARQUE 1 : La saisie est considérée comme ayant été exécutée lorsque l’utilisateur a saisi suffisamment de caractères pour que les TIC établissent quels caractères envoyer.

REMARQUE 2 : La saisie différera selon que le système permet d’entrer le texte mot par mot (p. ex., la conversion de la voix en texte et la saisie du texte prédictif) ou d’entrer un caractère à la fois.

6.2.4 Réactivité du texte en temps réel

Lorsque les TIC permettent la saisie de TTR, cette saisie est transmise au réseau des TIC prenant en charge le TTR dans un délai d’une seconde après la saisie.

REMARQUE 1 : La saisie est considérée comme ayant été exécutée lorsque l’utilisateur a saisi suffisamment de caractères pour que les TIC établissent quels caractères envoyer.

REMARQUE 2 : La saisie différera selon que le système permet d’entrer le texte mot par mot (p. ex., la conversion de la voix en texte et la saisie du texte prédictif) ou d’entrer un caractère à la fois.

6.2.4 Réactivité du TTR

Lorsque les TIC permettent la saisie de TTR, cette saisie est transmise au réseau des TIC ou à la plateforme sur laquelle fonctionnent les TIC dans un délai de 500 ms à compter du moment où la plus petite unité de saisie de texte fiable est accessible aux TIC aux fins de transmission. Les retards attribuables à la performance de la plateforme ou du réseau ne doivent pas être inclus dans la limite de 500 ms.

REMARQUE 1 : Pour la saisie de caractère par caractère, la « plus petite unité de saisie de texte fiable » serait un caractère.

Pour la prédiction des mots, ce serait un mot. Pour certains systèmes de reconnaissance vocale, le texte peut ne pas quitter le logiciel de reconnaissance tant qu’un mot entier (ou une expression entière) n’a pas été prononcé. Dans ce cas, la plus petite unité de saisie de texte fiable accessible aux TIC serait le mot (ou l’expression).

REMARQUE 2 : La limite de 500 ms permet de conserver en mémoire tampon les caractères avant leur transmission de sorte que la transmission caractère par caractère ne soit pas nécessaire à moins que les caractères soient générés plus lentement que 1 caractère par 500 ms.

REMARQUE 3 : Un délai de 300 ms, ou moins, produit une meilleure impression de fluidité pour l'utilisateur.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

6.2.4 Réactivité du TTR

Lorsque les TIC permettent la saisie de TTR, cette saisie est transmise au réseau des TIC ou à la plateforme sur laquelle fonctionnent les TIC dans un délai de 500 ms à compter du moment où la plus petite unité de saisie de texte fiable est accessible aux TIC aux fins de transmission. Les retards attribuables à la performance de la plateforme ou du réseau ne doivent pas être inclus dans la limite de 500 ms.

REMARQUE 1 : Pour la saisie de caractère par caractère, la « plus petite unité de saisie de texte fiable » serait un caractère.

Pour la prédiction des mots, ce serait un mot. Pour certains systèmes de reconnaissance vocale, le texte peut ne pas quitter le logiciel de reconnaissance tant qu’un mot entier (ou une expression entière) n’a pas été prononcé. Dans ce cas, la plus petite unité de saisie de texte fiable accessible aux TIC serait le mot (ou l’expression).

REMARQUE 2 : La limite de 500 ms permet de conserver en mémoire tampon les caractères avant leur transmission de sorte que la transmission caractère par caractère ne soit pas nécessaire à moins que les caractères soient générés plus lentement que 1 caractère par 500 ms.

REMARQUE 3 : Un délai de 300 ms, ou moins, produit une meilleure impression de fluidité pour l'utilisateur.

6.4 Autres solutions de services vocaux

Lorsque les TIC permettent la communication vocale en temps réel ainsi que la messagerie vocale, la réception automatique ou la réponse vocale interactive, elles devraient permettre à l’utilisateur d’accéder aux renseignements et d’exécuter les tâches sans recourir à l’ouïe ou à la parole.

REMARQUE : Des solutions permettant de traiter les supports sons, texte et vidéo en temps réel pourraient répondre au besoin susmentionné.

6.4 Autres solutions de services vocaux

Lorsque les TIC permettent la communication vocale en temps réel ainsi que la messagerie vocale, la réception automatique ou la réponse vocale interactive, elles devraient permettre à l’utilisateur d’accéder aux renseignements et d’exécuter les tâches sans recourir à l’ouïe ou à la parole.

REMARQUE : Des solutions permettant de traiter les supports sons, texte et vidéo en temps réel pourraient répondre au besoin susmentionné.

6.4 Autres solutions de services vocaux

Lorsque les TIC permettent la communication vocale en temps réel ainsi que la messagerie vocale, la réception automatique ou la réponse vocale interactive, elles doivent permettre à l’utilisateur d’accéder aux renseignements et d’exécuter les tâches sans recourir à l’ouïe ou à la parole.

REMARQUE 1 : Les tâches qui impliquent à la fois l’utilisation de l'interface et la perception des renseignements exigeraient que l'interface et les renseignements soient accessibles sans recourir à la parole ou à l’ouïe.

REMARQUE 2 : Des solutions permettant de traiter les supports sons, TTR et vidéo en temps réel pourraient répondre au besoin susmentionné.

Changement fonctionnel

Mise à jour explicative

Reformulation stylistique

6.4 Autres solutions de services vocaux

Lorsque les TIC permettent la communication vocale en temps réel ainsi que la messagerie vocale, la réception automatique ou la réponse vocale interactive, elles doivent permettre à l’utilisateur d’accéder aux renseignements et d’exécuter les tâches sans recourir à l’ouïe ou à la parole.

REMARQUE 1 : Les tâches qui impliquent à la fois l’utilisation de l'interface et la perception des renseignements exigeraient que l'interface et les renseignements soient accessibles sans recourir à la parole ou à l’ouïe.

REMARQUE 2 : Des solutions permettant de traiter les supports sons, TTR et vidéo en temps réel pourraient répondre au besoin susmentionné.

6.5.5 Indicateur visuel de l’audio avec vidéo

Lorsque les TIC prévoient une communication vocale bidirectionnelle et qu’elles comprennent une fonctionnalité de vidéo en temps réel, elles doivent fournir un indicateur visuel en temps réel de l’activité audio.

REMARQUE 1 : L’indicateur visuel peut être un simple point visuel ou lumière LED, ou d’autre type d’indicateur marche-arrêt, qui clignote pour refléter l’activité audio.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

Nouvelle exigence

6.5.5 Indicateur visuel de l’audio avec vidéo

Lorsque les TIC prévoient une communication vocale bidirectionnelle et qu’elles comprennent une fonctionnalité de vidéo en temps réel, elles doivent fournir un indicateur visuel en temps réel de l’activité audio.

REMARQUE 1 : L’indicateur visuel peut être un simple point visuel ou lumière LED, ou d’autre type d’indicateur marche-arrêt, qui clignote pour refléter l’activité audio.

REMARQUE 2 : Sans cette indication, une personne qui n’a pas la capacité d’entendre ne sait pas quand quelqu’un parle.

6.5.6 Identification des interlocuteurs avec communication vidéo (langue des signes)

Lorsque les TIC prévoient une fonction d’identification des interlocuteurs pour les utilisateurs de la capacité vocale, elles doivent fournir un moyen d’identification des interlocuteurs pour les utilisateurs de signes en temps réel et de langage des signes dès qu’il est indiqué que des signes sont utilisés.

REMARQUE 1 : L’ID des interlocuteurs peut se trouver au même emplacement que celui des utilisateurs de capacité vocale dans le cas des appels avec plusieurs interlocuteurs.

REMARQUE 2 : Ce mécanisme peut être déclenché manuellement par un utilisateur ou automatiquement lorsque cela est techniquement réalisable.

Nouvelle exigence

6.5.6 Identification des interlocuteurs avec communication vidéo (langue des signes)

Lorsque les TIC prévoient une fonction d’identification des interlocuteurs pour les utilisateurs de la capacité vocale, elles doivent fournir un moyen d’identification des interlocuteurs pour les utilisateurs de signes en temps réel et de langage des signes dès qu’il est indiqué que des signes sont utilisés.

REMARQUE 1 : L’ID des interlocuteurs peut se trouver au même emplacement que celui des utilisateurs de capacité vocale dans le cas des appels avec plusieurs interlocuteurs.

REMARQUE 2 : Ce mécanisme peut être déclenché manuellement par un utilisateur ou automatiquement lorsque cela est techniquement réalisable.

6.6 Autres solutions de services vidéo

Lorsque les TIC sont dotées de la communication vidéo en temps réel ainsi que d’un répondeur, d’un standard automatique ou de moyens de réponse interactifs, elles doivent permettre aux utilisateurs d’accéder aux renseignements et d’exécuter les tâches liées à ces moyens :

  1. pour des renseignements audibles, sans recourir à l’ouïe;
  2. pour les commandes vocales, sans recourir à la parole;
  3. pour les renseignements visuels, sans recourir à la vision.

REMARQUE : Les solutions pouvant produire des sous-titres en temps réel ou traiter du texte en temps réel pourraient répondre au besoin susmentionné.

6.6 Autres solutions de services vidéo

Lorsque les TIC sont dotées de la communication vidéo en temps réel ainsi que d’un répondeur, d’un standard automatique ou de moyens de réponse interactifs, elles doivent permettre aux utilisateurs d’accéder aux renseignements et d’exécuter les tâches liées à ces moyens :

  1. pour des renseignements audibles, sans recourir à l’ouïe;
  2. pour les commandes vocales, sans recourir à la parole;
  3. pour les renseignements visuels, sans recourir à la vision.

REMARQUE : Les solutions pouvant produire des sous-titres en temps réel ou traiter du texte en temps réel pourraient répondre au besoin susmentionné.

6.6 Autres solutions de services vidéo

Lorsque les TIC sont dotées de la communication vidéo en temps réel ainsi que d’un répondeur, d’un standard automatique ou de moyens de réponse interactifs, elles doivent permettre aux utilisateurs d’accéder aux renseignements et d’exécuter les tâches liées à ces moyens :

  1. pour des renseignements audibles, sans recourir à l’ouïe;
  2. pour les commandes vocales, sans recourir à la parole;
  3. pour les renseignements visuels, sans recourir à la vision.

REMARQUE : Les solutions pouvant produire des sous-titres en temps réel ou traiter du TTR pourraient répondre au besoin susmentionné.

Reformulation stylistique

6.6 Autres solutions de services vidéo

Lorsque les TIC sont dotées de la communication vidéo en temps réel ainsi que d’un répondeur, d’un standard automatique ou de moyens de réponse interactifs, elles doivent permettre aux utilisateurs d’accéder aux renseignements et d’exécuter les tâches liées à ces moyens :

  1. pour des renseignements audibles, sans recourir à l’ouïe;
  2. pour les commandes vocales, sans recourir à la parole;
  3. pour les renseignements visuels, sans recourir à la vision.

REMARQUE : Les solutions pouvant produire des sous-titres en temps réel ou traiter du TTR pourraient répondre au besoin susmentionné.

7.1.2 Synchronisation des sous-titres

Lorsque les TIC affichent des sous-titres, le mécanisme d’affichage des sous-titres doit préserver la synchronisation entre le son et les sous-titres correspondants.

7.1.2 Synchronisation des sous-titres

Lorsque les TIC affichent des sous-titres, le mécanisme d’affichage des sous-titres doit préserver la synchronisation entre le son et les sous-titres correspondants.

7.1.2 Synchronisation des sous-titres

Lorsque les TIC affichent des sous-titres, le mécanisme d’affichage des sous-titres doit préserver la synchronisation entre le son et les sous-titres correspondants comme suit :

  • Sous-titres dans le matériel enregistré : dans les 100 ms de l’horodatage du sous-titre.
  • Sous-titres en direct : dans les 100 ms suivant la disponibilité du sous-titre pour le lecteur.
Changement fonctionnel

7.1.2 Synchronisation des sous-titres

Lorsque les TIC affichent des sous-titres, le mécanisme d’affichage des sous-titres doit préserver la synchronisation entre le son et les sous-titres correspondants comme suit :

  • Sous-titres dans le matériel enregistré : dans les 100 ms de l’horodatage du sous-titre.
  • Sous-titres en direct : dans les 100 ms suivant la disponibilité du sous-titre pour le lecteur.

7.1.4 Caractéristiques des sous-titres

Lorsque les TIC affichent des sous-titres, elles doivent permettre à l’utilisateur d’adapter les caractéristiques affichées des sous-titres à ses besoins individuels, sauf lorsque les sous-titres sont affichés sous forme de caractères non modifiables.

REMARQUE 1 : La définition de la couleur d’arrière-plan et d’avant-plan des sous-titres, du type de police, de l’opacité de la zone d’arrière-plan des sous-titres et du contour ou de la bordure des polices peut contribuer à répondre à cette exigence.

REMARQUE 2 : Les sous-titres qui sont des images bitmap sont des exemples de caractères non modifiables.

Nouvelle exigence

7.1.4 Caractéristiques des sous-titres

Lorsque les TIC affichent des sous-titres, elles doivent permettre à l’utilisateur d’adapter les caractéristiques affichées des sous-titres à ses besoins individuels, sauf lorsque les sous-titres sont affichés sous forme de caractères non modifiables.

REMARQUE 1 : La définition de la couleur d’arrière-plan et d’avant-plan des sous-titres, du type de police, de l’opacité de la zone d’arrière-plan des sous-titres et du contour ou de la bordure des polices peut contribuer à répondre à cette exigence.

REMARQUE 2 : Les sous-titres qui sont des images bitmap sont des exemples de caractères non modifiables.

7.1.5 Sous-titres vocaux

Lorsque les TIC affichent des vidéos avec son synchronisé, elles doivent fournir un mode de fonctionnement qui fournit une sortie vocale pour les sous-titres disponibles, sauf lorsque le contenu des sous-titres affichés ne peut être déterminé par programmation.

REMARQUE 1 : Il est préférable pour la plupart des utilisateurs de pouvoir gérer la gamme de sortie vocale pour les sous-titres vocaux indépendamment de la capacité vocale générale des TIC. Cela est possible lorsque le fichier audio avec sous-titres vocaux est reçu dans une piste audio distincte puis mixé sur l’appareil des utilisateurs finaux.

REMARQUE 2 : Présenter la piste audio distincte avec des sous-titres vocaux en synchronisme avec les sous-titres affichés améliore la compréhension des sous-titres.

REMARQUE 3 : Fournir les sous-titres sous forme de flux de texte distincts facilite la conversion des textes respectifs en audio.

REMARQUE 4 : Les sous-titres qui sont des images bitmap sont des exemples pour lesquels le contenu de sous-titres affichés ne peut pas être déterminé par programmation.

Nouvelle exigence

7.1.5 Sous-titres vocaux

Lorsque les TIC affichent des vidéos avec son synchronisé, elles doivent fournir un mode de fonctionnement qui fournit une sortie vocale pour les sous-titres disponibles, sauf lorsque le contenu des sous-titres affichés ne peut être déterminé par programmation.

REMARQUE 1 : Il est préférable pour la plupart des utilisateurs de pouvoir gérer la gamme de sortie vocale pour les sous-titres vocaux indépendamment de la capacité vocale générale des TIC. Cela est possible lorsque le fichier audio avec sous-titres vocaux est reçu dans une piste audio distincte puis mixé sur l’appareil des utilisateurs finaux.

REMARQUE 2 : Présenter la piste audio distincte avec des sous-titres vocaux en synchronisme avec les sous-titres affichés améliore la compréhension des sous-titres.

REMARQUE 3 : Fournir les sous-titres sous forme de flux de texte distincts facilite la conversion des textes respectifs en audio.

REMARQUE 4 : Les sous-titres qui sont des images bitmap sont des exemples pour lesquels le contenu de sous-titres affichés ne peut pas être déterminé par programmation.

7.2.1 Lecture de la description audio

Lorsque les TIC affichent des vidéos avec du son synchronisé, elles doivent fournir un mécanisme permettant de sélectionner et de lire la description audio disponible sur le canal audio par défaut.

Lorsque les technologies vidéo ne disposent pas de mécanismes explicites et distincts pour la description audio, une TIC est réputée satisfaire à cette exigence si elle permet à l'utilisateur de sélectionner et de lire plusieurs pistes audio.

REMARQUE 1 : Dans ce cas, le contenu vidéo peut inclure la description audio comme l’une des pistes audio disponibles.

REMARQUE 2 : Les descriptions audio dans les médias numériques comprennent parfois des informations permettant des descriptions plus longues que les intervalles entre les dialogues. La prise en charge de cette fonction de « description audio étendue » par les lecteurs de médias numériques est utile, en particulier pour les médias numériques qui sont visionnés personnellement.

7.2.1 Lecture de la description audio

Lorsque les TIC affichent des vidéos avec du son synchronisé, elles doivent fournir un mécanisme permettant de sélectionner et de lire la description audio disponible sur le canal audio par défaut.

Lorsque les technologies vidéo ne disposent pas de mécanismes explicites et distincts pour la description audio, une TIC est réputée satisfaire à cette exigence si elle permet à l'utilisateur de sélectionner et de lire plusieurs pistes audio.

REMARQUE 1 : Dans ce cas, le contenu vidéo peut inclure la description audio comme l’une des pistes audio disponibles.

REMARQUE 2 : Les descriptions audio dans les médias numériques comprennent parfois des informations permettant des descriptions plus longues que les intervalles entre les dialogues. La prise en charge de cette fonction de « description audio étendue » par les lecteurs de médias numériques est utile, en particulier pour les médias numériques qui sont visionnés personnellement.

7.2.1 Lecture de la description audio

Lorsque les TIC affichent des vidéos avec du son synchronisé, elles doivent fournir un mécanisme permettant de sélectionner et de lire la description audio disponible sur le canal audio par défaut.

Lorsque les technologies vidéo ne disposent pas de mécanismes explicites et distincts pour la description audio, une TIC est réputée satisfaire à cette exigence si elle permet à l'utilisateur de sélectionner et de lire plusieurs pistes audio.

REMARQUE 1 : Dans ce cas, le contenu vidéo peut inclure la description audio comme l’une des pistes audio disponibles.

REMARQUE 2 : Les descriptions audio dans les médias numériques comprennent parfois des informations permettant des descriptions plus longues que les intervalles entre les dialogues. La prise en charge de cette fonction de « description audio étendue » par les lecteurs de médias numériques est utile, en particulier pour les médias numériques qui sont visionnés personnellement.

7.2.1 Lecture de la description audio

Lorsque les TIC affichent des vidéos avec du son synchronisé, elles doivent fournir un mécanisme permettant de sélectionner et de lire la description audio disponible sur le canal audio par défaut.

Lorsque les technologies vidéo ne disposent pas de mécanismes explicites et distincts pour la description audio, une TIC est réputée satisfaire à cette exigence si elle permet à l'utilisateur de sélectionner et de lire plusieurs pistes audio.

REMARQUE 1 : Dans ce cas, le contenu vidéo peut inclure la description audio comme l’une des pistes audio disponibles.

REMARQUE 2 : Les descriptions audio dans les médias numériques comprennent parfois des informations permettant des descriptions plus longues que les intervalles entre les dialogues. La prise en charge de cette fonction de « description audio étendue » par les lecteurs de médias numériques est utile, en particulier pour les médias numériques qui sont visionnés personnellement.

7.2.2 Synchronisation de la description audio

Lorsque les TIC prévoient un mécanisme de lecture de la description audio, celui-ci doit préserver la synchronisation entre le contenu audio/visuel et la description audio correspondante.

7.2.2 Synchronisation de la description audio

Lorsque les TIC prévoient un mécanisme de lecture de la description audio, celui-ci doit préserver la synchronisation entre le contenu audio/visuel et la description audio correspondante.

7.2.2 Synchronisation de la description audio

Lorsque les TIC prévoient un mécanisme de lecture de la description audio, celui-ci doit préserver la synchronisation entre le contenu audio/visuel et la description audio correspondante.

7.2.2 Synchronisation de la description audio

Lorsque les TIC prévoient un mécanisme de lecture de la description audio, celui-ci doit préserver la synchronisation entre le contenu audio/visuel et la description audio correspondante.

8.3.0 Généralités

Le présent document définit les dimensions pour accéder aux TIC fixes qui peuvent être placées dans un environnement bâti, mais ne définit pas les normes de l’environnement bâti en général.

Le champ d’application inclut les TIC fixes, dont les planchers et les espaces de circulation font « partie intégrante » (généralement les kiosques et les cabines), et où il existe des plages de portée externe qui sont importantes pour le fonctionnement des TIC fixes.

Les clauses 8.3.2 à 8.3.4 précisent les limites obligatoires pour la hauteur maximale et minimale des pièces manœuvrables et des écrans.

Selon les dimensions indiquées à la figure 53 de la norme ISO 21542:2011, il est recommandé que la portée possible en hauteur soit ramenée :

  • aux hauteurs minimale et maximale des pièces manœuvrables : 800 mm et 1 100 mm respectivement, et
  • aux hauteurs minimale et maximale des écrans : 1 200 mm et 1 400 mm respectivement.
Nouvelle exigence

8.3.0 Généralités

Le présent document définit les dimensions pour accéder aux TIC fixes qui peuvent être placées dans un environnement bâti, mais ne définit pas les normes de l’environnement bâti en général.

Le champ d’application inclut les TIC fixes, dont les planchers et les espaces de circulation font « partie intégrante » (généralement les kiosques et les cabines), et où il existe des plages de portée externe qui sont importantes pour le fonctionnement des TIC fixes.

Les clauses 8.3.2 à 8.3.4 précisent les limites obligatoires pour la hauteur maximale et minimale des pièces manœuvrables et des écrans.

Selon les dimensions indiquées à la figure 53 de la norme ISO 21542:2011, il est recommandé que la portée possible en hauteur soit ramenée :

  • aux hauteurs minimale et maximale des pièces manœuvrables : 800 mm et 1 100 mm respectivement, et
  • aux hauteurs minimale et maximale des écrans : 1 200 mm et 1 400 mm respectivement.

8.3.2.1 Changement de niveau

Lorsqu’un dénivelé de plancher fait partie intégrante des TIC, une rampe présentant une pente d’au plus 1 : 48 doit être aménagée.

Exceptions

  1. Si le dénivelé est inférieur ou égal à 6,4 mm (¼ po), le dénivelé peut être vertical.
  2. Si le dénivelé est inférieur ou égal à 13 mm (½ po), le dénivelé peut présenter une pente d’au plus 1 : 2.

8.3.2.1 Changement de niveau

Lorsqu’un dénivelé de plancher fait partie intégrante des TIC, une rampe présentant une pente d’au plus 1 : 48 doit être aménagée.

Exceptions

  1. Si le dénivelé est inférieur ou égal à 6,4 mm (¼ po), le dénivelé peut être vertical.
  2. Si le dénivelé est inférieur ou égal à 13 mm (½ po), le dénivelé peut présenter une pente d’au plus 1 : 2.

8.3.4.1 Changement de niveau

Lorsque des TIC fixes comportent un plancher, tout dénivelé de plancher qui y est intégré doit être aménagé d’une rampe présentant une pente d’au plus 1 : 48.

Exceptions

  1. Si le dénivelé est inférieur ou égal à 6,4 mm (¼ po), le dénivelé peut être vertical.
  2. Si le dénivelé est inférieur ou égal à 13 mm (½ po), le dénivelé peut présenter une pente d’au plus 1 : 2.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.1 Changement de niveau

Lorsque des TIC fixes comportent un plancher, tout dénivelé de plancher qui y est intégré doit être aménagé d’une rampe présentant une pente d’au plus 1 : 48.

Exceptions

  1. Si le dénivelé est inférieur ou égal à 6,4 mm (¼ po), le dénivelé peut être vertical comme il est illustré à la figure 8.
  2. Si le dénivelé est inférieur ou égal à 13 mm (½ po), le dénivelé peut présenter une pente d’au plus 1 : 2.

8.3.2.3.1 Généralités

Lorsque l’espace d’accès fait partie intégrante des TIC, au moins un côté complet de l’espace doit être dégagé.

8.3.2.3.1 Généralités

Lorsque l’espace d’accès fait partie intégrante des TIC, au moins un côté complet de l’espace doit être dégagé.

8.3.4.3.1 Généralités

Lorsque des TIC fixes comportent un espace d’accès, au moins un côté complet de l’espace doit être dégagé.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.3.1 Généralités

Lorsque des TIC fixes comportent un espace d’accès, au moins un côté complet de l’espace doit être dégagé.

8.3.2.3.2 Approche avant

Lorsque l’espace opérationnel se trouve dans une alcôve faisant partie intégrante des TIC, la profondeur de l’alcôve est supérieure à 610 mm (24 po), et lorsqu’une approche avant est nécessaire, l’espace d’accès doit être d’au moins 915 mm (36 po) de largeur.

8.3.2.3.2 Approche avant

Lorsque l’espace opérationnel se trouve dans une alcôve faisant partie intégrante des TIC, la profondeur de l’alcôve est supérieure à 610 mm (24 po), et lorsqu’une approche avant est nécessaire, l’espace d’accès doit être d’au moins 915 mm (36 po) de largeur.

8.3.4.3.2 Approche avant

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 610 mm (24 po), et lorsqu’une approche avant est nécessaire, l’espace d’accès doit être d’au moins 915 mm (36 po) de largeur.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.3.2 Approche avant

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 610 mm (24 po), et lorsqu’une approche avant est nécessaire, l’espace d’accès doit être d’au moins 915 mm (36 po) de largeur.

8.3.2.3.3 Approche parallèle

Lorsque l’espace opérationnel se trouve dans une alcôve faisant partie intégrante des TIC, la profondeur de l’alcôve est supérieure à 380 mm (15 po), et lorsqu’une approche parallèle est nécessaire, l’espace d’accès devrait être d’au moins 1 525 mm (60 po) de largeur.

8.3.2.3.3 Approche parallèle

Lorsque l’espace opérationnel se trouve dans une alcôve faisant partie intégrante des TIC, la profondeur de l’alcôve est supérieure à 380 mm (15 po), et lorsqu’une approche parallèle est nécessaire, l’espace d’accès devrait être d’au moins 1 525 mm (60 po) de largeur.

8.3.4.3.3 Approche parallèle

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 380 mm (15 po), et lorsqu’une approche parallèle est nécessaire, l’espace d’accès doit être d’au moins 1 525 mm (60 po) de largeur.

Changement de numérotation

Reformulation stylistique

Changement fonctionnel

8.3.4.3.3 Approche parallèle

Lorsque l’espace opérationnel se trouve dans une alcôve au sein des TIC fixes, la profondeur de l’alcôve est supérieure à 380 mm (15 po), et lorsqu’une approche parallèle est nécessaire, l’espace d’accès doit être d’au moins 1 525 mm (60 po) de largeur.

8.3.5 Instructions d’installation

Lorsque les TIC doivent être installées, des instructions doivent présenter une méthode d’installation des TIC de manière à garantir que les dimensions des espaces faisant partie intégrante des TIC sont conformes aux clauses 8.3.2 à 8.3.4.

8.3.5 Instructions d’installation

Lorsque les TIC doivent être installées, des instructions doivent présenter une méthode d’installation des TIC de manière à garantir que les dimensions des espaces faisant partie intégrante des TIC sont conformes aux clauses 8.3.2 à 8.3.4.

8.3.6 Instructions d’installation

Les instructions d’installation doivent être accessibles pour toutes les TIC fixes. Ces instructions doivent donner des directives sur la façon d’installer les TIC d’une manière qui tient compte des exigences applicables en matière d’accessibilité de l’environnement bâti lorsqu’elles s’appliquent à l’installation des TIC. Lorsque de telles exigences n’existent pas, les instructions devraient exiger que les dimensions des TIC installées soient conformes aux clauses 8.3.2 à 8.3.5 du présent document.

Changement de numérotation

Reformulation stylistique

Mise à jour explicative

Changement fonctionnel

8.3.6 Instructions d’installation

Les instructions d’installation doivent être accessibles pour toutes les TIC fixes. Ces instructions doivent donner des directives sur la façon d’installer les TIC d’une manière qui tient compte des exigences applicables en matière d’accessibilité de l’environnement bâti lorsqu’elles s’appliquent à l’installation des TIC. Lorsque de telles exigences n’existent pas, les instructions devraient exiger que les dimensions des TIC installées soient conformes aux clauses 8.3.2 à 8.3.5 du présent document.

9.1.3.4 Orientation

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.4 Orientation des WCAG 2.1.

Nouvelle exigence

9.1.3.4 Orientation

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.4 Orientation des WCAG 2.1.

9.1.3.4 Orientation

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.3.4 Orientation des WCAG 2.1.

9.1.3.5 Identifier la finalité de la saisie

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Nouvelle exigence

9.1.3.5 Identifier la finalité de la saisie

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

9.1.3.5 Identifier la finalité de la saisie

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

9.1.4.10 Redistribution

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.10 Redistribution des WCAG 2.1.

Nouvelle exigence

9.1.4.10 Redistribution

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.10 Redistribution des WCAG 2.1.

9.1.4.10 Redistribution

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.10 Redistribution des WCAG 2.1.

9.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Nouvelle exigence

9.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

9.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est une page Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

9.1.4.12 Espacement du texte

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Nouvelle exigence

9.1.4.12 Espacement du texte

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

9.1.4.12 Espacement du texte

Dans le cas où la TIC utilisée est une page Web, celle-ci doit satisfaire au critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

9.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est une page Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Nouvelle exigence

9.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est une page Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

9.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est une page Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

9.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

Nouvelle exigence

9.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

9.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC sont une page Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

9.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.1 Gestes pour le contrôle du pointeur.

Nouvelle exigence

9.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.1 Gestes pour le contrôle du pointeur.

9.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.1 Gestes pour le contrôle du pointeur.

9.2.5.2 Annulation de l’action du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.2 Annulation de l’action du pointeur.

Nouvelle exigence

9.2.5.2 Annulation de l’action du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.2 Annulation de l’action du pointeur.

9.2.5.2 Annulation de l’action du pointeur

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.2 Annulation de l’action du pointeur.

9.2.5.3 Étiquette dans le nom

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom de WCAG 2.1.

Nouvelle exigence

9.2.5.3 Étiquette dans le nom

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom de WCAG 2.1.

9.2.5.3 Étiquette dans le nom

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom de WCAG 2.1.

9.2.5.4 Activation par le mouvement

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement.

Nouvelle exigence

9.2.5.4 Activation par le mouvement

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement.

9.2.5.4 Activation par le mouvement

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement.

9.4.1.3 Messages d’état

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

Nouvelle exigence

9.4.1.3 Messages d’état

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

9.4.1.3 Messages d’état

Dans le cas où la technologie est une page Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

9.5 Critères de succès de niveau AAA des WCAG 2.1

Outre les critères de succès de niveau AA, les Règles pour l’accessibilité des contenus Web comprennent les critères de succès pour le niveau AAA, aux clauses 9.1 à 9.4. Ces critères sont énumérés dans le tableau 9.1. Les auteurs de sites Web et les spécialistes de l’approvisionnement en matière d’accessibilité sont invités à tenir compte des critères de succès de niveau AAA des WCAG 2.1 qui, lorsqu’il est possible de les appliquer, peuvent fournir un accès au-delà de ce qui est requis dans le présent document.

REMARQUE : Le W3C stipule qu’« il n’est pas recommandé de se fixer le niveau AAA comme objectif à l’échelle de sites entiers car il n’est pas possible de satisfaire à tous les critères de succès du niveau AAA pour certains contenus ».

Nouvelle exigence

9.5 Critères de succès de niveau AAA des WCAG 2.1

Outre les critères de succès de niveau AA, les Règles pour l’accessibilité des contenus Web comprennent les critères de succès pour le niveau AAA, aux clauses 9.1 à 9.4. Ces critères sont énumérés dans le tableau 9.1. Les auteurs de sites Web et les spécialistes de l’approvisionnement en matière d’accessibilité sont invités à tenir compte des critères de succès de niveau AAA des WCAG 2.1 qui, lorsqu’il est possible de les appliquer, peuvent fournir un accès au-delà de ce qui est requis dans le présent document.

REMARQUE : Le W3C stipule qu’« il n’est pas recommandé de se fixer le niveau AAA comme objectif à l’échelle de sites entiers car il n’est pas possible de satisfaire à tous les critères de succès du niveau AAA pour certains contenus ».

10.2.7 Information et relations

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès. L’information, la structure et les relations véhiculées dans la présentation peuvent être déterminées à l’aide d’un programme informatique ou être disponibles sous forme de texte.

Remarque :Ce critère de succès est identique au critère de succès 1.3.1 Information et relations des WCAG 2.0.

10.1.3.1 Information et relations

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

Changement de numérotation

10.1.3.1 Information et relations

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE : Lorsque les documents contiennent des types de structure non standard (rôles), il est préférable de les faire correspondre à un type de structure standard comme solution de secours pour le lecteur.

Mise à jour explicative

10.1.3.1 Information et relations

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE : Lorsque les documents contiennent des types de structure non standard (rôles), il est préférable de les faire correspondre à un type de structure standard comme solution de secours pour le lecteur.

10.1.3.4 Orientation

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

Nouvelle exigence

10.1.3.4 Orientation

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

10.1.3.4 Orientation

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

10.1.3.5 Identifier la finalité de la saisie

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Nouvelle exigence

10.1.3.5 Identifier la finalité de la saisie

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

10.1.3.5 Identifier la finalité de la saisie

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

10.1.4.10 Redistribution

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

Nouvelle exigence

10.1.4.10 Redistribution

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

10.1.4.10 Redistribution

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

10.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Nouvelle exigence

10.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

10.1.4.11 Contraste du contenu non textuel

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

10.1.4.12 Espacement du texte

Dans le cas où la TIC est un document non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Nouvelle exigence

10.1.4.12 Espacement du texte

Dans le cas où la TIC est un document non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

10.1.4.12 Espacement du texte

Dans le cas où la TIC est un document non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

10.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Nouvelle exigence

10.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

10.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un document non Web, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

10.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC ne sont pas un document Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

Nouvelle exigence

10.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC ne sont pas un document Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

10.2.1.4 Raccourcis clavier utilisant des caractères

Lorsque les TIC ne sont pas un document Web, elles doivent satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

10.2.20 Clause vide

Cette clause ne contient aucune exigence. Elle est incluse afin d’aligner la numérotation des sous-clauses connexes dans les clauses 9.2, 10.2 et 11.2.

10.2.4.1 VideChangement de numérotation

10.2.4.1 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Contourner des blocs » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents » qui sont rares.

REMARQUE 2 : Bien qu’il ne s’agisse pas d’une exigence, la possibilité de contourner des blocs de contenu qui sont répétés dans les documents est généralement considérée comme une pratique exemplaire et répond aux besoins des utilisateurs.

Mise à jour explicative

10.2.4.1 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Contourner des blocs » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents » qui sont rares.

REMARQUE 2 : Bien qu’il ne s’agisse pas d’une exigence, la possibilité de contourner des blocs de contenu qui sont répétés dans les documents est généralement considérée comme une pratique exemplaire et répond aux besoins des utilisateurs.

10.2.20 Clause vide

Cette clause ne contient aucune exigence. Elle est incluse afin d’aligner la numérotation des sous-clauses connexes dans les clauses 9.2, 10.2 et 11.2.

10.2.4.5 VideChangement de numérotation

10.2.4.5 Vide

REMARQUE : L’exigence de la page Web connexe «Accès multiples » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents »qui sont rares.

Mise à jour explicative

10.2.4.5 Vide

REMARQUE : L’exigence de la page Web connexe «Accès multiples » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents »qui sont rares.

10.2.5.1 Gestes pour le contrôle du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Toutes les fonctionnalités qui utilisent des gestes multipoints ou basés sur un tracé peuvent être utilisées avec un pointage à contact unique sans geste basé sur un tracé, à moins qu’un geste multipoint ou basé sur un tracé ne soit essentiel.

REMARQUE 1 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

Nouvelle exigence

10.2.5.1 Gestes pour le contrôle du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Toutes les fonctionnalités qui utilisent des gestes multipoints ou basés sur un tracé peuvent être utilisées avec un pointage à contact unique sans geste basé sur un tracé, à moins qu’un geste multipoint ou basé sur un tracé ne soit essentiel.

REMARQUE 1 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

10.2.5.1 Gestes pour le contrôle du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Toutes les fonctionnalités qui utilisent des gestes multipoints ou basés sur un tracé peuvent être utilisées avec un pointage à contact unique sans geste basé sur un tracé, à moins qu’un geste multipoint ou basé sur un tracé ne soit essentiel.

REMARQUE 1 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

10.2.5.2 Annulation de l’action du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

Nouvelle exigence

10.2.5.2 Annulation de l’action du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

10.2.5.2 Annulation de l’action du pointeur

Lorsque la TIC est un document non Web, elle doit satisfaire au critère de succès suivant.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

10.2.5.3 Étiquette dans le nom

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Nouvelle exigence

10.2.5.3 Étiquette dans le nom

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

10.2.5.3 Étiquette dans le nom

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

10.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

Nouvelle exigence

10.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

10.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

10.2.32 Clause vide

Cette clause ne contient aucune exigence. Elle est incluse afin d’aligner la numérotation des sous-clauses connexes dans les clauses 9.2, 10.2 et 11.2.

10.3.2.3 VideChangement de numérotation

10.3.2.3 Vide

REMARQUE : L’exigence de la page Web connexe « Navigation cohérente » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents » qui sont rares.

Mise à jour explicative

10.3.2.3 Vide

REMARQUE : L’exigence de la page Web connexe « Navigation cohérente » ne s’applique pas aux documents uniques, mais à une définition précise d’« ensembles de documents » qui sont rares.

10.4.1.3 Vide

10.4.1.3 Messages d’état

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

Nouvelle exigence

10.4.1.3 Messages d’état

Dans le cas où la TIC est un document non Web, celle-ci doit satisfaire au critère de succès 4.1.3 Messages d’état.

10.2.39 Positionnement des sous-titres

Lorsque la TIC est un document non Web qui contient des médias synchronisés avec des sous-titres, les sous-titres ne devraient pas cacher les renseignements pertinents dans les médias synchronisés.

10.5 Positionnement des sous-titres

Lorsque la TIC est un document non Web qui contient des médias synchronisés avec des sous-titres, les sous-titres ne devraient pas cacher les renseignements pertinents dans les médias synchronisés.

Changement de numérotation

10.5 Positionnement des sous-titres

Lorsque la TIC est un document non Web qui contient des médias synchronisés avec des sous-titres, les sous-titres ne devraient pas cacher les renseignements pertinents dans les médias synchronisés.

10.5 Positionnement des sous-titres

Lorsque la TIC est un document non Web qui contient des médias synchronisés avec des sous-titres, les sous-titres ne devraient pas cacher les renseignements pertinents dans les médias synchronisés.

11.1.2.1.2.1 Préenregistrement audio uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran et lorsque des renseignements auditifs préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes de la TIC, la fonctionnalité du logiciel qui fournit une interface utilisateur doit satisfaire à l'exigence 5.1.5 (sortie visuelle pour renseignements audio).

Nouvelle exigence

11.1.2.1.2.1 Préenregistrement audio uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran et lorsque des renseignements auditifs préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes de la TIC, la fonctionnalité du logiciel qui fournit une interface utilisateur doit satisfaire à l'exigence 5.1.5 (sortie visuelle pour renseignements audio).

11.1.2.1.2.1 Préenregistrement audio uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran et lorsque des renseignements auditifs préenregistrés sont nécessaires pour permettre l’utilisation de fonctions restreintes de la TIC, la fonctionnalité du logiciel qui fournit une interface utilisateur doit satisfaire à l'exigence 5.1.5 (sortie visuelle pour renseignements audio).

11.1.2.1.2.2 Préenregistrement vidéo uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l'exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

Nouvelle exigence

11.1.2.1.2.2 Préenregistrement vidéo uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l'exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

11.1.2.1.2.2 Préenregistrement vidéo uniquement (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l'exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

11.2.1.6 Description audio (préenregistrée)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur, elle doit satisfaire au critère de succès 1.2.5 Description audio (préenregistrée) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin. REMARQUE 3 : Ce critère de succès est identique au critère 1.2.5 Description audio (Pré-enregistrée) des WCAG 2.0, avec l’ajout de la remarque 1 ci-dessus.

11.1.2.5 Description audio (préenregistrée)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur, elle doit satisfaire au critère de succès 1.2.5 Description audio (préenregistrée) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

Changement de numérotation

11.1.2.5 Description audio (préenregistrée)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur, elle doit satisfaire au critère de succès 1.2.5 Description audio (préenregistrée) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

11.1.2.5 Description audio (préenregistrée)

Lorsque la TIC est un logiciel non Web qui fournit une interface utilisateur, elle doit satisfaire au critère de succès 1.2.5 Description audio (préenregistrée) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

11.1.2.3.1 Audio-description ou version de remplacement pour un média temporel (préenregistré – fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

Nouvelle exigence

11.1.2.3.1 Audio-description ou version de remplacement pour un média temporel (préenregistré – fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

11.1.2.3.1 Audio-description ou version de remplacement pour un média temporel (préenregistré – fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.2.3 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) des WCAG 2.1.

REMARQUE 1 : La définition WCAG 2.1 de la « description audio » indique que la description audio est également appelée « description vidéo » et « commentaire descriptif ».

REMARQUE 2 : Des pistes audio secondaires ou de rechange sont couramment utilisées à cette fin.

11.1.2.3.2 Audio-description ou version de remplacement pour un média temporel (pré-enregistré – fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

Nouvelle exigence

11.1.2.3.2 Audio-description ou version de remplacement pour un média temporel (pré-enregistré – fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

11.1.2.3.2 Audio-description ou version de remplacement pour un média temporel (pré-enregistré) – fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.7 (sortie vocale pour l’information vidéo).

11.2.1.7 Information et relations

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès. L’information, la structure et les relations véhiculées dans la présentation peuvent être déterminées avec un programme informatique ou être disponibles en texte.

REMARQUE 1 : Dans les logiciels, la déterminabilité par un programme informatique est le mieux réalisée par l'utilisation des services d'accessibilité fournis par les logiciels de plateforme pour permettre l'interopérabilité entre les logiciels et les technologies d'assistance et les fonctions d'accessibilité des logiciels (voir la clause 11.3 Interopérabilité avec les technologies d'assistance). REMARQUE 2 : Ce critère de succès est identique au critère 1.3.1 Information et relations des WCAG 2.0, avec l’ajout de la remarque 1 ci-dessus.

11.1.3.1.1 Information et relations (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE : Dans les logiciels, la déterminabilité par un programme informatique est le mieux réalisée par l'utilisation des services d'accessibilité fournis par les logiciels de plateforme pour permettre l'interopérabilité entre les logiciels et les technologies d'assistance et les fonctions d'accessibilité des logiciels (voir la clause 11.5 Interopérabilité avec les technologies d'assistance).

Changement de numérotation

Mise à jour explicative

11.1.3.1.1 Information et relations (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE : Dans les logiciels, la déterminabilité par un programme informatique est le mieux réalisée par l'utilisation des services d'accessibilité fournis par les logiciels de plateforme pour permettre l'interopérabilité entre les logiciels et les technologies d'assistance et les fonctions d'accessibilité des logiciels (voir la clause 11.5 Interopérabilité avec les technologies d'assistance).

11.1.3.1.1 Information et relations (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.1 Information et relations des WCAG 2.1.

REMARQUE : Dans les logiciels, la déterminabilité par un programme informatique est le mieux réalisée par l'utilisation des services d'accessibilité fournis par les logiciels de plateforme pour permettre l'interopérabilité entre les logiciels et les technologies d'assistance et les fonctions d'accessibilité des logiciels (voir la clause 11.5 Interopérabilité avec les technologies d'assistance).

11.1.3.1.2 Information et relations (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

Nouvelle exigence

11.1.3.1.2 Information et relations (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

11.1.3.1.2 Information et relations (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

11.2.1.8 Ordre séquentiel logique

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès. Lorsque la séquence dans laquelle le contenu est présenté affecte sa signification, une bonne séquence de lecture peut être déterminée par un programme informatique.

REMARQUE : Ce critère de succès est identique au critère 1.3.2 Ordre séquentiel logique des WCAG 2.0.

11.1.3.2.1 Ordre séquentiel logique (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

Changement de numérotation

11.1.3.2.1 Ordre séquentiel logique (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

11.1.3.2.1 Ordre séquentiel logique (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.3.2 Ordre séquentiel logique des WCAG 2.1.

11.1.3.2.2 Ordre séquentiel logique (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

Nouvelle exigence

11.1.3.2.2 Ordre séquentiel logique (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

11.1.3.2.2 Ordre séquentiel logique (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur restreinte aux technologies d'assistance pour la lecture d'écran et que des informations sont affichées à l'écran, elle devrait fournir des informations auditives permettant à l'utilisateur de mettre en corrélation l’audio avec les informations affichées à l'écran.

REMARQUE 1 : De nombreuses personnes aveugles au sens de la loi ont encore des capacités visuelles et utilisent certains aspects de l’affichage visuel même s’il ne peut être entièrement compris. Une solution de rechange audio à la fois complète et complémentaire comprend toutes les informations visuelles telles que le focus ou la surbrillance, de sorte que l’audio puisse être mis en corrélation avec des informations visibles à l’écran à tout moment.

REMARQUE 2 : Les exemples d’informations auditives qui permettent à l’utilisateur de mettre en corrélation l’audio avec les informations affichées à l’écran comprennent la structure et les relations véhiculées dans la présentation.

11.1.3.4 Orientation

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

Nouvelle exigence

11.1.3.4 Orientation

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

11.1.3.4 Orientation

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.4 Orientation des WCAG 2.1.

11.1.3.5 Identifier la finalité de la saisie

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Nouvelle exigence

11.1.3.5.1 Identifier la finalité de la saisie (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit remplir le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

Changement de numérotation

Changement fonctionnel

11.1.3.5.1 Identifier la finalité de la saisie (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit remplir le critère de succès 1.3.5 Identifier la finalité de la saisie des WCAG 2.1.

11.1.3.5.2 Identifier la finalité de la saisie (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui est restreint aux technologies d’assistance, elle doit prévoir au moins un mode de fonctionnement selon lequel l’utilisateur est présenté, sous forme audio, l’objectif de chaque champ de saisie recueillant des renseignements sur l’utilisateur, lorsque ce champ sert un objectif défini à la section Identifier la finalité de la saisie pour les composants d’interface utilisateur des WCAG 2.1.

Nouvelle exigence

11.1.3.5.2 Identifier la finalité de la saisie (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui est restreint aux technologies d’assistance, elle doit prévoir au moins un mode de fonctionnement selon lequel l’utilisateur est présenté, sous forme audio, l’objectif de chaque champ de saisie recueillant des renseignements sur l’utilisateur, lorsque ce champ sert à un objectif définie à la section Identifier la finalité de la saisie pour les composants d’interface utilisateur des WCAG 2.1.

11.2.1.13 Redimensionnement du texte

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux fonctions d’agrandissement d’une plateforme ou d’une technologie d’assistance, elle doit satisfaire au critère de succès. À l’exception des légendes et des images de texte, le texte peut être redimensionné sans technologie d’assistance jusqu’à 200 % sans perte de contenu ou de fonctionnalité.

REMARQUE 1 : Le contenu pour lequel il existe des logiciels de lecture, de visualisation ou d’édition dotés d'une fonction de zoom de 200 % répondrait automatiquement à ce critère de succès lorsqu'il est utilisé avec ces logiciels, sauf si le contenu ne fonctionne pas avec le zoom.

REMARQUE 2 : technologies. Ce critère de succès a trait à la capacité de permettre aux utilisateurs d’agrandir le texte à l’écran au moins jusqu’à 200 % sans avoir besoin d'utiliser des technologies d’assistance. Cela signifie que l’application fournit un moyen d’agrandir le texte de 200 % (zoom ou autre) sans perte de contenu ou de fonctionnalité ou que l’application fonctionne avec les fonctionnalités de la plate-forme qui répondent à cette exigence.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.4 Redimensionner le texte des WCAG 2.0 avec l’ajout des remarques 1 et 2 ci-dessus.

11.1.4.4.2 Redimensionnement du texte (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui n’est pas en mesure d’accéder aux fonctions d’agrandissement d’une plateforme ou d’une technologie d’assistance, elle doit satisfaire à l’exigence 5.1.4 (Fonction restreinte à l’agrandissement du texte).

REMARQUE : Étant donné que la prise en charge du rendu de texte dans un environnement restreint peut être plus limitée que celle que l’on trouve dans les agents utilisateurs pour le Web, le respect de la clause 11.1.4.4.2 dans un environnement restreint peut imposer un fardeau beaucoup plus lourd à l’auteur du contenu.

Changement de numérotation
Changement fonctionnel

11.1.4.4.2 Redimensionnement du texte (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui n’est pas en mesure d’accéder aux fonctions d’agrandissement d’une plateforme ou d’une technologie d’assistance, elle doit satisfaire à l’exigence 5.1.4 (Fonction restreinte à l’agrandissement du texte).

REMARQUE : Étant donné que la prise en charge du rendu de texte dans un environnement restreint peut être plus limitée que celle que l’on trouve dans les agents utilisateurs pour le Web, le respect de la présente clause dans un environnement restreint peut imposer un fardeau beaucoup plus lourd à l’auteur du contenu.

11.1.4.4.2 Redimensionnement du texte (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui n’est pas en mesure d’accéder aux fonctions d’agrandissement d’une plateforme ou d’une technologie d’assistance, elle doit satisfaire à l’exigence 5.1.4 (Fonction restreinte à l’agrandissement du texte).

REMARQUE : Étant donné que la prise en charge du rendu de texte dans un environnement restreint peut être plus limitée que celle que l’on trouve dans les agents utilisateurs pour le Web, le respect de la présente clause dans un environnement restreint peut imposer un fardeau beaucoup plus lourd à l’auteur du contenu.

11.2.1.14 Texte sous forme d’image

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès.

Si les technologies utilisées peuvent réaliser la présentation visuelle, du texte est utilisé pour véhiculer l’information plutôt que du texte sous forme d’image sauf dans les cas suivants :

  • Personnalisable : le texte sous forme d’image peut être personnalisé visuellement selon les exigences de l’utilisateur ;
  • Essentielle : une présentation spécifique du texte est essentielle à l’information véhiculée.

REMARQUE 1 : Les logotypes sont considérés comme essentiels (le texte qui fait partie d’un logo ou d’un nom de marque).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 1.4.5 Images de texte des WCAG 2.0.

11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

Changement de numérotation

Changement fonctionnel

Mise à jour explicative

11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

11.1.4.5.1 Texte sous forme d’image (fonction non restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire au critère de succès 1.4.5 Texte sous forme d’image des WCAG 2.1.

11.1.4.5.2 Texte sous forme d’image (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle n’a pas besoin de satisfaire au critère de succès 1.4.5 Images de texte des WCAG 2.1 parce qu’il n’est pas nécessaire d’imposer à toutes les fonctionnalités fermées que le texte affiché à l'écran soit effectivement représenté en interne comme du texte (aux termes des WCAG 2.1), étant donné qu'il n'y a pas d’interopérabilité avec les technologies d’assistance.

Nouvelle exigence

11.1.4.5.2 Texte sous forme d’image (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.6 (sortie vocale pour les contenus non textuels).

Changement fonctionnel

11.1.4.5.2 Texte sous forme d’image (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.6 (sortie vocale pour les contenus non textuels).

11.1.4.10.1 Redistribution (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui prend en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle remplit le critère de succès suivant.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

Nouvelle exigence

11.1.4.10 Redistribution

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, il doit remplir le critère de succès suivant.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

Changement de numérotation

Changement fonctionnel

11.1.4.10 Redistribution

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, il doit remplir le critère de succès.

Le contenu peut être présenté sans perte d’information ou de fonctionnalité et sans nécessité de défilement dans les deux dimensions pour :

  • un contenu à défilement vertical avec une largeur équivalente à 320 pixels CSS ;
  • un contenu à défilement horizontal avec une hauteur équivalente à 256 pixels CSS.

Sauf pour les parties du contenu dont l’utilisation ou la compréhension nécessite une mise en page en deux dimensions.

REMARQUE 1 : 320 pixels CSS équivaut à une largeur d’affichage initiale de 1280 pixels CSS avec un zoom de 400 %. Pour les contenus Web conçus pour défiler horizontalement (par exemple, avec du texte vertical), la valeur de 256 pixels CSS équivaut à une hauteur d’affichage initiale de 1024 pixels avec un zoom de 400 %.

REMARQUE 2 : On compte parmi les exemples de contenu nécessitant une mise en page en deux dimensions : les images, les cartes, les diagrammes, les vidéos, les jeux, les présentations, les tableaux de données, et les interfaces où il est nécessaire de garder les barres d’outils visibles pendant la manipulation du contenu.

REMARQUE 3 : Ce critère de succès est identique au critère de succès 1.4.10 Redistribution des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

11.1.4.10.2 Redistribution (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne pas prend en charge l’accès aux fonctions d’agrandissement de la plateforme ou à la technologie d’assistance, elle remplit l’exigence 5.1.4 (fonction restreinte à l’agrandissement du texte).

Nouvelle exigenceVideVide

11.1.4.11 Contraste du contenu non textuel

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

Nouvelle exigence

11.1.4.11 Contraste du contenu non textuel

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

11.1.4.11 Contraste du contenu non textuel

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.11 Contraste du contenu non textuel des WCAG 2.1.

11.1.4.12 Espacement du texte

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

Nouvelle exigence

11.1.4.12 Espacement du texte

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

11.1.4.12 Espacement du texte

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui n’a pas de zone de présentation de contenu de taille fixe essentielle à l’information véhiculée, elle remplit le critère de succès 1.4.12 Espacement du texte des WCAG 2.1.

11.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

Nouvelle exigence

11.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

11.1.4.13 Contenu au survol ou au focus

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès 1.4.13 Contenu au survol ou au focus des WCAG 2.1.

11.2.1.1.2 Clavier (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

Nouvelle exigence

11.2.1.1.2 Clavier (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

11.2.1.1.2 Clavier (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

11.2.1.4.1 Raccourcis clavier utilisant des caractères (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

Nouvelle exigence

11.2.1.4.1 Raccourcis clavier utilisant des caractères (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

11.2.1.4.1 Raccourcis clavier utilisant des caractères (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.1.4 Raccourcis clavier utilisant des caractères des WCAG 2.1.

11.2.1.4.2 Raccourcis clavier utilisant des caractères (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

Nouvelle exigence

11.2.1.4.2 Raccourcis clavier utilisant des caractères (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

11.2.1.4.2 Raccourcis clavier utilisant des caractères (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui fournit une interface utilisateur restreinte aux claviers ou une interface clavier, elle doit satisfaire à l’exigence 5.1.6.1 (Fonctionnement sans interface clavier : fonction restreinte).

11.2.1.20 Clause vide

Cette clause ne contient aucune exigence. Elle est incluse afin d’aligner la numérotation des sous-clauses connexes dans les clauses 9.2, 10.2 et 11.2.

11.2.4.1 Vide

11.2.4.1 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Contourner des blocs » ne s’applique pas aux programmes logiciels uniques, mais à une définition précise d’ « ensembles de programmes logiciels » qui sont extrêmement rares.

REMARQUE 2 : Bien qu’il ne s’agisse pas d’une exigence, la possibilité de contourner des blocs de contenu qui sont répétés dans les logiciels est généralement considérée comme une pratique exemplaire et répond aux besoins des utilisateurs.

Reformulation stylistique

11.2.4.1 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Contourner des blocs » ne s’applique pas aux programmes logiciels uniques, mais à une définition précise d’ « ensembles de programmes logiciels » qui sont extrêmement rares.

REMARQUE 2 : Bien qu’il ne s’agisse pas d’une exigence, la possibilité de contourner des blocs de contenu qui sont répétés dans les logiciels est généralement considérée comme une pratique exemplaire et répond aux besoins des utilisateurs.

11.2.1.21 Clause vide

Cette clause ne contient aucune exigence. Elle est incluse afin d’aligner la numérotation des sous-clauses connexes dans les clauses 9.2, 10.2 et 11.2.

11.2.4.2 Vide

11.2.4.2 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Page intitulée » ne s’applique pas aux programmes logiciels uniques, mais à une définition précise d’« ensembles de programmes logiciels » qui sont extrêmement rares.

REMARQUE 2 : Bien que le nom d’un produit logiciel puisse constituer un titre suffisant s’il décrit le sujet ou l’objectif, les noms de logiciels sont des marques déposées et les noms de marques ne peuvent pas, selon la loi, être des noms descriptifs. Il n’est pas pratique de rendre les noms de logiciels à la fois uniques et descriptifs.

Reformulation stylistique

11.2.4.2 Vide

REMARQUE 1 : L’exigence de la page Web connexe « Page intitulée » ne s’applique pas aux programmes logiciels uniques, mais à une définition précise d’« ensembles de programmes logiciels » qui sont extrêmement rares.

REMARQUE 2 : Bien que le nom d’un produit logiciel puisse constituer un titre suffisant s’il décrit le sujet ou l’objectif, les noms de logiciels sont des marques déposées et les noms de marques ne peuvent pas, selon la loi, être des noms descriptifs. Il n’est pas pratique de rendre les noms de logiciels à la fois uniques et descriptifs.

11.3.1.1.2 Langue du logiciel (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.14 (Langues parlées).

Nouvelle exigence

11.3.1.1.2 Langue du logiciel (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.14 (Langues parlées).

11.3.1.1.2 Langue du logiciel (fonction restreinte)

Lorsque la TIC est un logiciel non Web qui est doté d’une interface utilisateur qui est restreinte aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.14 (Langues parlées).

11.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès suivant.

Toutes les fonctions qui utilisent des mouvements multipoints ou basés sur un tracé pour exécuter une commande peuvent être utilisées avec un seul pointeur sans mouvement basé sur un tracé, à moins qu’un mouvement multipoint ou basé sur un tracé soit essentiel.

REMARQUE 1 : Cette exigence s’applique au logiciel non Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

Nouvelle exigence

11.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès suivant.

Toutes les fonctions qui utilisent des mouvements multipoints ou basés sur un tracé pour exécuter une commande peuvent être utilisées avec un seul pointeur sans mouvement basé sur un tracé, à moins qu’un mouvement multipoint ou basé sur un tracé soit essentiel.

REMARQUE 1 : Cette exigence s’applique au logiciel non Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1 Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

11.2.5.1 Gestes pour le contrôle du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès.

Toutes les fonctions qui utilisent des mouvements multipoints ou basés sur un tracé pour exécuter une commande peuvent être utilisées avec un seul pointeur sans mouvement basé sur un tracé, à moins qu’un mouvement multipoint ou basé sur un tracé soit essentiel.

REMARQUE 1 : Cette exigence s’applique au logiciel non Web qui interprète les actions du pointeur (c.-à-d. qu’elle ne s’applique pas aux actions requises pour faire fonctionner l’agent utilisateur ou la technologie d’assistance).

REMARQUE 2 : Ce critère de succès est identique au critère de succès 2.5.1

Gestes pour le contrôle du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par la note 1 ci-dessus.

11.2.5.2 Annulation de l’action du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès suivant.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

Nouvelle exigence

11.2.5.2 Annulation de l’action du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès suivant.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

11.2.5.2 Annulation de l’action du pointeur

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle remplit le critère de succès.

Pour une fonctionnalité qui peut être activée avec un dispositif de pointage à contact unique, au moins une des conditions suivantes est vraie :

  • Aucun événement descendant : l’événement descendant (down-event) du pointeur n’est pas utilisé pour exécuter une partie ou la totalité de la fonction ;
  • Abandon ou annulation : l’achèvement de la fonction se fait sur l’événement ascendant (up-event), et un mécanisme est disponible pour interrompre la fonction avant l’achèvement ou pour annuler la fonction après l’achèvement ;
  • Inversion sur l’événement ascendant : l’événement ascendant inverse tout résultat de l’événement descendant précédent ;
  • Essentiel : l’achèvement de la fonction lors de l’événement descendant est essentiel.

REMARQUE 1 : Les fonctions qui émulent l’appui d’une touche du clavier ou du pavé numérique sont considérées comme essentielles.

REMARQUE 2 : Cette exigence s’applique aux contenus Web qui interprètent les actions du pointeur (elle ne s’applique donc pas aux actions nécessaires à l’utilisation d’un agent utilisateur ou d’une technologie d’assistance).

REMARQUE 3 : Ce critère de succès est identique au critère de succès 2.5.2 Annulation de l’action du pointeur des WCAG 2.1 après remplacement des notes originales des WCAG 2.1 par les notes 1 et 2 ci-dessus.

11.2.5.3 Étiquette dans le nom

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Nouvelle exigence

11.2.5.3.1 Étiquette dans le nom (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

Changement de numérotation

11.2.5.3.1 Étiquette dans le nom (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.3 Étiquette dans le nom des WCAG 2.1.

11.2.5.3.2 Étiquette dans le nom (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.3 (Corrélation de sortie sonore).

Nouvelle exigence

11.2.5.3.2 Étiquette dans le nom (fonction restreinte)

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur et qui ne prend pas en charge l’accès aux technologies d’assistance pour la lecture d’écran, elle doit satisfaire à l’exigence 5.1.3.3 (Corrélation de sortie sonore).

11.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

Nouvelle exigence

11.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

11.2.5.4 Activation par le mouvement

Dans le cas où la TIC est un logiciel non Web qui est doté d’une interface utilisateur, elle doit satisfaire au critère de succès 2.5.4 Activation par le mouvement des WCAG 2.1.

11.4.1.3.1 Messages d’état (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web, elle doit satisfaire au critère de succès 4.1.3 Messages d’état des WCAG 2.1.

Nouvelle exigence

11.4.1.3.1 Messages d’état (fonction non restreinte)

Dans le cas où la TIC est un logiciel non Web, elle doit satisfaire au critère de succès 4.1.3 Messages d’état des WCAG 2.1.

11.4.1.3.2 Messages d’état (fonction restreinte)

Sans objet.

Nouvelle exigence

11.4.1.3.2 Messages d’état (fonction restreinte)

Sans objet.

13.1.1 Généralités (information)

Les services de relais permettent aux utilisateurs de différents modes de communication (texte, signes, parole, etc.) d’interagir à distance, grâce aux TIC et à la communication bidirectionnelle, en assurant une conversion entre les modes de communication, normalement effectuée par un opérateur humain.

Une pratique exemplaire consiste à respecter les exigences de la norme en vigueur ES 202 975 en matière de services de relais.

13.1.1 Généralités (information)

Les services de relais permettent aux utilisateurs de différents modes de communication (texte, signes, parole, etc.) d’interagir à distance, grâce aux TIC et à la communication bidirectionnelle, en assurant une conversion entre les modes de communication, normalement effectuée par un opérateur humain.

Une pratique exemplaire consiste à respecter les exigences de la norme en vigueur ES 202 975 de l’ETSI en matière de services de relais.

Mise à jour explicative

13.1.1 Généralités (information)

Les services de relais permettent aux utilisateurs de différents modes de communication (texte, signes, parole, etc.) d’interagir à distance, grâce aux TIC et à la communication bidirectionnelle, en assurant une conversion entre les modes de communication, normalement effectuée par un opérateur humain.

Une pratique exemplaire consiste à respecter les exigences de la norme en vigueur ES 202 975 de l’ETSI en matière de services de relais.

13.1.1 Généralités (information)

Les services de relais permettent aux utilisateurs de différents modes de communication (texte, signes, parole, etc.) d’interagir à distance, grâce aux TIC et à la communication bidirectionnelle, en assurant une conversion entre les modes de communication, normalement effectuée par un opérateur humain.

Une pratique exemplaire consiste à respecter les exigences de la norme en vigueur ES 202 975 [i.5] de l’ETSI en matière de services de relais.

13.1.6 Services de relais de la parole à la parole

Lorsque les TIC visent à fournir un service de relais de la parole à la parole, celui-ci doit permettre aux utilisateurs de téléphones souffrant de troubles de l’élocution ou de troubles cognitifs et à tout autre utilisateur de communiquer en leur fournissant une assistance mutuelle.

13.1.6 Services de relais de la parole à la parole

Lorsque les TIC visent à fournir un service de relais de la parole à la parole, celui-ci doit permettre aux utilisateurs de téléphones souffrant de troubles de l’élocution ou de troubles cognitifs et à tout autre utilisateur de communiquer en leur fournissant une assistance mutuelle.

13.1.6 Services de relais de la parole à la parole

Lorsque les TIC visent à fournir un service de relais de la parole à la parole, celui-ci doit permettre aux utilisateurs de téléphones souffrant de troubles de l’élocution ou ayant des capacités cognitives, linguistiques et d’apprentissage limitées, ainsi qu’à tout autre utilisateur, de communiquer en leur fournissant une assistance mutuelle.

Reformulation stylistique

Changement fonctionnel

Mise à jour explicative

13.1.6 Services de relais de la parole à la parole

Lorsque les TIC visent à fournir un service de relais de la parole à la parole, celui-ci doit permettre aux utilisateurs de téléphones souffrant de troubles de l’élocution ou ayant des capacités cognitives, linguistiques et d’apprentissage limitées, ainsi qu’à tout autre utilisateur, de communiquer en leur fournissant une assistance mutuelle.

13.2 Accès aux services de relais

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et qu’un ensemble de services de relais est spécifié pour ce type de communication, l’accès à ces services de relais ne doit pas être bloqué pour les appels sortants et entrants.

REMARQUE 1 : La communication bidirectionnelle peut comprendre les communications vocales, par texte en temps réel ou par vidéo, seules ou combinées, appuyées par un service de relais et le système des TIC.

REMARQUE 2 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

13.2 Accès aux services de relais

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et qu’un ensemble de services de relais est spécifié pour ce type de communication, l’accès à ces services de relais ne doit pas être bloqué pour les appels sortants et entrants.

REMARQUE 1 : La communication bidirectionnelle peut comprendre les communications vocales, par texte en temps réel ou par vidéo, seules ou combinées, appuyées par un service de relais et le système des TIC.

REMARQUE 2 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

13.2 Accès aux services de relais

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services de relais, l’accès à ces services de relais ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par un service de relais et le système des TIC.

REMARQUE 1 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services de relais, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

Mise à jour explicative

Reformulation stylistique

Changement fonctionnel

13.2 Accès aux services de relais

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services de relais, l’accès à ces services de relais ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par un service de relais et le système des TIC.

REMARQUE 1 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel.

REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services de relais, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

13.3 Accès aux services d’urgence

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et qu’un ensemble de services d’urgence est spécifié pour ce type de communication, l’accès à ces services d’urgence ne doit pas être bloqué pour les appels sortants et entrants.

REMARQUE 1 : La communication bidirectionnelle peut comprendre les communications vocales, par texte en temps réel ou par vidéo, seules ou combinées, appuyées par un service d’urgence et le système des TIC.

REMARQUE 2 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel avec les services d’urgence.

13.3 Accès aux services d’urgence

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et qu’un ensemble de services d’urgence est spécifié pour ce type de communication, l’accès à ces services d’urgence ne doit pas être bloqué pour les appels sortants et entrants.

REMARQUE 1 : La communication bidirectionnelle peut comprendre les communications vocales, par texte en temps réel ou par vidéo, seules ou combinées, appuyées par un service d’urgence et le système des TIC.

REMARQUE 2 : La présente exigence vise à assurer aux personnes handicapées un accès aux communications équivalent sur le plan fonctionnel avec les services d’urgence.

13.3 Accès aux services d’urgence

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services d’urgence, l’accès à ces services d’urgence ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par le service d’urgence et le système des TIC.

REMARQUE 1 : La présente exigence vise à assurer aux personnes handicapées un accès aux services d’urgence équivalent sur le plan fonctionnel.
REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services d’urgence, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

Mise à jour explicative

Reformulation stylistique

Changement fonctionnel

13.3 Accès aux services d’urgence

Lorsque les systèmes des TIC prennent en charge la communication bidirectionnelle et que le système est spécifié comme devant être utilisé avec des services d’urgence, l’accès à ces services d’urgence ne doit pas être bloqué pour les appels sortants et entrants, ce qui comprend les communications vocales, par TTR ou par vidéo, seules ou combinées, appuyées par le service d’urgence et le système des TIC.

REMARQUE 1 : La présente exigence vise à assurer aux personnes handicapées un accès aux services d’urgence équivalent sur le plan fonctionnel.

REMARQUE 2 : Le système peut être spécifié comme devant fonctionner avec des services d’urgence, par exemple, par des acheteurs, des organismes de réglementation ou des spécifications de produits.

Liste des tableaux

Notes de bas de page

  1. Les critères de rendement fonctionnel 302.7 et 302.8 de l’article 508 et les énoncés de rendement fonctionnel 4.2.7 et 4.2.8 de la norme EN 301 549 inclusivement visent les mêmes exigences, même s’ils sont regroupés légèrement différemment dans chaque norme.Return to reference 1

  2. Les critères de rendement fonctionnel 302.7 et 302.8 de l’article 508 et les énoncés de rendement fonctionnel 4.2.7 et 4.2.8 de la norme EN 301 549 inclusivement visent les mêmes exigences, même s’ils sont regroupés légèrement différemment dans chaque norme.Return to reference 2

  3. L’article 508 précise que le mode de fonctionnement non visuel doit être une sortie vocale.Return to reference 3

  4. L’article 508 fait référence à une configuration de clavier spécifique qui n’est pas nécessairement pertinente à toutes les langues.Return to reference 4

  5. L’article 508 contient des exigences supplémentaires relatives à la superposition des touches alphabétiques sur les touches numériques.Return to reference 5

  6. Certaines différences quant à la méthode de calcul de l’espace pour les genoux et les pieds.Return to reference 6

  7. Certaines différences quant à la méthode de calcul de l’espace pour les genoux et les pieds.Return to reference 7

  8. Certaines différences quant à la méthode de calcul de l’espace pour les genoux et les pieds.Return to reference 7b

  9. Certaines différences quant à la méthode de calcul de l’espace pour les genoux et les pieds.Return to reference 8

  10. La norme EN 301 549 V3.1.1 (2019-11) contient une erreur: «Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher est considéré comme un espace libre pour les genoux et il devrait […] » Les 685 mm auraient dû être convertis en 27 po. Ce document démontre l’erreur dans la documentation originale de la norme EN.Return to reference 9

  11. La norme EN 301 549 V3.1.1 (2019-11) contient une erreur: «Lorsqu’un obstacle fait partie intégrante des TIC, un espace sous l’obstacle entre 230 mm (9 po) et 685 mm (25 po) au-dessus du plancher est considéré comme un espace libre pour les genoux et il devrait […] » Les 685 mm auraient dû être convertis en 27 po. Ce document démontre l’erreur dans la documentation originale de la norme EN.Return to reference 10

  12. L’article 508 fait référence à la norme 47 CFR 68.317 (une réglementation américaine), tandis que la norme EN 301 549 fait référence au niveau spécifique de gain de volume requis.Return to reference 11

  13. La norme EN 301 549 comprend des exigences plus spécifiques en matière de gain de volume.Return to reference 12

  14. Chacune fait référence à des normes locales pertinentes.Return to reference 13

  15. Chacune fait référence à des normes locales pertinentes.Return to reference 14

  16. Les exigences de la norme EN 301 549 n’ont qu’une valeur informative et font référence à une limite de fréquence supérieure plutôt qu’à la norme de l’UTI.Return to reference 15

  17. La norme EN 301 549 fournit les exigences relatives au TTR, dont il est question ci-dessous.Return to reference 16

  18. La norme EN 301 549 précise qu’elle doit être offerte « en mode textuel et dans au moins un autre mode » tandis que l’article 508 précise qu’elle doit être « visible et audible ».Return to reference 17

  19. La norme EN 301 549 contient des exigences plus spécifiques.Return to reference 18

  20. La norme EN 301 549 contient des exigences plus spécifiques.Return to reference 19

  21. La norme EN 301 549 contient des exigences plus spécifiques.Return to reference 20

  22. La norme EN 301 549 contient des exigences plus spécifiques.Return to reference 21

  23. L’article 508 fait référence aux normes locales spécifiques relatives aux syntoniseurs de télévision numérique.Return to reference 22

  24. L’article 508 met l’accent sur les pièces manœuvrables tandis que la norme EN 301 549 met l’accent sur le niveau d’interaction.Return to reference 23

  25. L’article 508 met l’accent sur les pièces manœuvrables tandis que la norme EN 301 549 met l’accent sur le niveau d’interaction.Return to reference 24

  26. L’article 508 mentionne spécifiquement les touches; tandis que la norme EN 301 549 a une portée plus large et doit inclure les touches.Return to reference 25

  27. L’article 508 exige que le délai soit réglé jusqu’à 2 secondes, tandis que la norme EN 301 549 exige le réglage du délai jusqu’à 0,5 seconde.Return to reference 26

  28. La norme EN 301 549 considère la réponse minutée comme un problème logiciel. Voir 11.2.1.17 (réglable du délai).Return to reference 27

  29. Les clauses des normes EN 301 549 V1.1.1 (2014) et V2.1.2 (2018) de la série 407.8 sont des recommandations (« devrait » par opposition à « doit »). Toutefois, les dispositions de la norme 301 549 V3.1.1 (2019) sont des exigences (« doit » par opposition à « devrait »).Return to reference 28

  30. La norme EN 301 549 considère les problèmes liés au clignotement et à la photosensibilité comme des critères de rendement fonctionnel (voir 4.2.9) et un critère logiciel (voir 11.2.1.19)Return to reference 29

  31. La norme EN 301 549 considère les problèmes liés à la transmission des renseignements par multiples modalités comme des problèmes logiciels (voir 11.2.1.9)Return to reference 30

  32. Aucune clause correspondante dans la norme EN 301 549. Certains aspects sont abordés dans les articles 5.1.5, 7.1.1, 7.1.2, 7.3, 11.2.1.2, 11.2.1.3 et 11.2.1.5 de la norme EN 301 549 (2014).Return to reference 31

  33. Aucune clause correspondante dans la norme EN 301 549. Certains aspects sont abordés dans les articles 5.1.3, 7.2.2 et 11.3 de la norme

    EN 301 549 (2014).Return to reference 32

  34. Aucune clause correspondante dans la norme EN 301 549. La question de l’interopérabilité avec les technologies d’assistance est abordée à l’article 11.3 de la norme EN 301 549 (2014).Return to reference 33

  35. Aucune clause correspondante dans la norme EN 301 549, mais la clause 11.6.3 couvre la même exigence sans préciser PDF.Return to reference 34

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/personas-handicapes-pour-la-conception-d-une-experience-utilisateur-inclusive-eu/index.html b/fr/personas-handicapes-pour-la-conception-d-une-experience-utilisateur-inclusive-eu/index.html index d9107a4ce..6cde81a30 100644 --- a/fr/personas-handicapes-pour-la-conception-d-une-experience-utilisateur-inclusive-eu/index.html +++ b/fr/personas-handicapes-pour-la-conception-d-une-experience-utilisateur-inclusive-eu/index.html @@ -1,4 +1,4 @@ -Personas handicapés pour la conception d'une expérience utilisateur inclusive (EU) - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Personas handicapés pour la conception d'une expérience utilisateur inclusive (EU)

Le cas d'inclure les handicaps dans les personas des utilisateurs, les types de technologies qu'ils utilisent et les échantillons de personas avec des handicaps.

Sur cette page

Le présent document a pour but d’aider l’utilisateur à comprendre la manière de créer des personas handicapés. Des personas sont des personnages fictifs créés pour représenter divers types d’utilisateurs dont l’utilisation d’un site, d’une marque ou d’un produit serait unique. Souvent, les développeurs conçoivent des sites Web, des applications Web de bureau et mobiles à leurs propres goûts, ce qui peut éventuellement créer des obstacles pour certains utilisateurs. Il est important de planifier pour un groupe diversifié d’utilisateurs présentant un vaste éventail de capacités et d’incapacités, de niveaux techniques, de capacités fonctionnelles et de degrés de familiarité avec les processus ou les activités. Un aspect important de la conception inclusive consiste à inclure les personnes handicapées dès la première étape de la conception, puis à toutes les étapes du cycle de vie du développement logiciel. On contribuera ainsi à élever l’accessibilité et la convivialité du produit final et à mieux assurer l’inclusion de tous. Le présent document est un recueil de données provenant de diverses sources et visant à créer une vision cohérente de la conception inclusive.

Créer l’égalité d’accès pour tous

Le gouvernement du Canada s’est engagé à fournir de l’information au public sous une forme accessible; il s’est également engagé à créer un milieu de travail inclusif et sans obstacle qui inclut les personnes handicapées. Ces deux engagements nécessitent le respect de normes, d’exigences et de lignes directrices et le soutien d’une grande utilisation de la technologie, notamment les divers outils de la technologie adaptée comme les logiciels, le matériel et les dispositifs à l’intention des utilisateurs handicapés.

Les utilisateurs accèdent à l’information par divers moyens : les ordinateurs de bureau, les ordinateurs portatifs et, de plus en plus, les appareils mobiles comme les téléphones intelligents et les tablettes. Pour suivre le rythme de la demande et procurer une expérience satisfaisante à tous les utilisateurs, il faut examiner trois différents aspects des exigences :

  1. Le besoin d’exigences relatives à la fonctionnalité et à l’inclusion au niveau de l’entreprise, notamment :
    1. Les exigences fonctionnelles des utilisateurs finaux handicapés comprenant les techniques, outils et technologies d’adaptation suivants :
      1. Amélioration de la vision;
      2. Substitution de la vision;
      3. Amélioration et substitution audio;
      4. Amélioration et substitution de la mobilité et de la dextérité;
      5. Amélioration du style cognitif et d’apprentissage.
      6. Les tâches précisées et les capacités des utilisateurs.
  2. La conception des applications qui constituent la solution et la façon dont elles se rattachent aux deux éléments suivants :
    1. Les normes officielles du fabricant du système d’exploitation;
    2. Les normes des applications d’origine accessibles.
  3. Les besoins des utilisateurs individuels en matière de technologie adaptée et de fonctionnalité intégrée.

Comprendre les techniques, les outils et la technologie d’adaptation

Technologie d’amélioration de la vision

La technologie d’amélioration de la vision est utilisée par un grand nombre de personnes qui souffrent d’une forme de déficience visuelle (communément appelée « basse vision »), mais qui peuvent encore se fier à la vision pour consommer l’information. Les exigences peuvent varier beaucoup pour ce qui est de la manière et du niveau de caractéristiques requis (c.-à-d. une personne ayant un champ visuel différent aura besoin de réglages qui sont différents de ceux dont a besoin une personne atteinte de glaucome ou d’une forme de daltonisme).

L’information est souvent présentée différemment, par exemple avec des couleurs très contrastantes, de gros caractères ou un agrandissement. Souvent, le système doit être utilisable avec une basse vision sans compter sur les fonctions audio. Une basse vision s’accompagne parfois d’une perte auditive, ce qui est particulièrement courant chez les personnes âgées. Les fonctions audio à elles seules en tant que stratégie d’accessibilité ne permettront pas de répondre aux besoins de ce groupe. Les programmes d’agrandissement d’écran (également appelés des programmes de gros caractères) permettent aux utilisateurs d’agrandir une partie de leurs écrans. Le moniteur d’ordinateur se transforme effectivement en une fenêtre d’affichage qui montre une partie seulement d’un affichage virtuel agrandi. L’utilisateur peut ensuite utiliser la souris ou les commandes du clavier pour déplacer cette fenêtre d’affichage afin de visualiser différentes zones de l’affichage virtuel.

Technologie de substitution de la vision

La technologie de substitution de la vision est utilisée par les personnes souffrant d’une forme de déficience visuelle (communément appelée « cécité »), qui ne peuvent plus se fier à la vision, ou ne l’ont jamais fait, pour consommer l’information. Souvent, l’information est présentée par un moyen différent, comme le braille ou un moteur texte-voix. Windows de Microsoft, Windows Mobile, Linux, Blackberry OS, Apple Mac OS, iOS, Android et Chrome OS de Google (parmi d’autres) offrent tous des solutions aux utilisateurs aveugles qui utilisent les logiciels de lecture d’écran pour divers appareils. Les lecteurs d’écran tentent de reconnaître et d’interpréter ce qui est affiché à l’écran. L’information est ensuite représentée à l’utilisateur avec du texte-voix, du son, des icônes haptiques ou une sortie braille. Le lecteur d’écran suit ce qui se produit (p. ex. une ouverture de fenêtre) et les interventions qui sont effectuées sur un dispositif muni d’un clavier physique, d’un D-Pad, d’une boule de commande ou d’une manette de jeu. Dans le cas d’un appareil doté d’un écran tactile, il modifie la façon dont se comporte l’écran tactile et offre des méthodes d’interaction tactile. Il y a également la technologie d’exploration tactile qui permet à une personne aveugle d’explorer l’écran en le touchant, sans activer les éléments à l’écran. De plus, le lecteur d’écran peut fournir de la rétroaction au sujet des éléments de l’écran en émettant des alertes audio ou haptiques. Il fournit également du texte oral comme commandes et de l’information lorsqu’on y touche. Un ensemble de gestes supplémentaires permettent de se déplacer d’un élément à l’autre à l’écran et d’activer des fonctions précises du lecteur d’écran (p. ex. lire un bloc de texte).

Technologie d’amélioration et de substitution de l’audio

La technologie d’amélioration et de substitution de l’audio est utilisée par les personnes souffrant d’une forme de trouble auditif et par certains utilisateurs souffrant d’un trouble de la parole. Cette catégorie de technologie englobe divers besoins et exigences. Les solutions peuvent être aussi simples que la compatibilité avec un appareil auditif doté d’un capteur téléphonique, ou aussi complexes que l’accès à un téléimprimeur (TTY).

Il faut souvent que les systèmes d’information soient utilisables sans pouvoir les entendre. L’information communiquée par des fonctions audio seulement est inaccessible pour les personnes sourdes. De plus, il faut que les systèmes d’information soient utilisables par des personnes ayant une déficience auditive. Souvent, ces personnes ont également une déficience visuelle, surtout chez les personnes plus âgées. Il est donc important de permettre à ces personnes de se fier à l’audition résiduelle plutôt qu’à la vision (c.-à-d. les méthodes d’accès utilisées par des personnes sourdes).

Les personnes qui n’entendent pas les bips ou qui ne reconnaissent pas les mots prononcés pourraient avoir besoin d’un programme qui les sollicite autrement, notamment un clignotement à l’écran, ou bien l’affichage de messages prononcés sous forme de texte ou de signaux sonores traduits en signaux visuels.

Technologie d’amélioration et de substitution de la mobilité et de la dextérité

La technologie de mobilité et de dextérité sert aux personnes ayant une déficience ou une limitation physique. Cette catégorie de technologie englobe divers besoins et exigences. Les solutions sont parfois aussi simples que la saisie par mode de substitution ou la reconnaissance de la voix, parfois aussi complexes que le balayage avec accès à un dispositif d’entrée. Dispositifs d’entrée (mobilité) : divers dispositifs d’entrée sont offerts sur le marché pour cliquer, glisser ou toucher de pair avec un dispositif pour déplacer le curseur. Les dispositifs d’entrée peuvent aussi servir pour communiquer avec un dispositif au moyen de systèmes divers de codage, notamment le code Morse, dont certaines personnes atteintes de graves déficiences physiques se servent pour entrer du texte.

Technologie de reconnaissance vocale permet à l’utilisateur de commander le dispositif et d’entrer du texte en parlant. La reconnaissance de la voie devient courante, mais son application dans l’industrie de la technologie adaptée a toujours été importante. Elle permet d’utiliser des dispositifs mains libres. En plus d’être utilisables par des personnes dont les besoins relatifs à la dextérité ou la mobilité sont différents, les systèmes doivent souvent être utilisables sans égard à la gravité de la déficience physique. Pour une personne atteinte d’une déficience physique, par exemple une limite de la force, de la portée ou de la manipulation, des tremblements ou un manque de sensation, la technologie peut offrir des modes de fonctionnement qui ne font pas appel au contrôle de la motricité fine ou à des actions simultanées, qui sont possibles si la personne a une force et une portée limitées et qui ne dépendent pas d’un délai de réponse.

Technologie d’amélioration du style cognitif et d’apprentissage

Les troubles cognitifs et d’apprentissage sont des problèmes de traitement neurologiques. Ces problèmes de traitement peuvent interférer avec les compétences d’apprentissage telles que la lecture, l’écriture et / ou les mathématiques. Ils peuvent également interférer avec les compétences de niveau supérieur telles que l’organisation, la planification du temps, le raisonnement abstrait, la mémoire à long ou à court terme et l’attention. Cette catégorie de technologie englobe divers besoins et exigences.

Les solutions sont parfois aussi simples que des calendriers ou des systèmes de gestion des tâches, parfois aussi complexes que la lecture de documents multimodaux.

La reconnaissance de la voix aide les personnes atteintes de dyslexie ou de dysgraphie qui pourraient avoir de la difficulté à s’exprimer.

De plus, certains logiciels conçus pour faciliter le processus d’entrée de texte dans un ordinateur par l’emploi d’outils tels que le vérificateur d’orthographe phonétique et le thésaurus avancé sont d’usage courant. D’habitude, une combinaison de systèmes d’agrandissement et de lecture d’écran et de dispositifs de saisie par mode de substitution sert à donner à ces personnes l’accès à un ordinateur.

Les déficiences cognitives prennent de nombreuses formes, notamment le syndrome de Down, les troubles de la mémoire à court et à long termes et les différences de perception. Une conception appropriée peut accroître la fonctionnalité d’un ordinateur pour les personnes ayant des déficiences cognitives légères.

Le syndrome de stress visuel (commotion cérébrale) est une affection neurologique qui interfère avec la lecture, l’attention, la coordination, la santé générale et le comportement, et peut se produire malgré une vision normale. Le stress visuel se produit lorsque des stimuli tels que les modèles, le contraste, la lumière et la couleur affectent le cortex visuel, altérant la fonction cérébrale et entraînant des symptômes d’inconfort physique et de distorsions perceptuelles. Des solutions telles que des filtres colorés ont été montrées pour réduire les effets de ces stimuli, calmant le stress et rétablissant le fonctionnement du cerveau.

Certaines déficiences neurologiques rendent la parole difficile et les systèmes qui parlent à la place de l’utilisateur peuvent aider les personnes atteintes d’un trouble de la parole. La plupart des progiciels de ce genre exploitent un synthétiseur de parole.

Élimination des obstacles à la facilité d’utilisation

Les obstacles courants auxquels les utilisateurs se heurtent en naviguant dans Internet et en accédant à l’information au moyen de la technologie peuvent se regrouper dans les catégories suivantes :

  1. Obstacles critiques : ils empêchent une personne d’utiliser un site ou une caractéristique avec succès;
  2. Obstacles graves : ils causent la frustration, ralentissent l’utilisateur ou nécessitent une solution de rechange;
  3. Obstacles modérés : ils sont contrariants et frustrants, mais n’empêchent pas la personne d’utiliser le site;
  4. Obstacles mineurs : des bruits qui ne causent peut-être pas de problème pour la personne, mais qui nuisent à la crédibilité.

Il ne s’agit pas tout simplement de listes de vérification; dans l’inclusion, il s’agit de personnes. Le respect des Règles pour l’accessibilité des contenus Web (WCAG 2.0) permettra de rendre le contenu Web plus accessible, mais la question importante est la suivante : le contenu sera-t-il utilisable?

Faire participer les utilisateurs aux projets

L’accessibilité est une question à aborder au début du cycle de vie du projet. Dès le lancement d’un projet, elle doit faire partie des processus de conception centrée sur l’utilisateur (CCU). L’une des méthodes de CCU consiste en l’utilisation de personas. La création de personas diverses permettra aux concepteurs de logiciels de comprendre les besoins en matière d’accessibilité et de mettre en place des solutions plus inclusives.

Intégration des besoins en matière d’accessibilité aux personas

La création de personas handicapés nécessite une attention particulière compte tenu d’une longue liste de facteurs clés à prendre en considération :

Exemple de personas généraux handicapés

Thomas

Il a 18 ans, vit avec sa famille et fréquente l’école secondaire. Il utilise les ordinateurs à l’école, un ordinateur portable chez lui et un téléphone mobile de base offrant le service d’envoi de messages courts (SMS). Il aime les sites Web constants et qui lui sont familiers.

Catégorie de handicap
Amélioration du style cognitif et d’apprentissage.
Handicap
Il est atteint d’un trouble du spectre de l’autisme.
Capacités
Il fait agrandir le texte et utilise un programme qui cache tout sauf le texte pour ne pas être distrait.
Aptitudes
Il utilise bien l’ordinateur pour jouer des jeux, mais il apprend difficilement de nouveaux sites.
Attitude
Il préfère des sites familiers et une routine établie.
Technologie adaptée
Il utilise le réglage des paramètres du texte et un clavier bureautique.

Émilie

Elle a 24 ans, est diplômée de l’école secondaire et travaille sur un diplôme collégial. Elle vit dans un petit centre de vie autonome et travaille à temps partiel dans un centre communautaire local. Elle veut être entièrement autonome.

Catégorie de handicap
Amélioration et substitution de la mobilité et de la dextérité.
Handicap
Elle est atteinte de paralysie cérébrale; elle a de la difficulté à se servir de ses mains et à parler clairement.
Capacités
Elle utilise un fauteuil roulant motorisé.
Aptitudes
Elle utilise bien l’ordinateur à l’aide du bon dispositif d’entrée et elle trouve facilement des mots de recherche efficaces.
Attitude
Elle veut tout faire elle-même et parfois, elle est impatiente.
Technologie adaptée
Elle utilise un outil de communication augmentatif et alternatif (CAA) avec un générateur de parole, un iPad et un fauteuil roulant motorisé.

Francis

Ancien combattant, il a 30 ans et il vit avec sa copine. Il utilise un ordinateur portable chez lui et des ordinateurs dans les centres communautaires et les bibliothèques. Il a un iPhone. Il travaille à temps partiel comme réceptionniste au centre communautaire. Il a de la difficulté à se concentrer, à se souvenir de choses, à gérer le stress, à réfléchir et à écrire ou parler clairement. Il a de la difficulté à organiser et à gérer son temps, ce qui a tendance à lui causer des problèmes dans des situations sociales et professionnelles.

Catégorie de handicap
Amélioration du style cognitif et d’apprentissage
Handicap
Il est atteint du trouble de stress post-traumatique (TSPT) et de déficiences cognitives.
Capacités
Il lit et écrit lentement; il a besoin de plus de temps pour traiter l’information.
Aptitudes
Auparavant, il utilisait couramment des ordinateurs, mais il trouve maintenant qu’il est plus difficile de réaliser des tâches professionnelles.
Attitude
Il utilise couramment des ordinateurs, mais il est susceptible à des crises épileptiques et des pertes de conscience et il trouve certains sites trop stimulants.
Technologie adaptée
Il utilise des caractéristiques intelligentes et de traitement telles que des agents logiciels, des rappels et des vérificateurs d’orthographe de pair avec des adaptations aux systèmes d’entrée ou de sortie. Autres logiciel de gestion du temps; générateur de bruit blanc; logiciel de remue-méninges; logiciel pour noter rapidement des idées (Quick Note); logiciel de saisie semi-automatique.

Jacob

Il a 32 ans. Il a un diplôme collégial, suit des cours de formation juridique et partage un appartement avec un ami. Parajuriste, il examine des cas et rédige des résumés de cas. Il utilise un ordinateur portable, un afficheur Braille et un iPhone. La bonne technologie lui permet de faire tout ce qu’il veut.

Catégorie de handicap
Substitution de la vision.
Handicap
Il est aveugle de naissance.
Capacités
Il a une perception lumineuse.
Aptitudes
Il est un utilisateur habile de la technologie.
Attitude
C’est un natif numérique parmi les premiers utilisateurs de nouvelles technologies qui persiste jusqu’à ce qu’il réussisse.
Technologie adaptée
Il utilise un lecteur d’écran, un logiciel de prise de notes audio et un afficheur Braille.

Lea

Elle a 35 ans et a fait une maîtrise. Elle est rédactrice pour une publication spécialisée et travaille de chez elle. Personne ne comprend qu’il s’agit bel et bien d’un handicap.

Catégorie de handicap
Amélioration de la mobilité et de la dextérité.
Handicap
Elle souffre de fibromyalgie.
Capacités
Elle souffre de fatigue en raison de la fibromyalgie. Elle utilise une boule de commande et un clavier spécialisé.
Aptitudes
C’est une utilisatrice moyenne.
Attitude
Elle voudrait que les gens comprennent jusqu’à quel point il est difficile parfois pour elle de composer avec sa journée.
Technologie adaptée
Elle utilise un clavier réglable, un clavier bureautique et le logiciel de reconnaissance vocale _Naturally Speaking_ de Dragon.

Stéphane

Il a 38 ans et a fréquenté une école des beaux-arts. Il travaille comme graphiste dans une petite agence de publicité. Il utilise un iPad, un iPhone, un ordinateur portable MacBook Pro et il a un bon ordinateur au travail. Son unique handicap, c’est que ce n’est pas tout le monde qui communique en langage gestuel.

Catégorie de handicap
Substitution audio.
Handicap
Il est sourd de naissance.
Capacités
Sa langue maternelle est le langage gestuel américain (ASL). Il sait parler et lire sur les lèvres. Il utilise le service d’envoi de messages courts (SMS), la messagerie instantanée (IM), le logiciel Skype et le vidéoclavardage.
Aptitudes
Il est habile avec des outils graphiques et préfère le visuel au texte. Il a une mauvaise orthographe, ce qui rend les recherches plus difficiles.
Attitude
L’accessibilité et en particulier, le manque de sous-titre, peut l’irriter.
Technologie adaptée
Il utilise le langage gestuel, le service CART (transcription en temps réel des communications), les sous-titres et le vidéoclavardage.

Nancy

Elle a 45 ans et depuis quatre ans, elle exploite des technologies informatiques qui lui donnent un accès autonome à la lecture et à des communications écrites.

Catégorie de handicap
Substitution audio et de la vision.
Handicap
Elle est sourde et aveugle et elle ne parle pas. Ses compétences en langage gestuel (ASL) sont limitées.
Capacités
Elle sait lire le braille abrégé et elle utilise un téléphone muni d’un TTY Braille.
Attitude
Elle utilise le langage gestuel pour communiquer avec d’autres à l’aide d’un interprète ou d’un facilitateur.
Attitude
Elle peut devenir facilement frustrée quand les services dont elle a besoin pour communiquer ne sont pas fournis ou n’existent pas.
Technologie adaptée
Elle utilise un lecteur d’écran, un afficheur Braille, un téléphone muni d’un TTY Braille et un logiciel TTY.

Vishnu

Il a 48 ans et il est diplômé en ingénierie. Il travaille sur des projets internationaux pour une entreprise de logiciels médicaux. Né en Inde, il a terminé ses études supérieures en Malaisie et il vit à Singapour. Il utilise la haute technologie au travail, deux téléphones mobiles et un ordinateur portatif personnel. Il veut être au même niveau que tout le monde.

Catégorie de handicap
Amélioration de la vision.
Handicap
Il a une basse vision.
Capacités : Il parle trois langues
le gujarati, le hindi, l’anglais et un peu le mandarin. Il utilise le réglage du contraste pour bien voir l’écran.
Aptitudes
C’est un utilisateur expert d’outils techniques. Il trouve frustrantes les recherches d’une langue à une autre.
Attitude
Il se voit comme un citoyen du monde et veux pouvoir utiliser n’importe quel site.
Technologie adaptée
Il utilise le réglage du contraste, l’agrandissement de l’écran et des feuilles de style personnalisées.

Maria

Elle a 49 ans. Elle est titulaire d’un diplôme de collège communautaire et d’un certificat en soins de santé. Elle est mariée et ses enfants sont adultes. Elle parle l’espagnol et l’anglais. Elle est agente de santé communautaire. Elle utilise un téléphone intelligent et l’ordinateur personnel chez elle sert principalement à son mari pour son travail. Elle est contente avec ce qu’elle a pourvu qu’elle puisse trouver ce qu’elle cherche.

Catégorie de handicap
Amélioration du style cognitif et d’apprentissage.
Handicap
Elle est dyslexique.
Capacités
Elle préfère les sites en espagnol quand elle peut les trouver. Elle a besoin d’information et de directives clairement écrites.
Aptitudes
Elle a l’esprit aventurier, mais elle n’est pas très autonome, son mari et sa fille posent des signets pour elle.
Attitude
Elle pense que c’est merveilleux d’avoir ses sites Web avec elle en tout temps.
Technologie adaptée
Elle utilise le logiciel Skype et des sites de traduction en ligne.

Marie

Elle a 52 ans et elle est titulaire d’un diplôme collégial. Elle vit avec sa sœur. Elle a travaillé dans un cabinet de dentiste comme réceptionniste pendant 20 ans. Depuis cinq ans, elle reçoit des prestations d’invalidité.

Catégorie de handicap
Amélioration de la vision; amélioration de la mobilité et de la dextérité.
Handicap
Elle est atteinte de sclérose en plaques chronique progressive et de déficiences motrice et sensorielle.
Capacités
Elle utilise un fauteuil roulant motorisé qu’elle commande au moyen d’une manette de jeu pour se déplacer. Sa vision est très limitée et fluctuante.
Aptitudes
Avant, elle utilisait couramment les ordinateurs, mais maintenant, ses capacités physiques sont extrêmement limitées.
Attitude
Elle aime utiliser les ordinateurs, mais elle s’irrite quand elle ne peut accéder à certaines caractéristiques.
Technologie adaptée
Elle peut utiliser un ordinateur à l’aide d’un clavier programmable. Les touches d’un pouce carré présentent de gros caractères noirs sur un fond blanc pour l’aider à taper. Les jours où sa vision est au point le plus faible, elle dépend de la mémoire motrice pour accéder à son clavier. Les jours où ça va mieux, elle lit parfois en faisant agrandir le texte de 8 fois ou plus.

Carole

Elle a 74 ans et son mari est décédé il y a un an. Elle habite un appartement près de l’une de ses filles et de certains de ses petits-enfants (âgés de 6 à 16 ans). Elle est à la retraite après avoir travaillé comme aide-comptable dans une entreprise de construction. Elle utilise un ancien ordinateur chez elle et un téléphone mobile de base. Elle dit que ses petits-enfants la traînent dans le monde de la technologie.

Catégorie de handicap
Amélioration audio et de la vision.
Handicap
Elle montre les premiers signes de dégénérescence maculaire, souffre d’arthrite légère et porte une prothèse auditive.
Capacités
Son ordinateur n’est muni d’aucune technologie adaptée.
Aptitudes
Elle utilisait des ordinateurs quand elle travaillait comme aide-comptable, mais maintenant ses petits-enfants s’occupent de la mise à jour de son ancien ordinateur personnel.
Attitude
Elle a de la volonté, mais n’a pas l’esprit aventurier.
Technologie adaptée
Elle utilise l’agrandissement du texte, sans toucher beaucoup à d’autres réglages.

Exemple de personas d’employés handicapées du gouvernement du Canada

Jean-Marc

Il a 33 ans et il est diplômé d’une école des beaux-arts. Il travaille comme graphiste à la Direction générale des communications d’Affaires autochtones et du Nord Canada (AAND). Il utilise couramment les produits Apple (iPad, iPhone, MacBook Pro). Il est d’avis que son unique handicap est le fait que ce n’est pas tout le monde qui communique en langage gestuel.

Catégorie de handicap
Substitution audio.
Handicap
Il est sourd de naissance.
Capacités
Sa langue maternelle est le langage gestuel américain (ASL). Il sait parler et lire sur les lèvres. Il utilise le service d’envoi de messages courts (SMS), la messagerie instantanée (IM), le logiciel Skype et le vidéoclavardage.
Aptitudes
Il est habile avec des outils graphiques et des logiciels, très cultivé en informatique et il préfère le visuel au texte. Il a une mauvaise orthographe et sa grammaire anglaise laisse à désirer, ce qui rend difficile la recherche de soutien sur le Web.
Attitude
Il a tendance à s’irriter facilement au sujet de l’accessibilité, notamment le manque de sous-titre dans les vidéos ou les tutoriels.
Technologie adaptée
Il utilise le langage gestuel, le service CART (transcription en temps réel des communications), les sous-titres et le vidéoclavardage.

Abdul

C’est un ingénieur de structures âgé de 51 ans ayant une basse vision. Il est titulaire d’un baccalauréat spécialisé en génie. Il travaille à Affaires mondiales Canada sur des projets internationaux axés sur l’aide aux pays ravagés par la guerre aux fins de la reconstruction de leurs infrastructures. Il est constamment en déplacement et il est sur appel presque 24 heures sur 24, 7 jours sur 7. Il utilise deux téléphones mobiles, une tablette et un ordinateur portatif de travail ainsi qu’un ordinateur portatif personnel. Malgré sa basse vision, il s’efforce d’être au même niveau que tout le monde.

Catégorie de handicap
Amélioration de la vision.
Handicap
Il a une basse vision.
Capacités : Il parle trois langues
le gujarati, le hindi, l’anglais et un peu le mandarin. C’est un utilisateur très habile d’ordinateurs qui utilise le réglage du contraste pour bien voir l’écran.
Aptitudes
C’est un utilisateur expert d’outils techniques. Il a tendance à devenir frustré lors de ses recherches d’une langue à une autre et il trouve que certains appareils de l’étranger manquent de réglages d’adaptation.
Attitude
Il se considère comme un citoyen du monde. Il souhaite pouvoir utiliser n’importe quel site lorsqu’il passe des heures innombrables à faire des recherches, peu importe la langue ou le fait que la configuration des réglages de son ordinateur ou de son appareil mobile est personnalisée.
Technologie adaptée
Il utilise le réglage du contraste, l’agrandissement de l’écran et des feuilles de style personnalisées.

Yvette

Elle a 35 ans et elle est traductrice. Elle a fait une maîtrise en langue française et elle travaille comme traductrice pour le Bureau de la traduction à Services publics et Approvisionnement Canada. Elle travaille de chez elle et peut passer des heures à la fois à relire, à réviser et à traduire du contenu de tous les ministères du gouvernement du Canada. Ce qui la dérange le plus, c’est qu’elle a l’impression que personne ne comprend vraiment ce qu’elle vit au quotidien sur le plan physique et qu’elle a véritablement un handicap.

Catégorie de handicap
Amélioration de la mobilité et de la dextérité.
Handicap
Elle souffre de fibromyalgie.
Capacités
Elle souffre de fatigue en raison de la fibromyalgie et d’anxiété extrême lorsque sa charge de travail augmente soudainement. Souvent, elle a des crampes dans les mains et elles se figent. Elle utilise une boule de commande et un clavier spécialisé pour effectuer des tâches quotidiennes.
Aptitudes
C’est une utilisatrice moyenne d’ordinateurs ayant des compétences avancées en Microsoft Office.
Attitude
Elle voudrait que les gens comprennent jusqu’à quel point il est difficile parfois pour elle de composer avec sa journée et de faire les projets qui lui sont affectés dans les délais prévus.
Technologie adaptée
Elle utilise un clavier réglable, un clavier bureautique, le logiciel de reconnaissance vocale _Naturally Speaking_ de Dragon et des touches programmées au préalable.

Denis

Il a 21 ans et il vit avec sa famille. Il a terminé ses études secondaires en suivant un programme spécialisé pour personnes autistes ou atteintes du trouble déficitaire de l’attention avec hyperactivité (TDAH). Il a acquis ses connaissances informatiques générales à l’école. Chez lui, il a un ordinateur portable standard et un téléphone mobile de base avec service d’envoi de messages courts (SMS). Il a été embauché comme préposé aux services de courrier à Services publics et Approvisionnement Canada (SPAC). Denis travaille mieux dans un environnement où la routine et les processus sont constants et familiers.

Catégorie de handicap
Amélioration du style cognitif et d’apprentissage.
Handicap
Il est atteint d’un trouble du spectre de l’autisme.
Capacités
Il fait agrandir le texte sur ses appareils (un ordinateur portatif et un téléphone cellulaire standard) et utilise un programme qui cache tout sauf le texte pour ne pas être distrait.
Aptitudes
Il utilise bien l’ordinateur pour jouer des jeux, mais il apprend difficilement de nouveaux sites ou logiciels.
Attitude
Il préfère les sites Web qui lui sont familiers et il travaille mieux quand la routine est établie.
Technologie adaptée
Il utilise le réglage des paramètres du texte et un clavier bureautique.

Georges

Il a 47 ans et a fait une maîtrise en langues étrangères. Il travaille comme traducteur à Affaires mondiales Canada et vit seul. Georges a un ordinateur portable et un iPhone qu’il utilise au quotidien à des fins professionnelles et personnelles. Il ne sait pas lire le braille. Il lui faut donc un lecteur de documents pour la majorité de l’information qu’il reçoit depuis qu’il a perdu la vue. Georges a un chien-guide et il utilise une canne blanche quand il navigue des lieux inconnus.

Catégorie de handicap
Substitution de la vision.
Handicap
Il a perdu la vue à l’âge de 38 ans par suite d’autres problèmes médicaux.
Capacités
Il a une perception lumineuse résiduelle.
Aptitudes
Auparavant personne voyante, c’est un utilisateur habile de la technologie.
Attitude
Il est très ouvert à l’apprentissage de nouvelles technologies et de nouveaux outils. Il apprend à utiliser des logiciels spécialisés pour lire du matériel électronique.
Technologie adaptée
Il utilise un lecteur d’écran et un logiciel de prise de notes audio.

Benoît

Il a 27 ans. Il est technicien marin dans la Marine royale canadienne et en mer pendant des périodes de six mois à la fois au minimum.

Catégorie de handicap
Amélioration audio.
Handicap
Il a perdu l’ouïe de l’oreille gauche et 65 % de l’ouïe de l’oreille droite par suite d’un accident survenu en mer.
Capacités
Il est physiquement apte à l’exception d’une perte auditive grave et, à quelques rares occasions, de légers troubles d’équilibre.
Aptitudes
Il n’a pas encore 30 ans et il a l’esprit ouvert. Il est donc ouvert à toute technologie qui pourrait faire en sorte que sa perte de l’ouïe ait moins d’incidence.
Technologie adaptée
Il porte une prothèse auditive dotée d’un capteur téléphonique.

Il faut garder à l’esprit la diversité des gens. Soyez attentifs à ne pas tenir pour acquis que tous les utilisateurs y compris les utilisateurs handicapés utilisent votre produit de la même manière. Les gens se servent de méthodes d’interaction, de stratégies d’adaptation et de configurations de la technologie adaptée différentes. Les expériences, les attentes et les préférences des gens sont différentes. Vos personas handicapés nécessitent des recherches réelles, et les personas ne remplacent pas les tests utilisateurs par de vraies personnes handicapées.

Références

  1. Politique sur l'obligation de prendre des mesures d'adaptation pour les personnes handicapées dans la fonction publique fédérale
  2. Persona (ergonomie)
  3. Accessibility in User-Centered Design: Personas (en anglais seulement)
  4. Norme sur l’optimisation des sites Web et des applications pour appareils mobiles

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Personas handicapés pour la conception d'une expérience utilisateur inclusive (EU)

Le cas d'inclure les handicaps dans les personas des utilisateurs, les types de technologies qu'ils utilisent et les échantillons de personas avec des handicaps.

Sur cette page

Le présent document a pour but d’aider l’utilisateur à comprendre la manière de créer des personas handicapés. Des personas sont des personnages fictifs créés pour représenter divers types d’utilisateurs dont l’utilisation d’un site, d’une marque ou d’un produit serait unique. Souvent, les développeurs conçoivent des sites Web, des applications Web de bureau et mobiles à leurs propres goûts, ce qui peut éventuellement créer des obstacles pour certains utilisateurs. Il est important de planifier pour un groupe diversifié d’utilisateurs présentant un vaste éventail de capacités et d’incapacités, de niveaux techniques, de capacités fonctionnelles et de degrés de familiarité avec les processus ou les activités. Un aspect important de la conception inclusive consiste à inclure les personnes handicapées dès la première étape de la conception, puis à toutes les étapes du cycle de vie du développement logiciel. On contribuera ainsi à élever l’accessibilité et la convivialité du produit final et à mieux assurer l’inclusion de tous. Le présent document est un recueil de données provenant de diverses sources et visant à créer une vision cohérente de la conception inclusive.

Créer l’égalité d’accès pour tous

Le gouvernement du Canada s’est engagé à fournir de l’information au public sous une forme accessible; il s’est également engagé à créer un milieu de travail inclusif et sans obstacle qui inclut les personnes handicapées. Ces deux engagements nécessitent le respect de normes, d’exigences et de lignes directrices et le soutien d’une grande utilisation de la technologie, notamment les divers outils de la technologie adaptée comme les logiciels, le matériel et les dispositifs à l’intention des utilisateurs handicapés.

Les utilisateurs accèdent à l’information par divers moyens : les ordinateurs de bureau, les ordinateurs portatifs et, de plus en plus, les appareils mobiles comme les téléphones intelligents et les tablettes. Pour suivre le rythme de la demande et procurer une expérience satisfaisante à tous les utilisateurs, il faut examiner trois différents aspects des exigences :

  1. Le besoin d’exigences relatives à la fonctionnalité et à l’inclusion au niveau de l’entreprise, notamment :
    1. Les exigences fonctionnelles des utilisateurs finaux handicapés comprenant les techniques, outils et technologies d’adaptation suivants :
      1. Amélioration de la vision;
      2. Substitution de la vision;
      3. Amélioration et substitution audio;
      4. Amélioration et substitution de la mobilité et de la dextérité;
      5. Amélioration du style cognitif et d’apprentissage.
      6. Les tâches précisées et les capacités des utilisateurs.
  2. La conception des applications qui constituent la solution et la façon dont elles se rattachent aux deux éléments suivants :
    1. Les normes officielles du fabricant du système d’exploitation;
    2. Les normes des applications d’origine accessibles.
  3. Les besoins des utilisateurs individuels en matière de technologie adaptée et de fonctionnalité intégrée.

Comprendre les techniques, les outils et la technologie d’adaptation

Technologie d’amélioration de la vision

La technologie d’amélioration de la vision est utilisée par un grand nombre de personnes qui souffrent d’une forme de déficience visuelle (communément appelée « basse vision »), mais qui peuvent encore se fier à la vision pour consommer l’information. Les exigences peuvent varier beaucoup pour ce qui est de la manière et du niveau de caractéristiques requis (c.-à-d. une personne ayant un champ visuel différent aura besoin de réglages qui sont différents de ceux dont a besoin une personne atteinte de glaucome ou d’une forme de daltonisme).

L’information est souvent présentée différemment, par exemple avec des couleurs très contrastantes, de gros caractères ou un agrandissement. Souvent, le système doit être utilisable avec une basse vision sans compter sur les fonctions audio. Une basse vision s’accompagne parfois d’une perte auditive, ce qui est particulièrement courant chez les personnes âgées. Les fonctions audio à elles seules en tant que stratégie d’accessibilité ne permettront pas de répondre aux besoins de ce groupe. Les programmes d’agrandissement d’écran (également appelés des programmes de gros caractères) permettent aux utilisateurs d’agrandir une partie de leurs écrans. Le moniteur d’ordinateur se transforme effectivement en une fenêtre d’affichage qui montre une partie seulement d’un affichage virtuel agrandi. L’utilisateur peut ensuite utiliser la souris ou les commandes du clavier pour déplacer cette fenêtre d’affichage afin de visualiser différentes zones de l’affichage virtuel.

Technologie de substitution de la vision

La technologie de substitution de la vision est utilisée par les personnes souffrant d’une forme de déficience visuelle (communément appelée « cécité »), qui ne peuvent plus se fier à la vision, ou ne l’ont jamais fait, pour consommer l’information. Souvent, l’information est présentée par un moyen différent, comme le braille ou un moteur texte-voix. Windows de Microsoft, Windows Mobile, Linux, Blackberry OS, Apple Mac OS, iOS, Android et Chrome OS de Google (parmi d’autres) offrent tous des solutions aux utilisateurs aveugles qui utilisent les logiciels de lecture d’écran pour divers appareils. Les lecteurs d’écran tentent de reconnaître et d’interpréter ce qui est affiché à l’écran. L’information est ensuite représentée à l’utilisateur avec du texte-voix, du son, des icônes haptiques ou une sortie braille. Le lecteur d’écran suit ce qui se produit (p. ex. une ouverture de fenêtre) et les interventions qui sont effectuées sur un dispositif muni d’un clavier physique, d’un D-Pad, d’une boule de commande ou d’une manette de jeu. Dans le cas d’un appareil doté d’un écran tactile, il modifie la façon dont se comporte l’écran tactile et offre des méthodes d’interaction tactile. Il y a également la technologie d’exploration tactile qui permet à une personne aveugle d’explorer l’écran en le touchant, sans activer les éléments à l’écran. De plus, le lecteur d’écran peut fournir de la rétroaction au sujet des éléments de l’écran en émettant des alertes audio ou haptiques. Il fournit également du texte oral comme commandes et de l’information lorsqu’on y touche. Un ensemble de gestes supplémentaires permettent de se déplacer d’un élément à l’autre à l’écran et d’activer des fonctions précises du lecteur d’écran (p. ex. lire un bloc de texte).

Technologie d’amélioration et de substitution de l’audio

La technologie d’amélioration et de substitution de l’audio est utilisée par les personnes souffrant d’une forme de trouble auditif et par certains utilisateurs souffrant d’un trouble de la parole. Cette catégorie de technologie englobe divers besoins et exigences. Les solutions peuvent être aussi simples que la compatibilité avec un appareil auditif doté d’un capteur téléphonique, ou aussi complexes que l’accès à un téléimprimeur (TTY).

Il faut souvent que les systèmes d’information soient utilisables sans pouvoir les entendre. L’information communiquée par des fonctions audio seulement est inaccessible pour les personnes sourdes. De plus, il faut que les systèmes d’information soient utilisables par des personnes ayant une déficience auditive. Souvent, ces personnes ont également une déficience visuelle, surtout chez les personnes plus âgées. Il est donc important de permettre à ces personnes de se fier à l’audition résiduelle plutôt qu’à la vision (c.-à-d. les méthodes d’accès utilisées par des personnes sourdes).

Les personnes qui n’entendent pas les bips ou qui ne reconnaissent pas les mots prononcés pourraient avoir besoin d’un programme qui les sollicite autrement, notamment un clignotement à l’écran, ou bien l’affichage de messages prononcés sous forme de texte ou de signaux sonores traduits en signaux visuels.

Technologie d’amélioration et de substitution de la mobilité et de la dextérité

La technologie de mobilité et de dextérité sert aux personnes ayant une déficience ou une limitation physique. Cette catégorie de technologie englobe divers besoins et exigences. Les solutions sont parfois aussi simples que la saisie par mode de substitution ou la reconnaissance de la voix, parfois aussi complexes que le balayage avec accès à un dispositif d’entrée. Dispositifs d’entrée (mobilité) : divers dispositifs d’entrée sont offerts sur le marché pour cliquer, glisser ou toucher de pair avec un dispositif pour déplacer le curseur. Les dispositifs d’entrée peuvent aussi servir pour communiquer avec un dispositif au moyen de systèmes divers de codage, notamment le code Morse, dont certaines personnes atteintes de graves déficiences physiques se servent pour entrer du texte.

Technologie de reconnaissance vocale permet à l’utilisateur de commander le dispositif et d’entrer du texte en parlant. La reconnaissance de la voie devient courante, mais son application dans l’industrie de la technologie adaptée a toujours été importante. Elle permet d’utiliser des dispositifs mains libres. En plus d’être utilisables par des personnes dont les besoins relatifs à la dextérité ou la mobilité sont différents, les systèmes doivent souvent être utilisables sans égard à la gravité de la déficience physique. Pour une personne atteinte d’une déficience physique, par exemple une limite de la force, de la portée ou de la manipulation, des tremblements ou un manque de sensation, la technologie peut offrir des modes de fonctionnement qui ne font pas appel au contrôle de la motricité fine ou à des actions simultanées, qui sont possibles si la personne a une force et une portée limitées et qui ne dépendent pas d’un délai de réponse.

Technologie d’amélioration du style cognitif et d’apprentissage

Les troubles cognitifs et d’apprentissage sont des problèmes de traitement neurologiques. Ces problèmes de traitement peuvent interférer avec les compétences d’apprentissage telles que la lecture, l’écriture et / ou les mathématiques. Ils peuvent également interférer avec les compétences de niveau supérieur telles que l’organisation, la planification du temps, le raisonnement abstrait, la mémoire à long ou à court terme et l’attention. Cette catégorie de technologie englobe divers besoins et exigences.

Les solutions sont parfois aussi simples que des calendriers ou des systèmes de gestion des tâches, parfois aussi complexes que la lecture de documents multimodaux.

La reconnaissance de la voix aide les personnes atteintes de dyslexie ou de dysgraphie qui pourraient avoir de la difficulté à s’exprimer.

De plus, certains logiciels conçus pour faciliter le processus d’entrée de texte dans un ordinateur par l’emploi d’outils tels que le vérificateur d’orthographe phonétique et le thésaurus avancé sont d’usage courant. D’habitude, une combinaison de systèmes d’agrandissement et de lecture d’écran et de dispositifs de saisie par mode de substitution sert à donner à ces personnes l’accès à un ordinateur.

Les déficiences cognitives prennent de nombreuses formes, notamment le syndrome de Down, les troubles de la mémoire à court et à long termes et les différences de perception. Une conception appropriée peut accroître la fonctionnalité d’un ordinateur pour les personnes ayant des déficiences cognitives légères.

Le syndrome de stress visuel (commotion cérébrale) est une affection neurologique qui interfère avec la lecture, l’attention, la coordination, la santé générale et le comportement, et peut se produire malgré une vision normale. Le stress visuel se produit lorsque des stimuli tels que les modèles, le contraste, la lumière et la couleur affectent le cortex visuel, altérant la fonction cérébrale et entraînant des symptômes d’inconfort physique et de distorsions perceptuelles. Des solutions telles que des filtres colorés ont été montrées pour réduire les effets de ces stimuli, calmant le stress et rétablissant le fonctionnement du cerveau.

Certaines déficiences neurologiques rendent la parole difficile et les systèmes qui parlent à la place de l’utilisateur peuvent aider les personnes atteintes d’un trouble de la parole. La plupart des progiciels de ce genre exploitent un synthétiseur de parole.

Élimination des obstacles à la facilité d’utilisation

Les obstacles courants auxquels les utilisateurs se heurtent en naviguant dans Internet et en accédant à l’information au moyen de la technologie peuvent se regrouper dans les catégories suivantes :

  1. Obstacles critiques : ils empêchent une personne d’utiliser un site ou une caractéristique avec succès;
  2. Obstacles graves : ils causent la frustration, ralentissent l’utilisateur ou nécessitent une solution de rechange;
  3. Obstacles modérés : ils sont contrariants et frustrants, mais n’empêchent pas la personne d’utiliser le site;
  4. Obstacles mineurs : des bruits qui ne causent peut-être pas de problème pour la personne, mais qui nuisent à la crédibilité.

Il ne s’agit pas tout simplement de listes de vérification; dans l’inclusion, il s’agit de personnes. Le respect des Règles pour l’accessibilité des contenus Web (WCAG 2.0) permettra de rendre le contenu Web plus accessible, mais la question importante est la suivante : le contenu sera-t-il utilisable?

Faire participer les utilisateurs aux projets

L’accessibilité est une question à aborder au début du cycle de vie du projet. Dès le lancement d’un projet, elle doit faire partie des processus de conception centrée sur l’utilisateur (CCU). L’une des méthodes de CCU consiste en l’utilisation de personas. La création de personas diverses permettra aux concepteurs de logiciels de comprendre les besoins en matière d’accessibilité et de mettre en place des solutions plus inclusives.

Intégration des besoins en matière d’accessibilité aux personas

La création de personas handicapés nécessite une attention particulière compte tenu d’une longue liste de facteurs clés à prendre en considération :

Exemple de personas généraux handicapés

Thomas

Il a 18 ans, vit avec sa famille et fréquente l’école secondaire. Il utilise les ordinateurs à l’école, un ordinateur portable chez lui et un téléphone mobile de base offrant le service d’envoi de messages courts (SMS). Il aime les sites Web constants et qui lui sont familiers.

Catégorie de handicap
Amélioration du style cognitif et d’apprentissage.
Handicap
Il est atteint d’un trouble du spectre de l’autisme.
Capacités
Il fait agrandir le texte et utilise un programme qui cache tout sauf le texte pour ne pas être distrait.
Aptitudes
Il utilise bien l’ordinateur pour jouer des jeux, mais il apprend difficilement de nouveaux sites.
Attitude
Il préfère des sites familiers et une routine établie.
Technologie adaptée
Il utilise le réglage des paramètres du texte et un clavier bureautique.

Émilie

Elle a 24 ans, est diplômée de l’école secondaire et travaille sur un diplôme collégial. Elle vit dans un petit centre de vie autonome et travaille à temps partiel dans un centre communautaire local. Elle veut être entièrement autonome.

Catégorie de handicap
Amélioration et substitution de la mobilité et de la dextérité.
Handicap
Elle est atteinte de paralysie cérébrale; elle a de la difficulté à se servir de ses mains et à parler clairement.
Capacités
Elle utilise un fauteuil roulant motorisé.
Aptitudes
Elle utilise bien l’ordinateur à l’aide du bon dispositif d’entrée et elle trouve facilement des mots de recherche efficaces.
Attitude
Elle veut tout faire elle-même et parfois, elle est impatiente.
Technologie adaptée
Elle utilise un outil de communication augmentatif et alternatif (CAA) avec un générateur de parole, un iPad et un fauteuil roulant motorisé.

Francis

Ancien combattant, il a 30 ans et il vit avec sa copine. Il utilise un ordinateur portable chez lui et des ordinateurs dans les centres communautaires et les bibliothèques. Il a un iPhone. Il travaille à temps partiel comme réceptionniste au centre communautaire. Il a de la difficulté à se concentrer, à se souvenir de choses, à gérer le stress, à réfléchir et à écrire ou parler clairement. Il a de la difficulté à organiser et à gérer son temps, ce qui a tendance à lui causer des problèmes dans des situations sociales et professionnelles.

Catégorie de handicap
Amélioration du style cognitif et d’apprentissage
Handicap
Il est atteint du trouble de stress post-traumatique (TSPT) et de déficiences cognitives.
Capacités
Il lit et écrit lentement; il a besoin de plus de temps pour traiter l’information.
Aptitudes
Auparavant, il utilisait couramment des ordinateurs, mais il trouve maintenant qu’il est plus difficile de réaliser des tâches professionnelles.
Attitude
Il utilise couramment des ordinateurs, mais il est susceptible à des crises épileptiques et des pertes de conscience et il trouve certains sites trop stimulants.
Technologie adaptée
Il utilise des caractéristiques intelligentes et de traitement telles que des agents logiciels, des rappels et des vérificateurs d’orthographe de pair avec des adaptations aux systèmes d’entrée ou de sortie. Autres logiciel de gestion du temps; générateur de bruit blanc; logiciel de remue-méninges; logiciel pour noter rapidement des idées (Quick Note); logiciel de saisie semi-automatique.

Jacob

Il a 32 ans. Il a un diplôme collégial, suit des cours de formation juridique et partage un appartement avec un ami. Parajuriste, il examine des cas et rédige des résumés de cas. Il utilise un ordinateur portable, un afficheur Braille et un iPhone. La bonne technologie lui permet de faire tout ce qu’il veut.

Catégorie de handicap
Substitution de la vision.
Handicap
Il est aveugle de naissance.
Capacités
Il a une perception lumineuse.
Aptitudes
Il est un utilisateur habile de la technologie.
Attitude
C’est un natif numérique parmi les premiers utilisateurs de nouvelles technologies qui persiste jusqu’à ce qu’il réussisse.
Technologie adaptée
Il utilise un lecteur d’écran, un logiciel de prise de notes audio et un afficheur Braille.

Lea

Elle a 35 ans et a fait une maîtrise. Elle est rédactrice pour une publication spécialisée et travaille de chez elle. Personne ne comprend qu’il s’agit bel et bien d’un handicap.

Catégorie de handicap
Amélioration de la mobilité et de la dextérité.
Handicap
Elle souffre de fibromyalgie.
Capacités
Elle souffre de fatigue en raison de la fibromyalgie. Elle utilise une boule de commande et un clavier spécialisé.
Aptitudes
C’est une utilisatrice moyenne.
Attitude
Elle voudrait que les gens comprennent jusqu’à quel point il est difficile parfois pour elle de composer avec sa journée.
Technologie adaptée
Elle utilise un clavier réglable, un clavier bureautique et le logiciel de reconnaissance vocale _Naturally Speaking_ de Dragon.

Stéphane

Il a 38 ans et a fréquenté une école des beaux-arts. Il travaille comme graphiste dans une petite agence de publicité. Il utilise un iPad, un iPhone, un ordinateur portable MacBook Pro et il a un bon ordinateur au travail. Son unique handicap, c’est que ce n’est pas tout le monde qui communique en langage gestuel.

Catégorie de handicap
Substitution audio.
Handicap
Il est sourd de naissance.
Capacités
Sa langue maternelle est le langage gestuel américain (ASL). Il sait parler et lire sur les lèvres. Il utilise le service d’envoi de messages courts (SMS), la messagerie instantanée (IM), le logiciel Skype et le vidéoclavardage.
Aptitudes
Il est habile avec des outils graphiques et préfère le visuel au texte. Il a une mauvaise orthographe, ce qui rend les recherches plus difficiles.
Attitude
L’accessibilité et en particulier, le manque de sous-titre, peut l’irriter.
Technologie adaptée
Il utilise le langage gestuel, le service CART (transcription en temps réel des communications), les sous-titres et le vidéoclavardage.

Nancy

Elle a 45 ans et depuis quatre ans, elle exploite des technologies informatiques qui lui donnent un accès autonome à la lecture et à des communications écrites.

Catégorie de handicap
Substitution audio et de la vision.
Handicap
Elle est sourde et aveugle et elle ne parle pas. Ses compétences en langage gestuel (ASL) sont limitées.
Capacités
Elle sait lire le braille abrégé et elle utilise un téléphone muni d’un TTY Braille.
Attitude
Elle utilise le langage gestuel pour communiquer avec d’autres à l’aide d’un interprète ou d’un facilitateur.
Attitude
Elle peut devenir facilement frustrée quand les services dont elle a besoin pour communiquer ne sont pas fournis ou n’existent pas.
Technologie adaptée
Elle utilise un lecteur d’écran, un afficheur Braille, un téléphone muni d’un TTY Braille et un logiciel TTY.

Vishnu

Il a 48 ans et il est diplômé en ingénierie. Il travaille sur des projets internationaux pour une entreprise de logiciels médicaux. Né en Inde, il a terminé ses études supérieures en Malaisie et il vit à Singapour. Il utilise la haute technologie au travail, deux téléphones mobiles et un ordinateur portatif personnel. Il veut être au même niveau que tout le monde.

Catégorie de handicap
Amélioration de la vision.
Handicap
Il a une basse vision.
Capacités : Il parle trois langues
le gujarati, le hindi, l’anglais et un peu le mandarin. Il utilise le réglage du contraste pour bien voir l’écran.
Aptitudes
C’est un utilisateur expert d’outils techniques. Il trouve frustrantes les recherches d’une langue à une autre.
Attitude
Il se voit comme un citoyen du monde et veux pouvoir utiliser n’importe quel site.
Technologie adaptée
Il utilise le réglage du contraste, l’agrandissement de l’écran et des feuilles de style personnalisées.

Maria

Elle a 49 ans. Elle est titulaire d’un diplôme de collège communautaire et d’un certificat en soins de santé. Elle est mariée et ses enfants sont adultes. Elle parle l’espagnol et l’anglais. Elle est agente de santé communautaire. Elle utilise un téléphone intelligent et l’ordinateur personnel chez elle sert principalement à son mari pour son travail. Elle est contente avec ce qu’elle a pourvu qu’elle puisse trouver ce qu’elle cherche.

Catégorie de handicap
Amélioration du style cognitif et d’apprentissage.
Handicap
Elle est dyslexique.
Capacités
Elle préfère les sites en espagnol quand elle peut les trouver. Elle a besoin d’information et de directives clairement écrites.
Aptitudes
Elle a l’esprit aventurier, mais elle n’est pas très autonome, son mari et sa fille posent des signets pour elle.
Attitude
Elle pense que c’est merveilleux d’avoir ses sites Web avec elle en tout temps.
Technologie adaptée
Elle utilise le logiciel Skype et des sites de traduction en ligne.

Marie

Elle a 52 ans et elle est titulaire d’un diplôme collégial. Elle vit avec sa sœur. Elle a travaillé dans un cabinet de dentiste comme réceptionniste pendant 20 ans. Depuis cinq ans, elle reçoit des prestations d’invalidité.

Catégorie de handicap
Amélioration de la vision; amélioration de la mobilité et de la dextérité.
Handicap
Elle est atteinte de sclérose en plaques chronique progressive et de déficiences motrice et sensorielle.
Capacités
Elle utilise un fauteuil roulant motorisé qu’elle commande au moyen d’une manette de jeu pour se déplacer. Sa vision est très limitée et fluctuante.
Aptitudes
Avant, elle utilisait couramment les ordinateurs, mais maintenant, ses capacités physiques sont extrêmement limitées.
Attitude
Elle aime utiliser les ordinateurs, mais elle s’irrite quand elle ne peut accéder à certaines caractéristiques.
Technologie adaptée
Elle peut utiliser un ordinateur à l’aide d’un clavier programmable. Les touches d’un pouce carré présentent de gros caractères noirs sur un fond blanc pour l’aider à taper. Les jours où sa vision est au point le plus faible, elle dépend de la mémoire motrice pour accéder à son clavier. Les jours où ça va mieux, elle lit parfois en faisant agrandir le texte de 8 fois ou plus.

Carole

Elle a 74 ans et son mari est décédé il y a un an. Elle habite un appartement près de l’une de ses filles et de certains de ses petits-enfants (âgés de 6 à 16 ans). Elle est à la retraite après avoir travaillé comme aide-comptable dans une entreprise de construction. Elle utilise un ancien ordinateur chez elle et un téléphone mobile de base. Elle dit que ses petits-enfants la traînent dans le monde de la technologie.

Catégorie de handicap
Amélioration audio et de la vision.
Handicap
Elle montre les premiers signes de dégénérescence maculaire, souffre d’arthrite légère et porte une prothèse auditive.
Capacités
Son ordinateur n’est muni d’aucune technologie adaptée.
Aptitudes
Elle utilisait des ordinateurs quand elle travaillait comme aide-comptable, mais maintenant ses petits-enfants s’occupent de la mise à jour de son ancien ordinateur personnel.
Attitude
Elle a de la volonté, mais n’a pas l’esprit aventurier.
Technologie adaptée
Elle utilise l’agrandissement du texte, sans toucher beaucoup à d’autres réglages.

Exemple de personas d’employés handicapées du gouvernement du Canada

Jean-Marc

Il a 33 ans et il est diplômé d’une école des beaux-arts. Il travaille comme graphiste à la Direction générale des communications d’Affaires autochtones et du Nord Canada (AAND). Il utilise couramment les produits Apple (iPad, iPhone, MacBook Pro). Il est d’avis que son unique handicap est le fait que ce n’est pas tout le monde qui communique en langage gestuel.

Catégorie de handicap
Substitution audio.
Handicap
Il est sourd de naissance.
Capacités
Sa langue maternelle est le langage gestuel américain (ASL). Il sait parler et lire sur les lèvres. Il utilise le service d’envoi de messages courts (SMS), la messagerie instantanée (IM), le logiciel Skype et le vidéoclavardage.
Aptitudes
Il est habile avec des outils graphiques et des logiciels, très cultivé en informatique et il préfère le visuel au texte. Il a une mauvaise orthographe et sa grammaire anglaise laisse à désirer, ce qui rend difficile la recherche de soutien sur le Web.
Attitude
Il a tendance à s’irriter facilement au sujet de l’accessibilité, notamment le manque de sous-titre dans les vidéos ou les tutoriels.
Technologie adaptée
Il utilise le langage gestuel, le service CART (transcription en temps réel des communications), les sous-titres et le vidéoclavardage.

Abdul

C’est un ingénieur de structures âgé de 51 ans ayant une basse vision. Il est titulaire d’un baccalauréat spécialisé en génie. Il travaille à Affaires mondiales Canada sur des projets internationaux axés sur l’aide aux pays ravagés par la guerre aux fins de la reconstruction de leurs infrastructures. Il est constamment en déplacement et il est sur appel presque 24 heures sur 24, 7 jours sur 7. Il utilise deux téléphones mobiles, une tablette et un ordinateur portatif de travail ainsi qu’un ordinateur portatif personnel. Malgré sa basse vision, il s’efforce d’être au même niveau que tout le monde.

Catégorie de handicap
Amélioration de la vision.
Handicap
Il a une basse vision.
Capacités : Il parle trois langues
le gujarati, le hindi, l’anglais et un peu le mandarin. C’est un utilisateur très habile d’ordinateurs qui utilise le réglage du contraste pour bien voir l’écran.
Aptitudes
C’est un utilisateur expert d’outils techniques. Il a tendance à devenir frustré lors de ses recherches d’une langue à une autre et il trouve que certains appareils de l’étranger manquent de réglages d’adaptation.
Attitude
Il se considère comme un citoyen du monde. Il souhaite pouvoir utiliser n’importe quel site lorsqu’il passe des heures innombrables à faire des recherches, peu importe la langue ou le fait que la configuration des réglages de son ordinateur ou de son appareil mobile est personnalisée.
Technologie adaptée
Il utilise le réglage du contraste, l’agrandissement de l’écran et des feuilles de style personnalisées.

Yvette

Elle a 35 ans et elle est traductrice. Elle a fait une maîtrise en langue française et elle travaille comme traductrice pour le Bureau de la traduction à Services publics et Approvisionnement Canada. Elle travaille de chez elle et peut passer des heures à la fois à relire, à réviser et à traduire du contenu de tous les ministères du gouvernement du Canada. Ce qui la dérange le plus, c’est qu’elle a l’impression que personne ne comprend vraiment ce qu’elle vit au quotidien sur le plan physique et qu’elle a véritablement un handicap.

Catégorie de handicap
Amélioration de la mobilité et de la dextérité.
Handicap
Elle souffre de fibromyalgie.
Capacités
Elle souffre de fatigue en raison de la fibromyalgie et d’anxiété extrême lorsque sa charge de travail augmente soudainement. Souvent, elle a des crampes dans les mains et elles se figent. Elle utilise une boule de commande et un clavier spécialisé pour effectuer des tâches quotidiennes.
Aptitudes
C’est une utilisatrice moyenne d’ordinateurs ayant des compétences avancées en Microsoft Office.
Attitude
Elle voudrait que les gens comprennent jusqu’à quel point il est difficile parfois pour elle de composer avec sa journée et de faire les projets qui lui sont affectés dans les délais prévus.
Technologie adaptée
Elle utilise un clavier réglable, un clavier bureautique, le logiciel de reconnaissance vocale _Naturally Speaking_ de Dragon et des touches programmées au préalable.

Denis

Il a 21 ans et il vit avec sa famille. Il a terminé ses études secondaires en suivant un programme spécialisé pour personnes autistes ou atteintes du trouble déficitaire de l’attention avec hyperactivité (TDAH). Il a acquis ses connaissances informatiques générales à l’école. Chez lui, il a un ordinateur portable standard et un téléphone mobile de base avec service d’envoi de messages courts (SMS). Il a été embauché comme préposé aux services de courrier à Services publics et Approvisionnement Canada (SPAC). Denis travaille mieux dans un environnement où la routine et les processus sont constants et familiers.

Catégorie de handicap
Amélioration du style cognitif et d’apprentissage.
Handicap
Il est atteint d’un trouble du spectre de l’autisme.
Capacités
Il fait agrandir le texte sur ses appareils (un ordinateur portatif et un téléphone cellulaire standard) et utilise un programme qui cache tout sauf le texte pour ne pas être distrait.
Aptitudes
Il utilise bien l’ordinateur pour jouer des jeux, mais il apprend difficilement de nouveaux sites ou logiciels.
Attitude
Il préfère les sites Web qui lui sont familiers et il travaille mieux quand la routine est établie.
Technologie adaptée
Il utilise le réglage des paramètres du texte et un clavier bureautique.

Georges

Il a 47 ans et a fait une maîtrise en langues étrangères. Il travaille comme traducteur à Affaires mondiales Canada et vit seul. Georges a un ordinateur portable et un iPhone qu’il utilise au quotidien à des fins professionnelles et personnelles. Il ne sait pas lire le braille. Il lui faut donc un lecteur de documents pour la majorité de l’information qu’il reçoit depuis qu’il a perdu la vue. Georges a un chien-guide et il utilise une canne blanche quand il navigue des lieux inconnus.

Catégorie de handicap
Substitution de la vision.
Handicap
Il a perdu la vue à l’âge de 38 ans par suite d’autres problèmes médicaux.
Capacités
Il a une perception lumineuse résiduelle.
Aptitudes
Auparavant personne voyante, c’est un utilisateur habile de la technologie.
Attitude
Il est très ouvert à l’apprentissage de nouvelles technologies et de nouveaux outils. Il apprend à utiliser des logiciels spécialisés pour lire du matériel électronique.
Technologie adaptée
Il utilise un lecteur d’écran et un logiciel de prise de notes audio.

Benoît

Il a 27 ans. Il est technicien marin dans la Marine royale canadienne et en mer pendant des périodes de six mois à la fois au minimum.

Catégorie de handicap
Amélioration audio.
Handicap
Il a perdu l’ouïe de l’oreille gauche et 65 % de l’ouïe de l’oreille droite par suite d’un accident survenu en mer.
Capacités
Il est physiquement apte à l’exception d’une perte auditive grave et, à quelques rares occasions, de légers troubles d’équilibre.
Aptitudes
Il n’a pas encore 30 ans et il a l’esprit ouvert. Il est donc ouvert à toute technologie qui pourrait faire en sorte que sa perte de l’ouïe ait moins d’incidence.
Technologie adaptée
Il porte une prothèse auditive dotée d’un capteur téléphonique.

Il faut garder à l’esprit la diversité des gens. Soyez attentifs à ne pas tenir pour acquis que tous les utilisateurs y compris les utilisateurs handicapés utilisent votre produit de la même manière. Les gens se servent de méthodes d’interaction, de stratégies d’adaptation et de configurations de la technologie adaptée différentes. Les expériences, les attentes et les préférences des gens sont différentes. Vos personas handicapés nécessitent des recherches réelles, et les personas ne remplacent pas les tests utilisateurs par de vraies personnes handicapées.

Références

  1. Politique sur l'obligation de prendre des mesures d'adaptation pour les personnes handicapées dans la fonction publique fédérale
  2. Persona (ergonomie)
  3. Accessibility in User-Centered Design: Personas (en anglais seulement)
  4. Norme sur l’optimisation des sites Web et des applications pour appareils mobiles

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/plateformes-de-reunions-virtuelles-et-fonctionnalites/index.html b/fr/plateformes-de-reunions-virtuelles-et-fonctionnalites/index.html index 4b2f8c38f..db9420ccc 100644 --- a/fr/plateformes-de-reunions-virtuelles-et-fonctionnalites/index.html +++ b/fr/plateformes-de-reunions-virtuelles-et-fonctionnalites/index.html @@ -1,4 +1,4 @@ -Plateformes de réunions virtuelles et fonctionnalités - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Plateformes de réunions virtuelles et fonctionnalités

Les plateformes de réunions virtuelles Microsoft Teams et Zoom offrent diverses fonctionnalités d’accessibilité qui répondent à différents besoins, entre autres pour les réunions et les conversations.

Microsoft Teams

Microsoft Teams est la plateforme de réunion standard pour les réunions virtuelles.

Réunion

Conversation

Plus de fonctionnalités

Zoom

Zoom n'est pas l'outil recommandé pour les réunions internes, mais c'est une option accessible à utiliser avec des partenaires externes pour des informations non classifiées. Dans certaines situations, détaillées dans la section Types de réunions proposées et fonctionnalités d’accessibilité, il s'agit de l'outil recommandé pour traiter avec des citoyens canadiens en raison des diverses fonctionnalités d'accessibilité intégrées.

Réunion

Conversation

Plus de fonctionnalités

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Plateformes de réunions virtuelles et fonctionnalités

Les plateformes de réunions virtuelles Microsoft Teams et Zoom offrent diverses fonctionnalités d’accessibilité qui répondent à différents besoins, entre autres pour les réunions et les conversations.

Microsoft Teams

Microsoft Teams est la plateforme de réunion standard pour les réunions virtuelles.

Réunion

Conversation

Plus de fonctionnalités

Zoom

Zoom n'est pas l'outil recommandé pour les réunions internes, mais c'est une option accessible à utiliser avec des partenaires externes pour des informations non classifiées. Dans certaines situations, détaillées dans la section Types de réunions proposées et fonctionnalités d’accessibilité, il s'agit de l'outil recommandé pour traiter avec des citoyens canadiens en raison des diverses fonctionnalités d'accessibilité intégrées.

Réunion

Conversation

Plus de fonctionnalités

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/recherche-sur-notre-audience/index.html b/fr/recherche-sur-notre-audience/index.html index 52e0b1e7f..1bdee2358 100644 --- a/fr/recherche-sur-notre-audience/index.html +++ b/fr/recherche-sur-notre-audience/index.html @@ -1,4 +1,4 @@ -Recherche sur notre audience - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Recherche sur notre audience

L’objectif principal de la création de ces persona était de mieux comprendre notre public cible. En développant une meilleure compréhension de nos utilisateurs, nous serons en mesure de construire une architecture de site réactive pour tout le contenu existant et futur hébergé sur le site Web de la boite à outils d’accessibilité numérique.

À propos de la création de notre personnage

L’objectif principal de la création de ces persona était de mieux comprendre notre public cible. En développant une meilleure compréhension de nos utilisateurs, nous serons en mesure de construire une architecture de site réactive pour tout le contenu existant et futur hébergé sur le site Web de la boite à outils d’accessibilité numérique.

Pour ce faire, nous devons :

Cadre de référence

Notre approche est modulaire: nous avons combiné deux types de persona pour créer un modèle qui représente mieux notre public cible. Nous avons utilisé les deux cadres suivants :

Persona de l’utilisateur ciblé

Persona responsable de l’accessibilité

Types d’incapacités et inclusivité

Dans nos persona, nous avons inclus une variété de handicaps et un éventail de limitations:

Nous croyons qu’il est important de tenir compte d’un large éventail d’expériences humaines. C’est pourquoi, pour chaque type d’incapacité, nous avons inclus différentes possibilités d’exclusion.

Sept (7) Persona

5 grands types d’incapacité et 2 types d’incapacité combinés

Brandon - Auditif

À propos

Pronoms
Il / Lui
Âge
52
Emploi
Expérience utilisateur (UX).
Sites couramment utilisés
IAAP, EFPC.
Handicap :
Deaf since birth.

Exemple de temporaire ou situationnel

  • Perte auditive temporaire due à une infection de l’oreille dans l’oreille droite.
  • Bruit de construction.

Compétences (aptitude)

  • Technophile et capable de prendre de nouveaux logiciels rapidement.
  • Connaît la langue des signes.

Outils (technologie d’adaptation, appareils, autres)

Catégorie: remplacement et amélioration audio.

  • Live sous-titrage codé dans les réunions.
  • Autre : Transcriptions pendant et après l’événement.

Besoins (tâches, environnements)

  • Préfère l’option de travailler à domicile.
  • Nécessite l’accès à son ordinateur portable tous les jours pour le travail.
  • Demande souvent que des instructions ou des conversations lui soient répétées.

Obstacles et frustrations (détails, attitudes)

  • Cela peut être vraiment frustrant lorsque les outils sont en retard ou ne sont pas disponibles.
  • Les services et applications Web qui reposent sur des interactions à l’aide de commandes vocales uniquement sont vraiment difficiles ou parfois impossibles à utiliser.
  • Les réunions de groupe, les réunions consécutives ou tout simplement trop de réunions dans une journée peuvent être épuisantes.

Citation :

« Lorsque de la musique joue pendant qu’un haut-parleur parle, c’est très distrayant. WCAG 2.1 a un critère qui dit que le bruit de fond doit être certains décibels en dessous de la voix de l’orateur, mais c’est un niveau AAA. Cela signifie qu’il n’est pas obligatoire pour les entreprises et les organisations de se conformer à ce critère. »

Alasie - Vision

À propos

Pronoms
Elle / Elle.
Âge
23
Emploi
Testeur d’accessibilité junior.
Sites couramment utilisés
W3C et Deque.
Handicap :
Vision floue avec un faible contraste.

Exemple de temporaire ou situationnel

  • Luminosité du soleil.

Compétences (aptitude)

  • Solide compréhension de la technologie d’assistance utilisée pour la navigation sur le Web.
  • Utilisateur d’ordinateur hautement qualifié qui utilise des réglages de contraste pour voir clairement l’écran.

Outils (technologie d’adaptation, appareils, autres)

Catégorie : Amélioration de la vision

  • Réglages des couleurs.
  • Vérificateur automatisé de l’accessibilité du Web.
  • Microsoft Teams.
  • Lecteur d’écran.
  • Logiciel de traitement de texte.
  • Grossissement de l’écran.

Besoins (tâches, environnements)

  • Exige l’accès aux lignes directrices sur l’accessibilité du Web et des documents lors de la réalisation des tests.
  • Temps de mise à l’essai adéquat de l’accessibilité des technologies de l’information et des communications (TIC) au sein du GC.
  • Les fichiers numériques seront disponibles dans des formats accessibles.

Obstacles et frustrations (détails, attitudes)

  • Perte de contenu web ou de fonctionnalités lorsque la taille de la police ou l’écran du navigateur est redimensionné.
  • Le texte à faible contraste peut être difficile à lire.
  • Images sur des sites Web qui ne fournissent pas d’alternatives textuelles.
  • Les conférenciers qui ne fournissent pas d’informations qui aident à comprendre les informations affichées visuellement.

Citation :

« C’est vraiment ennuyeux quand les couleurs du texte et de l’arrière-plan sont si proches les unes des autres, cela rend tout ce qui se trouve à l’écran difficile à lire. »

Yenah - Dextérité

À propos

Pronoms
Elle / Elle.
Âge
29
Emploi
Développeur frontal.
Sites couramment utilisés
WCAG pour les développeurs.
Handicap :
Fibromyalgie.

Exemple de temporaire ou situationnel

  • Arthrite inflammatoire.
  • Trajet en voiture cahoteux.

Compétences (aptitude)

  • Utilise des macbook et des produits Apple tous les jours pour son travail.
  • Techsavvy et s’appuie sur ses outils dans sa vie quotidienne.

Outils (technologie d’adaptation, appareils, autres)

Catégorie: Amélioration de la mobilité et de la dextérité.

  • Clavier ergonomique, souris.
  • Dragon Naturellement Parlant.
  • X-Keys préprogrammés.
  • Logiciel de reconnaissance vocale.

Besoins (tâches, environnements)

  • Préfère les mesures d’adaptation et la flexibilité de l’horaire de travail pour tenir compte du repos, du soutien médical, des styles de travail préférés.
  • Compréhension de leur équipe pour les différents niveaux d’inconfort qui peuvent survenir chaque jour.
  • Gestes de pointeur simples lors de la navigation dans les pages Web (ex: simple clic / robinet).
  • Liens avec les noms propres pour indiquer clairement où le lien mène et quel est son but.

Obstacles et frustrations (détails, attitudes)

  • Distractions en milieu de travail.
  • Des politiques en milieu de travail qui rendent les mesures d’adaptation du travail à domicile difficiles à obtenir.
  • Lorsque d’autres modèles d’interaction ne sont pas disponibles et que l’action requise est difficile à accomplir (ex: secouer un appareil, pincer, dessiner, etc.).

Citation :

« Les boutons sur l’écran de mon téléphone peuvent être si petits, je veux appuyer sur une case à cocher mais accidentellement cliquer sur une autre option, je dois décocher le mauvais pour continuer, mais c’est frustrant. »

Ike - Mobility

À propos

Pronoms
Ils / Eux.
Âge
31
Emploi
Formateur / Éducateur.
Sites couramment utilisés
AAACT, GcPedia, DAT.
Handicap :
Maladie du neurone moteur.

Exemple de temporaire ou situationnel

  • Tenir un bébé.
  • Fracture d’un membre.

Compétences (aptitude)

  • A de l’expérience dans la prestation de formation sur l’accessibilité du Web et des documents

Outils (technologie d’adaptation, appareils, autres)

Catégorie : Amélioration de la mobilité.

  • Dispositif de reconnaissance vocale.
  • Fauteuil roulant électrique.
  • Moniteurs réglables.
  • Claviers adaptatifs.

Besoins (tâches, environnements)

  • Renseignements sur la façon d’acquérir des mesures d’adaptation en milieu de travail en raison des politiques de retour obligatoire au bureau.
  • Méthode normalisée pour fournir aux stagiaires des ressources sur les normes, les politiques et les exigences en matière d’accessibilité au sein du GC.
  • Possibilité de visualiser le contenu Web en orientation portrait et paysage.

Obstacles et frustrations (détails, attitudes)

  • Difficulté à réserver un espace de travail via l’application Web désignée.
  • Difficulté à trouver des itinéraires accessibles à l’extérieur et à l’intérieur des bâtiments.
  • Bâtiments sans bouton de porte automatique.
  • Obstacles sur les routes accessibles, y compris les rampes et les corridors.

Citation :

« Je ne peux pas réserver un espace de travail comme tout le monde le fait parce que l’application ne prend pas en charge la navigation au clavier. »

Damien - Cognitive

À propos

Pronoms
Il / Lui.
Âge
48
Emploi
Gestionnaire en communications.
Sites couramment utilisés
Deque.
Handicap :
Trouble du spectre de l’autisme, Dyslexie.

Exemple de temporaire ou situationnel

  • Subir une commotion cérébrale.

Compétences (aptitude)

  • S’appuie sur le calendrier, les horaires et les applications d’organisation sur ordinateur de bureau et mobile.
  • Préfère avoir la possibilité de personnaliser mon environnement (ex: outils et technologie, lumière ambiante et température, affichage du moniteur, etc.

Outils (technologie d’adaptation, appareils, autres)

Catégorie: Amélioration du style cognitif et d’apprentissage.

  • Paramètres de préférence de texte, utilisateur de clavier d’alimentation.
  • Logiciel de synthèse vocale.

Besoins (tâches, environnements)

  • Fonctionne mieux avec des routines et des processus cohérents et familiers.
  • Lors de la communication, les termes utilisés dans les conversations doivent être littéraux, clairs et précis.
  • J’espère que les gens comprennent que les diagnostics de neurodiversité sont uniques, les besoins de 1 personne peuvent être différents de ceux d’une autre personne ayant le même handicap.
  • Sites avec plusieurs voies de navigation pour rendre le site plus facile à utiliser.

Obstacles et frustrations (détails, attitudes)

  • Pas génial avec la socialisation, comme les petites conversations, le contact visuel, la cueillette d’indices subtils et le toucher physique.
  • Traite souvent des maux de tête et des migraines.

Citation :

“When I’m using a website, I find it frustrating when there is no consistency in page layouts and some terminologies to confirm my actions can be difficult to understand.”

Valeria – Cognitive and Auditory

À propos

Pronoms
Elle / Elle.
Âge
62
Emploi
Agent des services administratifs.
Sites couramment utilisés
Salesforce, IAAP, DAT.
Handicap :
TDAH, trouble anxieux, perte auditive sévère, entendre des sons mais ne peut pas distinguer la parole

Exemple de temporaire ou situationnel

  • Les utilisateurs qui ne sont pas familiers avec Internet.
  • Locuteurs non natifs.

Compétences (aptitude)

  • Fonctionne mieux avec des routines et des processus cohérents et familiers.
  • Qualifié dans les applications Microsoft Office.

Outils (technologie d’adaptation, appareils, autres)

Catégorie: Amélioration du style cognitif et d’apprentissage et autres.

  • Lecteur d’écran.
  • Loupe de zoom.
  • Gestionnaire de mots de passe.

Besoins (tâches, environnements)

  • Aime travailler avec des outils automatisés comme le remplissage automatique / complet qui peut aider à remplir rapidement les informations et aide les utilisateurs à se souvenir de toutes leurs différentes informations de compte.
  • Travaille souvent dans des espaces du bureau avec des politiques d’intimité et de faible volume pour aider à éliminer les distractions et faciliter un travail approfondi.
  • Utilisation d’un langage simple et simple, exempt d’acronymes, de métaphores, d’argots, d’instructions explicatives et d’images descriptives.

Obstacles et frustrations (détails, attitudes)

  • Ne pas être capable de lire sur les lèvres et de voir les expressions faciales lorsque les gens ont des caméras éteintes pendant un appel vidéo.
  • Utilisation de légendes inexactes ou non personnalisables.

Citation :

« Lorsque je remplis un formulaire en ligne, il est difficile de terminer la tâche dans les délais donnés. C’est encore plus frustrant quand je ne sais pas combien de temps j’ai, le site chronoppe et supprime mon travail, et je dois refaire le formulaire à nouveau. «

Yosef – Mobilité et parole

À propos

Pronoms
Il / Lui.
Âge
39
Emploi
Agent de soutien administratif et de programme.
Sites couramment utilisés
GCdocs, GCXchange, DAT.
Handicap :
Fatigue musculaire et troubles de l’élocution

Exemple de temporaire ou situationnel

  • Les blessures de stress répétitives et ne peuvent pas parler dans certaines situations en raison de l’anxiété.
  • Se remettre d’une commotion cérébrale.

Compétences (aptitude)

  • Expérience de l’examen d’informations et de l’extraction d’informations critiques.
  • Nécessite souvent une exposition répétée au contenu pour le comprendre.

Outils (technologie d’adaptation, appareils, autres)

Catégorie : Remplacement ou amélioration de la mobilité et de la parole.

  • Paramètres de préférence de texte, utilisateur de clavier d’alimentation.
  • Logiciel de synthèse vocale. Logiciel de synthèse vocale.
  • Correcteurs orthographiques.
  • Clavier et souris ergonomiques.
  • Modèles et outils organisationnels.

Besoins (tâches, environnements)

  • Sites Web et navigateurs qui fournissent une prise en charge complète du clavier et fournissent des options pour passer aux sections principales de la page.
  • D’autres moyens de communication qui ne reposent pas beaucoup sur la parole. Par exemple, chat textuel, e-mail et formulaire de commentaires.
  • Doit utiliser un clavier et une souris ergonomiques pour une utilisation quotidienne au bureau.

Obstacles et frustrations (détails, attitudes)

  • Contenu Web accessible à l’aide d’un clavier.
  • Limites de temps insuffisantes pour effectuer des tâches telles que remplir un formulaire Web.
  • Centres de support et d’aide qui offrent des numéros de téléphone comme seul moyen de communiquer avec leur organisation.

Citation :

« Il peut être très fatigant d’avoir à parcourir des documents non pertinents pour atteindre le contenu dont j’ai besoin. «

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Recherche sur notre audience

L’objectif principal de la création de ces persona était de mieux comprendre notre public cible. En développant une meilleure compréhension de nos utilisateurs, nous serons en mesure de construire une architecture de site réactive pour tout le contenu existant et futur hébergé sur le site Web de la boite à outils d’accessibilité numérique.

À propos de la création de notre personnage

L’objectif principal de la création de ces persona était de mieux comprendre notre public cible. En développant une meilleure compréhension de nos utilisateurs, nous serons en mesure de construire une architecture de site réactive pour tout le contenu existant et futur hébergé sur le site Web de la boite à outils d’accessibilité numérique.

Pour ce faire, nous devons :

Cadre de référence

Notre approche est modulaire: nous avons combiné deux types de persona pour créer un modèle qui représente mieux notre public cible. Nous avons utilisé les deux cadres suivants :

Persona de l’utilisateur ciblé

Persona responsable de l’accessibilité

Types d’incapacités et inclusivité

Dans nos persona, nous avons inclus une variété de handicaps et un éventail de limitations:

Nous croyons qu’il est important de tenir compte d’un large éventail d’expériences humaines. C’est pourquoi, pour chaque type d’incapacité, nous avons inclus différentes possibilités d’exclusion.

Sept (7) Persona

5 grands types d’incapacité et 2 types d’incapacité combinés

Brandon - Auditif

À propos

Pronoms
Il / Lui
Âge
52
Emploi
Expérience utilisateur (UX).
Sites couramment utilisés
IAAP, EFPC.
Handicap :
Deaf since birth.

Exemple de temporaire ou situationnel

  • Perte auditive temporaire due à une infection de l’oreille dans l’oreille droite.
  • Bruit de construction.

Compétences (aptitude)

  • Technophile et capable de prendre de nouveaux logiciels rapidement.
  • Connaît la langue des signes.

Outils (technologie d’adaptation, appareils, autres)

Catégorie: remplacement et amélioration audio.

  • Live sous-titrage codé dans les réunions.
  • Autre : Transcriptions pendant et après l’événement.

Besoins (tâches, environnements)

  • Préfère l’option de travailler à domicile.
  • Nécessite l’accès à son ordinateur portable tous les jours pour le travail.
  • Demande souvent que des instructions ou des conversations lui soient répétées.

Obstacles et frustrations (détails, attitudes)

  • Cela peut être vraiment frustrant lorsque les outils sont en retard ou ne sont pas disponibles.
  • Les services et applications Web qui reposent sur des interactions à l’aide de commandes vocales uniquement sont vraiment difficiles ou parfois impossibles à utiliser.
  • Les réunions de groupe, les réunions consécutives ou tout simplement trop de réunions dans une journée peuvent être épuisantes.

Citation :

« Lorsque de la musique joue pendant qu’un haut-parleur parle, c’est très distrayant. WCAG 2.1 a un critère qui dit que le bruit de fond doit être certains décibels en dessous de la voix de l’orateur, mais c’est un niveau AAA. Cela signifie qu’il n’est pas obligatoire pour les entreprises et les organisations de se conformer à ce critère. »

Alasie - Vision

À propos

Pronoms
Elle / Elle.
Âge
23
Emploi
Testeur d’accessibilité junior.
Sites couramment utilisés
W3C et Deque.
Handicap :
Vision floue avec un faible contraste.

Exemple de temporaire ou situationnel

  • Luminosité du soleil.

Compétences (aptitude)

  • Solide compréhension de la technologie d’assistance utilisée pour la navigation sur le Web.
  • Utilisateur d’ordinateur hautement qualifié qui utilise des réglages de contraste pour voir clairement l’écran.

Outils (technologie d’adaptation, appareils, autres)

Catégorie : Amélioration de la vision

  • Réglages des couleurs.
  • Vérificateur automatisé de l’accessibilité du Web.
  • Microsoft Teams.
  • Lecteur d’écran.
  • Logiciel de traitement de texte.
  • Grossissement de l’écran.

Besoins (tâches, environnements)

  • Exige l’accès aux lignes directrices sur l’accessibilité du Web et des documents lors de la réalisation des tests.
  • Temps de mise à l’essai adéquat de l’accessibilité des technologies de l’information et des communications (TIC) au sein du GC.
  • Les fichiers numériques seront disponibles dans des formats accessibles.

Obstacles et frustrations (détails, attitudes)

  • Perte de contenu web ou de fonctionnalités lorsque la taille de la police ou l’écran du navigateur est redimensionné.
  • Le texte à faible contraste peut être difficile à lire.
  • Images sur des sites Web qui ne fournissent pas d’alternatives textuelles.
  • Les conférenciers qui ne fournissent pas d’informations qui aident à comprendre les informations affichées visuellement.

Citation :

« C’est vraiment ennuyeux quand les couleurs du texte et de l’arrière-plan sont si proches les unes des autres, cela rend tout ce qui se trouve à l’écran difficile à lire. »

Yenah - Dextérité

À propos

Pronoms
Elle / Elle.
Âge
29
Emploi
Développeur frontal.
Sites couramment utilisés
WCAG pour les développeurs.
Handicap :
Fibromyalgie.

Exemple de temporaire ou situationnel

  • Arthrite inflammatoire.
  • Trajet en voiture cahoteux.

Compétences (aptitude)

  • Utilise des macbook et des produits Apple tous les jours pour son travail.
  • Techsavvy et s’appuie sur ses outils dans sa vie quotidienne.

Outils (technologie d’adaptation, appareils, autres)

Catégorie: Amélioration de la mobilité et de la dextérité.

  • Clavier ergonomique, souris.
  • Dragon Naturellement Parlant.
  • X-Keys préprogrammés.
  • Logiciel de reconnaissance vocale.

Besoins (tâches, environnements)

  • Préfère les mesures d’adaptation et la flexibilité de l’horaire de travail pour tenir compte du repos, du soutien médical, des styles de travail préférés.
  • Compréhension de leur équipe pour les différents niveaux d’inconfort qui peuvent survenir chaque jour.
  • Gestes de pointeur simples lors de la navigation dans les pages Web (ex: simple clic / robinet).
  • Liens avec les noms propres pour indiquer clairement où le lien mène et quel est son but.

Obstacles et frustrations (détails, attitudes)

  • Distractions en milieu de travail.
  • Des politiques en milieu de travail qui rendent les mesures d’adaptation du travail à domicile difficiles à obtenir.
  • Lorsque d’autres modèles d’interaction ne sont pas disponibles et que l’action requise est difficile à accomplir (ex: secouer un appareil, pincer, dessiner, etc.).

Citation :

« Les boutons sur l’écran de mon téléphone peuvent être si petits, je veux appuyer sur une case à cocher mais accidentellement cliquer sur une autre option, je dois décocher le mauvais pour continuer, mais c’est frustrant. »

Ike - Mobility

À propos

Pronoms
Ils / Eux.
Âge
31
Emploi
Formateur / Éducateur.
Sites couramment utilisés
AAACT, GcPedia, DAT.
Handicap :
Maladie du neurone moteur.

Exemple de temporaire ou situationnel

  • Tenir un bébé.
  • Fracture d’un membre.

Compétences (aptitude)

  • A de l’expérience dans la prestation de formation sur l’accessibilité du Web et des documents

Outils (technologie d’adaptation, appareils, autres)

Catégorie : Amélioration de la mobilité.

  • Dispositif de reconnaissance vocale.
  • Fauteuil roulant électrique.
  • Moniteurs réglables.
  • Claviers adaptatifs.

Besoins (tâches, environnements)

  • Renseignements sur la façon d’acquérir des mesures d’adaptation en milieu de travail en raison des politiques de retour obligatoire au bureau.
  • Méthode normalisée pour fournir aux stagiaires des ressources sur les normes, les politiques et les exigences en matière d’accessibilité au sein du GC.
  • Possibilité de visualiser le contenu Web en orientation portrait et paysage.

Obstacles et frustrations (détails, attitudes)

  • Difficulté à réserver un espace de travail via l’application Web désignée.
  • Difficulté à trouver des itinéraires accessibles à l’extérieur et à l’intérieur des bâtiments.
  • Bâtiments sans bouton de porte automatique.
  • Obstacles sur les routes accessibles, y compris les rampes et les corridors.

Citation :

« Je ne peux pas réserver un espace de travail comme tout le monde le fait parce que l’application ne prend pas en charge la navigation au clavier. »

Damien - Cognitive

À propos

Pronoms
Il / Lui.
Âge
48
Emploi
Gestionnaire en communications.
Sites couramment utilisés
Deque.
Handicap :
Trouble du spectre de l’autisme, Dyslexie.

Exemple de temporaire ou situationnel

  • Subir une commotion cérébrale.

Compétences (aptitude)

  • S’appuie sur le calendrier, les horaires et les applications d’organisation sur ordinateur de bureau et mobile.
  • Préfère avoir la possibilité de personnaliser mon environnement (ex: outils et technologie, lumière ambiante et température, affichage du moniteur, etc.

Outils (technologie d’adaptation, appareils, autres)

Catégorie: Amélioration du style cognitif et d’apprentissage.

  • Paramètres de préférence de texte, utilisateur de clavier d’alimentation.
  • Logiciel de synthèse vocale.

Besoins (tâches, environnements)

  • Fonctionne mieux avec des routines et des processus cohérents et familiers.
  • Lors de la communication, les termes utilisés dans les conversations doivent être littéraux, clairs et précis.
  • J’espère que les gens comprennent que les diagnostics de neurodiversité sont uniques, les besoins de 1 personne peuvent être différents de ceux d’une autre personne ayant le même handicap.
  • Sites avec plusieurs voies de navigation pour rendre le site plus facile à utiliser.

Obstacles et frustrations (détails, attitudes)

  • Pas génial avec la socialisation, comme les petites conversations, le contact visuel, la cueillette d’indices subtils et le toucher physique.
  • Traite souvent des maux de tête et des migraines.

Citation :

“When I’m using a website, I find it frustrating when there is no consistency in page layouts and some terminologies to confirm my actions can be difficult to understand.”

Valeria – Cognitive and Auditory

À propos

Pronoms
Elle / Elle.
Âge
62
Emploi
Agent des services administratifs.
Sites couramment utilisés
Salesforce, IAAP, DAT.
Handicap :
TDAH, trouble anxieux, perte auditive sévère, entendre des sons mais ne peut pas distinguer la parole

Exemple de temporaire ou situationnel

  • Les utilisateurs qui ne sont pas familiers avec Internet.
  • Locuteurs non natifs.

Compétences (aptitude)

  • Fonctionne mieux avec des routines et des processus cohérents et familiers.
  • Qualifié dans les applications Microsoft Office.

Outils (technologie d’adaptation, appareils, autres)

Catégorie: Amélioration du style cognitif et d’apprentissage et autres.

  • Lecteur d’écran.
  • Loupe de zoom.
  • Gestionnaire de mots de passe.

Besoins (tâches, environnements)

  • Aime travailler avec des outils automatisés comme le remplissage automatique / complet qui peut aider à remplir rapidement les informations et aide les utilisateurs à se souvenir de toutes leurs différentes informations de compte.
  • Travaille souvent dans des espaces du bureau avec des politiques d’intimité et de faible volume pour aider à éliminer les distractions et faciliter un travail approfondi.
  • Utilisation d’un langage simple et simple, exempt d’acronymes, de métaphores, d’argots, d’instructions explicatives et d’images descriptives.

Obstacles et frustrations (détails, attitudes)

  • Ne pas être capable de lire sur les lèvres et de voir les expressions faciales lorsque les gens ont des caméras éteintes pendant un appel vidéo.
  • Utilisation de légendes inexactes ou non personnalisables.

Citation :

« Lorsque je remplis un formulaire en ligne, il est difficile de terminer la tâche dans les délais donnés. C’est encore plus frustrant quand je ne sais pas combien de temps j’ai, le site chronoppe et supprime mon travail, et je dois refaire le formulaire à nouveau. «

Yosef – Mobilité et parole

À propos

Pronoms
Il / Lui.
Âge
39
Emploi
Agent de soutien administratif et de programme.
Sites couramment utilisés
GCdocs, GCXchange, DAT.
Handicap :
Fatigue musculaire et troubles de l’élocution

Exemple de temporaire ou situationnel

  • Les blessures de stress répétitives et ne peuvent pas parler dans certaines situations en raison de l’anxiété.
  • Se remettre d’une commotion cérébrale.

Compétences (aptitude)

  • Expérience de l’examen d’informations et de l’extraction d’informations critiques.
  • Nécessite souvent une exposition répétée au contenu pour le comprendre.

Outils (technologie d’adaptation, appareils, autres)

Catégorie : Remplacement ou amélioration de la mobilité et de la parole.

  • Paramètres de préférence de texte, utilisateur de clavier d’alimentation.
  • Logiciel de synthèse vocale. Logiciel de synthèse vocale.
  • Correcteurs orthographiques.
  • Clavier et souris ergonomiques.
  • Modèles et outils organisationnels.

Besoins (tâches, environnements)

  • Sites Web et navigateurs qui fournissent une prise en charge complète du clavier et fournissent des options pour passer aux sections principales de la page.
  • D’autres moyens de communication qui ne reposent pas beaucoup sur la parole. Par exemple, chat textuel, e-mail et formulaire de commentaires.
  • Doit utiliser un clavier et une souris ergonomiques pour une utilisation quotidienne au bureau.

Obstacles et frustrations (détails, attitudes)

  • Contenu Web accessible à l’aide d’un clavier.
  • Limites de temps insuffisantes pour effectuer des tâches telles que remplir un formulaire Web.
  • Centres de support et d’aide qui offrent des numéros de téléphone comme seul moyen de communiquer avec leur organisation.

Citation :

« Il peut être très fatigant d’avoir à parcourir des documents non pertinents pour atteindre le contenu dont j’ai besoin. «

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/rendre-vos-courriel-accessibles/index.html b/fr/rendre-vos-courriel-accessibles/index.html index 6c8c25494..c5de5c851 100644 --- a/fr/rendre-vos-courriel-accessibles/index.html +++ b/fr/rendre-vos-courriel-accessibles/index.html @@ -1,4 +1,4 @@ -Rendre vos courriel accessibles - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Rendre vos courriel accessibles

Un courriel accessible est important pour les personnes handicapées, mais aussi pour tout le monde. Découvrez comment créer un e-mail accessible dans Outlook.

Sur cette page

Format du texte

Outlook offre trois options de format : HTML, texte brut et texte enrichi. Parmi ces trois options, le format HTML est celui qui rend le contenu le plus accessible.

Le format HTML comporte plusieurs avantages afin de rendre vos courriels plus inclusifs :

L’utilisation du format HTML est conforme aux règles d’accessibilité en vigueur, notamment les normes WCAG et EN 301 549.

Pour rédiger vos courriels en format HTML :

  1. sélectionnez Fichier (Alt + F);
  2. sélectionnez Options (V);
  3. sélectionnez Courrier (C);
  4. dans la liste déroulante Composition des messages (Alt + É), choisissez HTML;
  5. sélectionnez OK.

Message bilingue (le cas échéant)

Dans la mesure du possible, évitez d’envoyer des courriels bilingues parce qu’ils peuvent créer divers problèmes d’accessibilité et de convivialité pour de nombreux utilisateurs.

Si vous devez utiliser des courriels bilingues, veillez à ce qu’ils soient aussi accessibles que possible.

Définir une langue

Si le document entier est en anglais mais que certaines sections renferment des passages en français, le lecteur d’écran configuré pour le texte anglais essaiera de prononcer les termes français et le résultat ressemblera à du charabia.

Langage clair

Évitez les styles d’écriture trop complexes.

Resources

Styles

Un style est un ensemble d’attributs de mise en forme intégrés que vous pouvez appliquer au contenu de votre document, y compris les titres. Un style contient des attributs de mise en forme tels que la couleur et la taille des caractères, si le texte est en gras ou en italique, ainsi que l’espacement des paragraphes et des lignes. Lorsque vous appliquez un style à un texte,

vous appliquez en une seule étape facile tous les attributs de mise en forme contenus dans le style particulier, et vous obtenez une présentation uniforme dans tout le document.

Utilisation d’un style

Le volet Styles se trouve sur l’onglet Format du texte. Mettez en évidence le texte que vous voulez modifier, par exemple, un titre dans votre message.

Pour ouvrir le volet Styles, cliquez sur la flèche d’expansion (Alt, X, S). Sélectionnez Titre. Le style Titre sera mis en évidence dans la liste et sera appliqué au texte sélectionné.

Modifier un style

  1. Placez votre curseur à l’endroit du texte dont vous voulez modifier le style.
  2. Appuyez sur les touches Ctrl + Maj + S.
  3. Sélectionnez Modifier dans la boîte de dialogue Appliquer les styles.
  4. Dans le groupe Mise en forme, effectuez les modifications souhaitées (style de police, taille des caractères, alignement, interligne ou tabulations).
  5. Déterminez si le changement de style s’applique au document en cours ou aux nouveaux documents basés sur ce modèle. L’option Uniquement dans ce document s’applique par défaut.
  6. Sélectionnez OK.

Remarque : Lorsque vous modifiez un style, le changement s’appliquera à toutes les occurrences du texte ayant ce style, pas seulement au texte sélectionné.

Polices de caractères

Les polices de caractères utilisées le plus souvent sont Arial ou Calibri (polices sans empattement), et Times New Roman ou Cambria (polices avec empattement). Les polices avec empattement peuvent créer des problèmes d’accessibilité pour les personnes atteintes de difficultés cognitives ou visuelles.

Veillez à utiliser une police de caractères sans empattement comme Arial, Calibri, Verdana, etc.

Attributs de la police de caractères

Il faut toujours :

Évitez :

Utilisation de la couleur

N’utilisez pas la couleur comme seul moyen de transmettre de l’information. Si vous utilisez la couleur pour communiquer un message, utilisez toujours une ou plusieurs autres méthodes pour transmettre la même information (par exemple, des motifs, des étiquettes, des symboles, etc.).

Contraste de couleurs

Thèmes Outlook

Évitez de modifier le thème Outlook par défaut (Office). L’utilisation d’autres thèmes peut créer des problèmes d’accessibilité.

Structure sémantique

Titres

Paragraphes

Listes

Images accessibles

Images alignées sur le texte

Lorsque vous insérez des images (aussi appelées illustrations) dans Word, définissez l’image comme étant Alignée sur le texte puisqu’il s’agit de la seule option accessible pour que les technologies adaptées voient l’image. N’entourez pas une image de texte puisque cela empêche certains utilisateurs d’accéder aux images et au texte de remplacement.

Texte de remplacement

Le texte de remplacement sert à décrire les images et autres contenus non textuels. Les éléments visuels tels que les photos, les icônes, les diagrammes et les tableaux doivent être accompagnés d’un texte de remplacement qui décrit brièvement le contenu pertinent de l’image. Vous devez ajouter un texte de remplacement aux images ou graphiques significatifs pour qu’ils soient accessibles aux utilisateurs de technologies adaptées.

Lorsque vous rédigez un texte de remplacement, pensez à la manière dont vous utilisez les images. Ne tenez pas compte des détails qui n’ont pas de lien avec le document. Par exemple, une image illustrant un groupe d’étudiants apparaît dans un document portant sur l’embauche d’étudiants pour l’été.

Ajouter un texte de remplacement

  1. Sélectionnez une image ou un graphique.
  2. Faites un clic‑droit sur l’image et sélectionnez Afficher le texte de remplacement (Maj + F10, T).
  3. Ajoutez une description.

Ajouter une légende

  1. Sélectionnez une image.
  2. Faites un clic‑droit sur l’image et sélectionnez Insérer une légende (Maj + F10, D).
  3. Ajoutez une légende.

Descriptions longues

Les descriptions longues fournissent les informations essentielles contenues dans une image complexe sous forme de texte. Tout lecteur, quelles que soient ses capacités, peut avoir de la difficulté à comprendre des images complexes sans une explication écrite plus longue.

Utilisation de tableaux

Ajouter un tableau

  1. Insérez un tableau en utilisant les options de l’onglet Insertion (Alt, S, ÇT, I).
  2. Choisissez le nombre de rangées et de colonnes.
  3. Sélectionnez OK.
  4. Les cases à cocher Ligne d’en-tête et Première colonne de l’onglet Création de tableau sont activées par défaut. Évitez de décocher ces cases, car il s’agit des options d’accessibilité par défaut.

Hyperliens pertinents

Microsoft Office affiche automatiquement les hyperliens sous forme de texte bleu souligné. Cela aide les lecteurs à repérer les hyperliens dans un document.

Remarque : Utilisez uniquement le soulignement pour les hyperliens dans votre contenu numérique.

Signets

Un peu comme une table des matières, les signets vous permettent de créer des liens vers certaines parties d’un courriel, ce qui permet à l’utilisateur d’accéder directement à une partie particulière du message.

La création d’un signet vous permet de choisir un sujet dans votre courriel vers lequel vous pouvez ensuite insérer un lien.

Pour créer un signet :

  1. Sélectionnez le texte auquel l’hyperlien du signet doit mener.
  2. Sous l’onglet Insertion, dans le groupe Liens, sélectionnez Signets (Alt, S, ÇI).
  3. Dans le champ Nom du signet, entrez un nom pertinent (par exemple, « Section en français »). Remarque : les espaces et les caractères spéciaux ne peuvent pas être utilisés dans les noms de signet.
  4. Sélectionnez Ajouter (Alt + A).

Pour créer un lien vers votre signet :

  1. Sous l’onglet Insertion, dans le groupe Liens, sélectionnez Lien, puis Insérer un lien (Alt, S, I2, I).
  2. Dans la boîte de dialogue Insérer un lien hypertexte, sélectionnez Emplacement dans ce document (Alt + A).
  3. Ajoutez un texte pertinent dans le champ de saisie Texte à afficher (Alt + T) [par exemple, « Section en français »].
  4. Dans le groupe Signets, sous Sélectionner un emplacement dans ce document (Alt + C), sélectionnez le nom du signet que vous avez créé.
  5. Sélectionnez OK.

Signatures de courriel accessibles

Créez une signature de courriel qui apparaîtra au bas de tous vos courriels sortants avec la fonction de signature intégrée à Outlook, dans les paramètres du courrier.

Remarque : Vérifiez les exigences de votre ministère concernant le formatage et le contenu des signatures.

  1. Allez à Fichier (Alt, F).
  2. Sélectionnez Options (V).
  3. Dans la boîte de dialogue Options Outlook, sélectionnez Courrier (C).
  4. Dans la section Composition des messages, sélectionnez Signatures (Alt + G).
  5. Sélectionnez Nouveau (Alt + N).
  6. Donnez un nom à la signature (par exemple, courante, informelle ou officielle, etc.).
  7. Placez le curseur dans le champ de signature (Alt + I et Tab jusqu’au champ) et entrez des éléments comme une salutation (Merci) et vos nom, titre, pronom, etc.
  8. Utilisez les options de mise en forme disponibles pour modifier l’apparence. a. Utilisez une taille de caractères appropriée (12 points ou plus).
  9. Sélectionnez OK.
  10. Sélectionnez OK de nouveau.

Remarque : N’utilisez pas d’images de texte dans votre bloc de signature (sauf s’il s’agit d’un logo).

Vérification de l’accessibilité

Le vérificateur d’accessibilité ne remplace pas la connaissance des principes de création d’un document accessible. Il s'agit d’un outil automatisé qui décèle seulement certains problèmes d’accessibilité.

Vérificateur d’accessibilité d’Outlook

  1. Sous l’onglet Révision (Alt, R).
  2. Sélectionnez Vérifier l’accessibilité (A).

Lecteur d’écran Narrateur de Windows

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Rendre vos courriel accessibles

Un courriel accessible est important pour les personnes handicapées, mais aussi pour tout le monde. Découvrez comment créer un e-mail accessible dans Outlook.

Sur cette page

Format du texte

Outlook offre trois options de format : HTML, texte brut et texte enrichi. Parmi ces trois options, le format HTML est celui qui rend le contenu le plus accessible.

Le format HTML comporte plusieurs avantages afin de rendre vos courriels plus inclusifs :

L’utilisation du format HTML est conforme aux règles d’accessibilité en vigueur, notamment les normes WCAG et EN 301 549.

Pour rédiger vos courriels en format HTML :

  1. sélectionnez Fichier (Alt + F);
  2. sélectionnez Options (V);
  3. sélectionnez Courrier (C);
  4. dans la liste déroulante Composition des messages (Alt + É), choisissez HTML;
  5. sélectionnez OK.

Message bilingue (le cas échéant)

Dans la mesure du possible, évitez d’envoyer des courriels bilingues parce qu’ils peuvent créer divers problèmes d’accessibilité et de convivialité pour de nombreux utilisateurs.

Si vous devez utiliser des courriels bilingues, veillez à ce qu’ils soient aussi accessibles que possible.

Définir une langue

Si le document entier est en anglais mais que certaines sections renferment des passages en français, le lecteur d’écran configuré pour le texte anglais essaiera de prononcer les termes français et le résultat ressemblera à du charabia.

Langage clair

Évitez les styles d’écriture trop complexes.

Resources

Styles

Un style est un ensemble d’attributs de mise en forme intégrés que vous pouvez appliquer au contenu de votre document, y compris les titres. Un style contient des attributs de mise en forme tels que la couleur et la taille des caractères, si le texte est en gras ou en italique, ainsi que l’espacement des paragraphes et des lignes. Lorsque vous appliquez un style à un texte,

vous appliquez en une seule étape facile tous les attributs de mise en forme contenus dans le style particulier, et vous obtenez une présentation uniforme dans tout le document.

Utilisation d’un style

Le volet Styles se trouve sur l’onglet Format du texte. Mettez en évidence le texte que vous voulez modifier, par exemple, un titre dans votre message.

Pour ouvrir le volet Styles, cliquez sur la flèche d’expansion (Alt, X, S). Sélectionnez Titre. Le style Titre sera mis en évidence dans la liste et sera appliqué au texte sélectionné.

Modifier un style

  1. Placez votre curseur à l’endroit du texte dont vous voulez modifier le style.
  2. Appuyez sur les touches Ctrl + Maj + S.
  3. Sélectionnez Modifier dans la boîte de dialogue Appliquer les styles.
  4. Dans le groupe Mise en forme, effectuez les modifications souhaitées (style de police, taille des caractères, alignement, interligne ou tabulations).
  5. Déterminez si le changement de style s’applique au document en cours ou aux nouveaux documents basés sur ce modèle. L’option Uniquement dans ce document s’applique par défaut.
  6. Sélectionnez OK.

Remarque : Lorsque vous modifiez un style, le changement s’appliquera à toutes les occurrences du texte ayant ce style, pas seulement au texte sélectionné.

Polices de caractères

Les polices de caractères utilisées le plus souvent sont Arial ou Calibri (polices sans empattement), et Times New Roman ou Cambria (polices avec empattement). Les polices avec empattement peuvent créer des problèmes d’accessibilité pour les personnes atteintes de difficultés cognitives ou visuelles.

Veillez à utiliser une police de caractères sans empattement comme Arial, Calibri, Verdana, etc.

Attributs de la police de caractères

Il faut toujours :

Évitez :

Utilisation de la couleur

N’utilisez pas la couleur comme seul moyen de transmettre de l’information. Si vous utilisez la couleur pour communiquer un message, utilisez toujours une ou plusieurs autres méthodes pour transmettre la même information (par exemple, des motifs, des étiquettes, des symboles, etc.).

Contraste de couleurs

Thèmes Outlook

Évitez de modifier le thème Outlook par défaut (Office). L’utilisation d’autres thèmes peut créer des problèmes d’accessibilité.

Structure sémantique

Titres

Paragraphes

Listes

Images accessibles

Images alignées sur le texte

Lorsque vous insérez des images (aussi appelées illustrations) dans Word, définissez l’image comme étant Alignée sur le texte puisqu’il s’agit de la seule option accessible pour que les technologies adaptées voient l’image. N’entourez pas une image de texte puisque cela empêche certains utilisateurs d’accéder aux images et au texte de remplacement.

Texte de remplacement

Le texte de remplacement sert à décrire les images et autres contenus non textuels. Les éléments visuels tels que les photos, les icônes, les diagrammes et les tableaux doivent être accompagnés d’un texte de remplacement qui décrit brièvement le contenu pertinent de l’image. Vous devez ajouter un texte de remplacement aux images ou graphiques significatifs pour qu’ils soient accessibles aux utilisateurs de technologies adaptées.

Lorsque vous rédigez un texte de remplacement, pensez à la manière dont vous utilisez les images. Ne tenez pas compte des détails qui n’ont pas de lien avec le document. Par exemple, une image illustrant un groupe d’étudiants apparaît dans un document portant sur l’embauche d’étudiants pour l’été.

Ajouter un texte de remplacement

  1. Sélectionnez une image ou un graphique.
  2. Faites un clic‑droit sur l’image et sélectionnez Afficher le texte de remplacement (Maj + F10, T).
  3. Ajoutez une description.

Ajouter une légende

  1. Sélectionnez une image.
  2. Faites un clic‑droit sur l’image et sélectionnez Insérer une légende (Maj + F10, D).
  3. Ajoutez une légende.

Descriptions longues

Les descriptions longues fournissent les informations essentielles contenues dans une image complexe sous forme de texte. Tout lecteur, quelles que soient ses capacités, peut avoir de la difficulté à comprendre des images complexes sans une explication écrite plus longue.

Utilisation de tableaux

Ajouter un tableau

  1. Insérez un tableau en utilisant les options de l’onglet Insertion (Alt, S, ÇT, I).
  2. Choisissez le nombre de rangées et de colonnes.
  3. Sélectionnez OK.
  4. Les cases à cocher Ligne d’en-tête et Première colonne de l’onglet Création de tableau sont activées par défaut. Évitez de décocher ces cases, car il s’agit des options d’accessibilité par défaut.

Hyperliens pertinents

Microsoft Office affiche automatiquement les hyperliens sous forme de texte bleu souligné. Cela aide les lecteurs à repérer les hyperliens dans un document.

Remarque : Utilisez uniquement le soulignement pour les hyperliens dans votre contenu numérique.

Signets

Un peu comme une table des matières, les signets vous permettent de créer des liens vers certaines parties d’un courriel, ce qui permet à l’utilisateur d’accéder directement à une partie particulière du message.

La création d’un signet vous permet de choisir un sujet dans votre courriel vers lequel vous pouvez ensuite insérer un lien.

Pour créer un signet :

  1. Sélectionnez le texte auquel l’hyperlien du signet doit mener.
  2. Sous l’onglet Insertion, dans le groupe Liens, sélectionnez Signets (Alt, S, ÇI).
  3. Dans le champ Nom du signet, entrez un nom pertinent (par exemple, « Section en français »). Remarque : les espaces et les caractères spéciaux ne peuvent pas être utilisés dans les noms de signet.
  4. Sélectionnez Ajouter (Alt + A).

Pour créer un lien vers votre signet :

  1. Sous l’onglet Insertion, dans le groupe Liens, sélectionnez Lien, puis Insérer un lien (Alt, S, I2, I).
  2. Dans la boîte de dialogue Insérer un lien hypertexte, sélectionnez Emplacement dans ce document (Alt + A).
  3. Ajoutez un texte pertinent dans le champ de saisie Texte à afficher (Alt + T) [par exemple, « Section en français »].
  4. Dans le groupe Signets, sous Sélectionner un emplacement dans ce document (Alt + C), sélectionnez le nom du signet que vous avez créé.
  5. Sélectionnez OK.

Signatures de courriel accessibles

Créez une signature de courriel qui apparaîtra au bas de tous vos courriels sortants avec la fonction de signature intégrée à Outlook, dans les paramètres du courrier.

Remarque : Vérifiez les exigences de votre ministère concernant le formatage et le contenu des signatures.

  1. Allez à Fichier (Alt, F).
  2. Sélectionnez Options (V).
  3. Dans la boîte de dialogue Options Outlook, sélectionnez Courrier (C).
  4. Dans la section Composition des messages, sélectionnez Signatures (Alt + G).
  5. Sélectionnez Nouveau (Alt + N).
  6. Donnez un nom à la signature (par exemple, courante, informelle ou officielle, etc.).
  7. Placez le curseur dans le champ de signature (Alt + I et Tab jusqu’au champ) et entrez des éléments comme une salutation (Merci) et vos nom, titre, pronom, etc.
  8. Utilisez les options de mise en forme disponibles pour modifier l’apparence. a. Utilisez une taille de caractères appropriée (12 points ou plus).
  9. Sélectionnez OK.
  10. Sélectionnez OK de nouveau.

Remarque : N’utilisez pas d’images de texte dans votre bloc de signature (sauf s’il s’agit d’un logo).

Vérification de l’accessibilité

Le vérificateur d’accessibilité ne remplace pas la connaissance des principes de création d’un document accessible. Il s'agit d’un outil automatisé qui décèle seulement certains problèmes d’accessibilité.

Vérificateur d’accessibilité d’Outlook

  1. Sous l’onglet Révision (Alt, R).
  2. Sélectionnez Vérifier l’accessibilité (A).

Lecteur d’écran Narrateur de Windows

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/repertoire-de-la-communaute/index.html b/fr/repertoire-de-la-communaute/index.html index 006dc903d..bfe7c36f2 100644 --- a/fr/repertoire-de-la-communaute/index.html +++ b/fr/repertoire-de-la-communaute/index.html @@ -9,4 +9,4 @@ w.gtag('js', new Date()); w.gtag('config', 'G-SM9MSHWDVN'); } - })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Répertoire de la communauté

En savoir plus sur les organisations, les projets et les personnes qui travaillent sur l'accessibilité au sein du gouvernement du Canada.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

lien interneCommunauté de pratique sur les communications accessibles

La Communauté de pratique sur les communications accessibles regroupe des collègues de tous les domaines et de tous les secteurs de la communication au sein du gouvernement du Canada. Son mandat est de relier la communauté du GC afin d'échanger des idées et de soutenir les politiques, les lignes directrices et les meilleures pratiques liées aux communications accessibles internes et externes.

Ses objectifs comprennent :

  • Aider à clarifier les orientations de Canada.ca et à développer les meilleures pratiques en matière d'utilisation de communications internes et externes accessibles.
  • Donner aux employés la possibilité d’utiliser des communications accessibles dans l'ensemble du GC
  • Identifier les lacunes dans les pratiques, les politiques et les normes du GC en matière de communications accessibles et formuler des recommandations stratégiques aux organismes centraux à cet égard.

Emploi et Développement social Canada (EDSC)

Emploi et Développement social Canada (EDSC) travaille à améliorer le niveau de vie et la qualité de vie de tous les Canadiens en faisant la promotion d'une main-d'œuvre mobile et hautement spécialisée ainsi que d'un marché du travail efficace et favorable à l'inclusion. EDSC compte plusieurs équipes travaillant dans le domaine de l'accessibilité numérique dans le but de créer un environnement sans obstacle pour les Canadiens et les employés !

Normes d’accessibilité Canada

Le rôle de Normes d'accessibilité Canada est de :

  • créer des normes d'accessibilité pour les organisations sous juridiction fédérale,
  • faire progresser la recherche sur l'accessibilité, et
  • partager les meilleures pratiques en matière d'accessibilité.

En tant qu'organisme d'élaboration de normes accrédité, ses normes sont reconnues comme normes nationales du Canada. Son travail ouvre des portes pour que le Canada soit un leader mondial en matière d'accessibilité.

Statistique Canada (StatCan)

Statistique Canada, en collaboration avec des partenaires d'Emploi et Développement social Canada, continuera d'élaborer et de diffuser des produits permettant de mieux comprendre les expériences des Canadiens en matière d'accessibilité. Le carrefour de données sur l'accessibilité offre un emplacement centralisé de sujets liés à l'accessibilité et à l'incapacité par le biais de tableaux de données, d'articles, d'infographies et d'outils interactifs de visualisation de données.

École de la fonction publique du Canada (EFPC)

L'École de la fonction publique du Canada dirige l'approche pangouvernementale en matière d'apprentissage en offrant un programme de cours commun normalisé qui appuie les fonctionnaires aux points tournants de leur carrière, afin d'assurer qu'ils sont outillés pour servir les Canadiens en respectant les plus hauts critères d'excellence. Plusieurs équipes de l’École soutiennent l'accessibilité numérique dans le but de créer un environnement d'apprentissage sans obstacles pour ses apprenants.

Autres ministères participants

  • Agence du revenu du Canada (ARC)
  • Agriculture et Agroalimentaire Canada (AAC)
  • Anciens Combattants Canada (ACC)
  • Commission de la fonction publique du Canada (CFP)
  • Ministère des Finances Canada (FIN)
  • Santé Canada (SC)
  • Secrétariat du Conseil du Trésor du Canada
  • Sécurité publique Canada (SP)
  • Services partagés Canada (SPC)
  • Services publics et Approvisionnement Canada (SPAC)

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Répertoire de la communauté

En savoir plus sur les organisations, les projets et les personnes qui travaillent sur l'accessibilité au sein du gouvernement du Canada.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

lien interneCommunauté de pratique sur les communications accessibles

La Communauté de pratique sur les communications accessibles regroupe des collègues de tous les domaines et de tous les secteurs de la communication au sein du gouvernement du Canada. Son mandat est de relier la communauté du GC afin d'échanger des idées et de soutenir les politiques, les lignes directrices et les meilleures pratiques liées aux communications accessibles internes et externes.

Ses objectifs comprennent :

  • Aider à clarifier les orientations de Canada.ca et à développer les meilleures pratiques en matière d'utilisation de communications internes et externes accessibles.
  • Donner aux employés la possibilité d’utiliser des communications accessibles dans l'ensemble du GC
  • Identifier les lacunes dans les pratiques, les politiques et les normes du GC en matière de communications accessibles et formuler des recommandations stratégiques aux organismes centraux à cet égard.

Emploi et Développement social Canada (EDSC)

Emploi et Développement social Canada (EDSC) travaille à améliorer le niveau de vie et la qualité de vie de tous les Canadiens en faisant la promotion d'une main-d'œuvre mobile et hautement spécialisée ainsi que d'un marché du travail efficace et favorable à l'inclusion. EDSC compte plusieurs équipes travaillant dans le domaine de l'accessibilité numérique dans le but de créer un environnement sans obstacle pour les Canadiens et les employés !

Normes d’accessibilité Canada

Le rôle de Normes d'accessibilité Canada est de :

  • créer des normes d'accessibilité pour les organisations sous juridiction fédérale,
  • faire progresser la recherche sur l'accessibilité, et
  • partager les meilleures pratiques en matière d'accessibilité.

En tant qu'organisme d'élaboration de normes accrédité, ses normes sont reconnues comme normes nationales du Canada. Son travail ouvre des portes pour que le Canada soit un leader mondial en matière d'accessibilité.

Statistique Canada (StatCan)

Statistique Canada, en collaboration avec des partenaires d'Emploi et Développement social Canada, continuera d'élaborer et de diffuser des produits permettant de mieux comprendre les expériences des Canadiens en matière d'accessibilité. Le carrefour de données sur l'accessibilité offre un emplacement centralisé de sujets liés à l'accessibilité et à l'incapacité par le biais de tableaux de données, d'articles, d'infographies et d'outils interactifs de visualisation de données.

École de la fonction publique du Canada (EFPC)

L'École de la fonction publique du Canada dirige l'approche pangouvernementale en matière d'apprentissage en offrant un programme de cours commun normalisé qui appuie les fonctionnaires aux points tournants de leur carrière, afin d'assurer qu'ils sont outillés pour servir les Canadiens en respectant les plus hauts critères d'excellence. Plusieurs équipes de l’École soutiennent l'accessibilité numérique dans le but de créer un environnement d'apprentissage sans obstacles pour ses apprenants.

Autres ministères participants

  • Agence du revenu du Canada (ARC)
  • Agriculture et Agroalimentaire Canada (AAC)
  • Anciens Combattants Canada (ACC)
  • Commission de la fonction publique du Canada (CFP)
  • Ministère des Finances Canada (FIN)
  • Santé Canada (SC)
  • Secrétariat du Conseil du Trésor du Canada
  • Sécurité publique Canada (SP)
  • Services partagés Canada (SPC)
  • Services publics et Approvisionnement Canada (SPAC)

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/ressources-additionnelles-sur-les-reunions-et-evenements-accessibles/index.html b/fr/ressources-additionnelles-sur-les-reunions-et-evenements-accessibles/index.html index 110583225..d864e80f8 100644 --- a/fr/ressources-additionnelles-sur-les-reunions-et-evenements-accessibles/index.html +++ b/fr/ressources-additionnelles-sur-les-reunions-et-evenements-accessibles/index.html @@ -1,4 +1,4 @@ -Ressources additionnelles sur les réunions et événements accessibles - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Ressources additionnelles sur les réunions et événements accessibles

Pour plus d'informations sur les réunions et événements accessibles, vous pouvez consulter cette liste de liens.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Ressources additionnelles sur les réunions et événements accessibles

Pour plus d'informations sur les réunions et événements accessibles, vous pouvez consulter cette liste de liens.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/ressources-additionnelles/index.html b/fr/ressources-additionnelles/index.html index caf4b0934..3acdae355 100644 --- a/fr/ressources-additionnelles/index.html +++ b/fr/ressources-additionnelles/index.html @@ -1,4 +1,4 @@ -Ressources additionnelles - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Ressources additionnelles

Ressources et outils utiles en matière d'accessibilité du web pour les employés du gouvernement du Canada.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

Sur cette page

Apprentissage

Accessibilité de M365 (en anglais seulement)

Liste des ressources et du matériel d’apprentissage sur l’accessibilité de Microsoft 365 (M365).

Considérations relatives aux lecteurs d’écran lors du choix entre Google à IU My Drive et Microsoft OneDrive à IU (en anglais seulement)

Le choix entre Google à IU My Drive et Microsoft OneDrive à IU n’est pas simple lorsqu’on considère l’accessibilité relative aux lecteurs d’écran. Les deux présentent des avantages et des inconvénients, qui peuvent varier en fonction de la combinaison du lecteur d’écran et du navigateur utilisé.

Cours d'accessibilité

Cours, webinaires, vidéos éducatives, et plus encore, proposés en accessibilité web.

Documents accessibles de ESDC

Les étapes de base nécessaires à l’accessibilité sont les mêmes, que votre document soit en format HTML, Word de Microsoft, PDF d’Adobe ou autre. Nous avons assemblé des ressources pour vous aider et assurez que tous, incluant les personnes avec un handicapes, puisse lire et comprendre vos documents.

Guide d'accessibilité du contenu Web (en anglais seulement)

La base fondamentale qui vous permettra de disposer de produits numériques réellement inclusifs et accessibles.

International Association of Accessibility Professionals (en anglais seulement)

Les professionnels de l’accessibilité du monde entier se réunissent pour définir, promouvoir et améliorer la profession de l’accessibilité par le biais du réseautage, de l’éducation et de la certification.

Le pouvoir des mots et des images

Suggestions pour la représentation des personnes en situation de handicap. Les personnes en situation de handicap demandent aux Canadiens, et aux médias en particulier, d'utiliser des termes respectueux lorsqu'ils écrivent et parlent d'elles ou des questions qui les concernent. Elles demandent également que les images choisies pour les représenter soient respectueuses et ne renforcent pas des stéréotypes dépassés.

Microsoft Windows 11 L’accessibilité pour tous

Ressources utiles sur les fonctions d'accessibilité de Microsoft Windows 11.

Quels outils de vidéoconférence sont les plus accessibles ? (en anglais seulement)

Dans cet article, Claudio Luis Vera explique ce qu’il faut garder à l’esprit lors du choix d’un outil de vidéoconférence pour que tous les membres de votre équipe puissent en profiter — notamment ceux avec des handicaps.

YouTube : Apple : Accessibilité (en anglais seulement)

De l’utilisation de votre iPhone sans voir l’écran, à l’adaptation des gestes à vos besoins physiques, découvrez comment les fonctionnalités d’accessibilité intégrées à vos appareils Apple peuvent vous aider à en faire plus.

Développement

Boîte à outils de l’expérience Web (BOEW)

Un cadre frontal primé pour la création de sites Web accessibles, utilisables, interopérables, adaptés aux téléphones portables et multilingues.

Liste de vérification pour l’accessibilité Web

Liste de verification develop par ESDC.

Méthodologie d’évaluation sur l’accessibilité des sites Web (niveau AA) (en anglais seulement)

Aider à mesurer les critères de succès de niveau A et AA des Règles pour l’accessibilité des contenus Web (WCAG) 2.1.

Solution de gabarits à déploiement centralisé (SGDC)

L’objectif de la SGDC consiste essentiellement à fournir la couche de présentation du thème de Canada.ca ou du thème d’Intranet.canada.ca aux actifs Web.

Soutien à l'accessibilité (en anglais seulement)

Vérifiez si votre code fonctionnera avec les technologies d'assistance.

Système de conception de Canada.ca

Utilisez ce système de conception pour offrir une expérience en ligne plus conviviale, cohérente et fiable aux personnes qui accèdent aux services numériques du gouvernement du Canada. Le contenu du système de conception comprend :

Amélioration continue du contenu Web

Choisir quoi améliorer, organiser et préparer votre équipe, recherche et prototypage, concevoir le contenu, suivi et mesure du succès.

Bibliothèque de modèles et configurations de conception

Modèles, mises en page, configurations de conception, directives et exemples de code, testés par les utilisateurs.

Blogue Canada.ca

Données probantes et observations sur l’amélioration des renseignements et des services sur Canada.ca.

Derniers changements apportés au système de conception de Canada.ca

Derniers changements apportés au système de conception, aux modèles et conceptions de configuration, au guide de rédaction et aux autres outils.

Guide de rédaction du contenu du site Canada.ca

Techniques d’écriture et principes qui aident à rendre le contenu clair et adapté aux besoins de tous.

Spécifications du contenu et de l'architecture de l'information pour Canada.ca

Qui doit utiliser le système de conception de Canada.ca, éléments obligatoires, comment organiser et concevoir du contenu.

Politique

Authoring Tool Accessibility Guidelines (ATAG) Overview (en anglais seulement) - Initiative pour l'accessibilité du Web (WAI)

Les outils de création sont des logiciels et des services que les "auteurs" (développeurs web, concepteurs, rédacteurs, etc.) utilisent pour produire du contenu web (pages web statiques, applications web dynamiques, etc.)

Directive visant à rendre les technologies de l’information utilisables par tous

Cette ligne directrice soutient la direction du gouvernement du Canada pour s’assurer que les ministères, les agences et les organisations prennent en compte l’accessibilité lors de l’acquisition ou du développement d’équipement et de solutions de la technologie de l’information (TI) pour rendre la TI utilisable par tous.

EU EN 301 549 (Gestion de l’accessibilité dans les marchés publics des TIC) (en anglais seulement)

Les exigences en matière d’accessibilité qui conviennent à l’approvisionnement, par les organismes publics, de produits et services de technologies de l’information et des communications (TIC) en Europe.

Règles pour l’accessibilité des contenus Web 2.1

Les Règles pour l’accessibilité des contenus Web (WCAG) 2.1 couvrent un large éventail de recommandations pour rendre les contenus Web plus accessibles. Suivre ces règles rendra aussi les contenus Web souvent plus faciles d’utilisation aux utilisateurs en général.

Directive sur les services et le numérique

Décrit la façon dont les organisations du gouvernement du Canada gèrent la prestation de services, l’information et les données, la technologie de l’information et la cybersécurité à l’ère du numérique.

Directive sur l’obligation de prendre des mesures d’adaptation

La directive donne des orientations aux gestionnaires et aux chefs des ressources humaines quant à leurs obligations de prendre des mesures d’adaptation afin d’instaurer un milieu de travail inclusif et sans obstacles qui offre à tous des chances égales au sein de l’administration publique centrale.

Directive sur la gestion des communications

Prévoit les règles pour la gestion et la coordination des communications, y compris les procédures relatives à la publicité, les recherches sur l’opinion publique, les médias sociaux et les communications Web.

Stratégie sur l’accessibilité au sein de la fonction publique du Canada

Améliorer l’accessibilité, les mesures d’adaptation, l’ergonomie, les données et les stages. Stratégie d’accessibilité pour la fonction publique

Loi canadienne sur l’accessibilité - Site Web de la législation

Source en ligne des lois et règlements consolidés du Canada.

Glossaire de l'accessibilité

Ce glossaire contient 342 concepts et terminologies liés au projet de loi C-81 dans les domaines de la sociologie du travail et des aides techniques aux personnes handicapées.

La Loi sur l'accessibilité du Canada en langage clair et simple (en anglais seulement)

Ce document aide les gens à comprendre les principaux points du projet de loi C-81 ; une loi visant à assurer un Canada sans obstacles.

Approvisionnement

Accessibilité à Services publics et Approvisionnement Canada

En tant que fournisseur de services communs du gouvernement du Canada, le SPAC s'efforce d'offrir un excellent service aux autres ministères fédéraux. En cherchant à améliorer l'accès à ses programmes et services pour les personnes handicapées, SPAC aide les ministères fédéraux à offrir des programmes et services de haute qualité à tous les Canadiens.

Réunions et événements virtuels accessibles

Les réunions et événements virtuels sont caractérisés par différents formats et différentes tailles, allant de petits ateliers comprenant des participants qui se connaissent à de grandes réunions publiques à planifier. Il est essentiel de veiller à ce que ces réunions et événements soient pleinement accessibles, depuis leur accès jusqu’aux présentations. En planifiant, vous pouvez intégrer l’accessibilité à tous les aspects d’une réunion. Cela permet à tout le monde de pleinement participer, y compris les personnes en situation de handicap.

Afin de vous aider à offrir une réunion ou une activité virtuelle pleinement accessible, qu’il s’agisse d’une séance de formation, d’une réunion, d’un kiosque ou d’une journée portes ouvertes, le Bureau de l’accessibilité des TI (BATI) a rassemblé les renseignements les plus pertinents à ce sujet.

GcWiki Microsoft 365 Teams

Une collection de produits de formation MS Teams pour aider les fonctionnaires.

Directives relatives aux réunions/événements accessibles

Une planification adéquate de réunions et d’événements est essentielle pour assurer l’inclusion de tout le monde. Plusieurs éléments doivent être pris en compte avant et pendant les réunions et activités.

Meilleures pratiques pour vos demandes d’interprétation des conférences et d’interprétation en langues des signes et translittération orale

Meilleures pratiques pour vos demandes de conférence et d'interprétation en langue des signes.

Outil de travail planification d’événements virtuels accessibles de l’École de la fonction publique du Canada

Cet outil de travail présente des pratiques exemplaires pour planifier des événements virtuels accessibles et inclusifs.

Planifier des événements inclusifs et accessibles – Guide à l’intention des fonctionnaires fédéraux Lien interne du Bureau de la condition des personnes handicapée/Emploi et Développement social Canada (EDSC) (Plutôt pour les rencontres en personne)

Le Bureau de la condition des personnes handicapées (BCPH) est fier de présenter ce guide à des collègues du gouvernement du Canada afin de fournir une orientation sur la planification d’événements inclusifs et accessibles.

Plateformes de réunions virtuelles et fonctionnalités d’accessibilité

Les plateformes de réunion virtuelle Microsoft Teams et Zoom proposent une variété de fonctionnalités d’accessibilité répondant à différents besoins en matière de participation à des réunions et discussions en ligne.

Recommandations en matière de langues officielles

Pratiques exemplaires à suivre pour les réunions et événements unilingues ou bilingues pour les deux langues officielles.

Recommandations pour la configuration et l’exécution d’une réunion teams ou d’un événement en direct pour les personnes sourdes ou malentendantes

Lors de la configuration et de l’exécution de Microsoft Teams réunions et d’événements en direct, il est important de connaître les bonnes pratiques pour s’assurer que votre contenu est accessible aux sourds et malentendants. Les fonctionnalités telles que les sous-titres en direct et le choix d’un arrière-plan clair sont importantes pour s’assurer que tout le monde peut participer de manière égale.

Répertoire de l’Association des traducteurs et interprètes de l’Ontario (ATIO)

Trouvez un traducteur, un interprète ou un terminologue pour des réunions et des événements.

Services CART et interprètes en langue des signes

La mesure d’adaptation la plus courante pour les réunions ou les événements est la traduction en temps réel des communications (CART) et les services d’interprétation.

Tirez parti des fonctionnalités d’accessibilité de Microsoft Teams pour une expérience de réunion ou d’événement en direct plus agréable

Types de réunions proposées et fonctionnalités d’accessibilité

Nos recommandations pour choisir des plateformes de réunion virtuelle en fonction du type de réunion ou d’activité, du nombre de personnes et du contenu partagé.

Vue d’ensemble de l’accessibilité dans Microsoft Teams

Cette page contient une vue d'ensemble des nombreuses fonctions d'accessibilité qui permettent à tous les utilisateurs de bénéficier de la meilleure expérience possible, y compris les fonctions d'accessibilité pour une meilleure expérience des réunions ou des événements en direct, et les meilleures pratiques pour la mise en place et le déroulement d'une réunion Teams ou d'un événement en direct pour les sourds et les malentendants.

Services

Détails de la page

Date de modification :
\ No newline at end of file + })(window);

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Ressources additionnelles

Ressources et outils utiles en matière d'accessibilité du web pour les employés du gouvernement du Canada.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

Sur cette page

Apprentissage

Accessibilité de M365 (en anglais seulement)

Liste des ressources et du matériel d’apprentissage sur l’accessibilité de Microsoft 365 (M365).

Considérations relatives aux lecteurs d’écran lors du choix entre Google à IU My Drive et Microsoft OneDrive à IU (en anglais seulement)

Le choix entre Google à IU My Drive et Microsoft OneDrive à IU n’est pas simple lorsqu’on considère l’accessibilité relative aux lecteurs d’écran. Les deux présentent des avantages et des inconvénients, qui peuvent varier en fonction de la combinaison du lecteur d’écran et du navigateur utilisé.

Cours d'accessibilité

Cours, webinaires, vidéos éducatives, et plus encore, proposés en accessibilité web.

Documents accessibles de ESDC

Les étapes de base nécessaires à l’accessibilité sont les mêmes, que votre document soit en format HTML, Word de Microsoft, PDF d’Adobe ou autre. Nous avons assemblé des ressources pour vous aider et assurez que tous, incluant les personnes avec un handicapes, puisse lire et comprendre vos documents.

Guide d'accessibilité du contenu Web (en anglais seulement)

La base fondamentale qui vous permettra de disposer de produits numériques réellement inclusifs et accessibles.

International Association of Accessibility Professionals (en anglais seulement)

Les professionnels de l’accessibilité du monde entier se réunissent pour définir, promouvoir et améliorer la profession de l’accessibilité par le biais du réseautage, de l’éducation et de la certification.

Le pouvoir des mots et des images

Suggestions pour la représentation des personnes en situation de handicap. Les personnes en situation de handicap demandent aux Canadiens, et aux médias en particulier, d'utiliser des termes respectueux lorsqu'ils écrivent et parlent d'elles ou des questions qui les concernent. Elles demandent également que les images choisies pour les représenter soient respectueuses et ne renforcent pas des stéréotypes dépassés.

Microsoft Windows 11 L’accessibilité pour tous

Ressources utiles sur les fonctions d'accessibilité de Microsoft Windows 11.

Quels outils de vidéoconférence sont les plus accessibles ? (en anglais seulement)

Dans cet article, Claudio Luis Vera explique ce qu’il faut garder à l’esprit lors du choix d’un outil de vidéoconférence pour que tous les membres de votre équipe puissent en profiter — notamment ceux avec des handicaps.

YouTube : Apple : Accessibilité (en anglais seulement)

De l’utilisation de votre iPhone sans voir l’écran, à l’adaptation des gestes à vos besoins physiques, découvrez comment les fonctionnalités d’accessibilité intégrées à vos appareils Apple peuvent vous aider à en faire plus.

Développement

Boîte à outils de l’expérience Web (BOEW)

Un cadre frontal primé pour la création de sites Web accessibles, utilisables, interopérables, adaptés aux téléphones portables et multilingues.

Liste de vérification pour l’accessibilité Web

Liste de verification develop par ESDC.

Méthodologie d’évaluation sur l’accessibilité des sites Web (niveau AA) (en anglais seulement)

Aider à mesurer les critères de succès de niveau A et AA des Règles pour l’accessibilité des contenus Web (WCAG) 2.1.

Solution de gabarits à déploiement centralisé (SGDC)

L’objectif de la SGDC consiste essentiellement à fournir la couche de présentation du thème de Canada.ca ou du thème d’Intranet.canada.ca aux actifs Web.

Soutien à l'accessibilité (en anglais seulement)

Vérifiez si votre code fonctionnera avec les technologies d'assistance.

Système de conception de Canada.ca

Utilisez ce système de conception pour offrir une expérience en ligne plus conviviale, cohérente et fiable aux personnes qui accèdent aux services numériques du gouvernement du Canada. Le contenu du système de conception comprend :

Amélioration continue du contenu Web

Choisir quoi améliorer, organiser et préparer votre équipe, recherche et prototypage, concevoir le contenu, suivi et mesure du succès.

Bibliothèque de modèles et configurations de conception

Modèles, mises en page, configurations de conception, directives et exemples de code, testés par les utilisateurs.

Blogue Canada.ca

Données probantes et observations sur l’amélioration des renseignements et des services sur Canada.ca.

Derniers changements apportés au système de conception de Canada.ca

Derniers changements apportés au système de conception, aux modèles et conceptions de configuration, au guide de rédaction et aux autres outils.

Guide de rédaction du contenu du site Canada.ca

Techniques d’écriture et principes qui aident à rendre le contenu clair et adapté aux besoins de tous.

Spécifications du contenu et de l'architecture de l'information pour Canada.ca

Qui doit utiliser le système de conception de Canada.ca, éléments obligatoires, comment organiser et concevoir du contenu.

Politique

Authoring Tool Accessibility Guidelines (ATAG) Overview (en anglais seulement) - Initiative pour l'accessibilité du Web (WAI)

Les outils de création sont des logiciels et des services que les "auteurs" (développeurs web, concepteurs, rédacteurs, etc.) utilisent pour produire du contenu web (pages web statiques, applications web dynamiques, etc.)

Directive visant à rendre les technologies de l’information utilisables par tous

Cette ligne directrice soutient la direction du gouvernement du Canada pour s’assurer que les ministères, les agences et les organisations prennent en compte l’accessibilité lors de l’acquisition ou du développement d’équipement et de solutions de la technologie de l’information (TI) pour rendre la TI utilisable par tous.

EU EN 301 549 (Gestion de l’accessibilité dans les marchés publics des TIC) (en anglais seulement)

Les exigences en matière d’accessibilité qui conviennent à l’approvisionnement, par les organismes publics, de produits et services de technologies de l’information et des communications (TIC) en Europe.

Règles pour l’accessibilité des contenus Web 2.1

Les Règles pour l’accessibilité des contenus Web (WCAG) 2.1 couvrent un large éventail de recommandations pour rendre les contenus Web plus accessibles. Suivre ces règles rendra aussi les contenus Web souvent plus faciles d’utilisation aux utilisateurs en général.

Directive sur les services et le numérique

Décrit la façon dont les organisations du gouvernement du Canada gèrent la prestation de services, l’information et les données, la technologie de l’information et la cybersécurité à l’ère du numérique.

Directive sur l’obligation de prendre des mesures d’adaptation

La directive donne des orientations aux gestionnaires et aux chefs des ressources humaines quant à leurs obligations de prendre des mesures d’adaptation afin d’instaurer un milieu de travail inclusif et sans obstacles qui offre à tous des chances égales au sein de l’administration publique centrale.

Directive sur la gestion des communications

Prévoit les règles pour la gestion et la coordination des communications, y compris les procédures relatives à la publicité, les recherches sur l’opinion publique, les médias sociaux et les communications Web.

Stratégie sur l’accessibilité au sein de la fonction publique du Canada

Améliorer l’accessibilité, les mesures d’adaptation, l’ergonomie, les données et les stages. Stratégie d’accessibilité pour la fonction publique

Loi canadienne sur l’accessibilité - Site Web de la législation

Source en ligne des lois et règlements consolidés du Canada.

Glossaire de l'accessibilité

Ce glossaire contient 342 concepts et terminologies liés au projet de loi C-81 dans les domaines de la sociologie du travail et des aides techniques aux personnes handicapées.

La Loi sur l'accessibilité du Canada en langage clair et simple (en anglais seulement)

Ce document aide les gens à comprendre les principaux points du projet de loi C-81 ; une loi visant à assurer un Canada sans obstacles.

Approvisionnement

Accessibilité à Services publics et Approvisionnement Canada

En tant que fournisseur de services communs du gouvernement du Canada, le SPAC s'efforce d'offrir un excellent service aux autres ministères fédéraux. En cherchant à améliorer l'accès à ses programmes et services pour les personnes handicapées, SPAC aide les ministères fédéraux à offrir des programmes et services de haute qualité à tous les Canadiens.

Réunions et événements virtuels accessibles

Les réunions et événements virtuels sont caractérisés par différents formats et différentes tailles, allant de petits ateliers comprenant des participants qui se connaissent à de grandes réunions publiques à planifier. Il est essentiel de veiller à ce que ces réunions et événements soient pleinement accessibles, depuis leur accès jusqu’aux présentations. En planifiant, vous pouvez intégrer l’accessibilité à tous les aspects d’une réunion. Cela permet à tout le monde de pleinement participer, y compris les personnes en situation de handicap.

Afin de vous aider à offrir une réunion ou une activité virtuelle pleinement accessible, qu’il s’agisse d’une séance de formation, d’une réunion, d’un kiosque ou d’une journée portes ouvertes, le Bureau de l’accessibilité des TI (BATI) a rassemblé les renseignements les plus pertinents à ce sujet.

GcWiki Microsoft 365 Teams

Une collection de produits de formation MS Teams pour aider les fonctionnaires.

Directives relatives aux réunions/événements accessibles

Une planification adéquate de réunions et d’événements est essentielle pour assurer l’inclusion de tout le monde. Plusieurs éléments doivent être pris en compte avant et pendant les réunions et activités.

Meilleures pratiques pour vos demandes d’interprétation des conférences et d’interprétation en langues des signes et translittération orale

Meilleures pratiques pour vos demandes de conférence et d'interprétation en langue des signes.

Outil de travail planification d’événements virtuels accessibles de l’École de la fonction publique du Canada

Cet outil de travail présente des pratiques exemplaires pour planifier des événements virtuels accessibles et inclusifs.

Planifier des événements inclusifs et accessibles – Guide à l’intention des fonctionnaires fédéraux Lien interne du Bureau de la condition des personnes handicapée/Emploi et Développement social Canada (EDSC) (Plutôt pour les rencontres en personne)

Le Bureau de la condition des personnes handicapées (BCPH) est fier de présenter ce guide à des collègues du gouvernement du Canada afin de fournir une orientation sur la planification d’événements inclusifs et accessibles.

Plateformes de réunions virtuelles et fonctionnalités d’accessibilité

Les plateformes de réunion virtuelle Microsoft Teams et Zoom proposent une variété de fonctionnalités d’accessibilité répondant à différents besoins en matière de participation à des réunions et discussions en ligne.

Recommandations en matière de langues officielles

Pratiques exemplaires à suivre pour les réunions et événements unilingues ou bilingues pour les deux langues officielles.

Recommandations pour la configuration et l’exécution d’une réunion teams ou d’un événement en direct pour les personnes sourdes ou malentendantes

Lors de la configuration et de l’exécution de Microsoft Teams réunions et d’événements en direct, il est important de connaître les bonnes pratiques pour s’assurer que votre contenu est accessible aux sourds et malentendants. Les fonctionnalités telles que les sous-titres en direct et le choix d’un arrière-plan clair sont importantes pour s’assurer que tout le monde peut participer de manière égale.

Répertoire de l’Association des traducteurs et interprètes de l’Ontario (ATIO)

Trouvez un traducteur, un interprète ou un terminologue pour des réunions et des événements.

Services CART et interprètes en langue des signes

La mesure d’adaptation la plus courante pour les réunions ou les événements est la traduction en temps réel des communications (CART) et les services d’interprétation.

Tirez parti des fonctionnalités d’accessibilité de Microsoft Teams pour une expérience de réunion ou d’événement en direct plus agréable

Types de réunions proposées et fonctionnalités d’accessibilité

Nos recommandations pour choisir des plateformes de réunion virtuelle en fonction du type de réunion ou d’activité, du nombre de personnes et du contenu partagé.

Vue d’ensemble de l’accessibilité dans Microsoft Teams

Cette page contient une vue d'ensemble des nombreuses fonctions d'accessibilité qui permettent à tous les utilisateurs de bénéficier de la meilleure expérience possible, y compris les fonctions d'accessibilité pour une meilleure expérience des réunions ou des événements en direct, et les meilleures pratiques pour la mise en place et le déroulement d'une réunion Teams ou d'un événement en direct pour les sourds et les malentendants.

Services

Détails de la page

Date de modification :
\ No newline at end of file diff --git a/fr/services-cart-et-interpretes-en-langue-des-signes-sli/index.html b/fr/services-cart-et-interpretes-en-langue-des-signes-sli/index.html index 010b49f45..2cf372415 100644 --- a/fr/services-cart-et-interpretes-en-langue-des-signes-sli/index.html +++ b/fr/services-cart-et-interpretes-en-langue-des-signes-sli/index.html @@ -1,4 +1,4 @@ -Services CART et interprètes en langue des signes (SLI) - Boîte à outils de l'accessibilité numérique

Sélection de la langue

Gouvernement du Canada / Gouvernement du Canada

Recherche

Services CART et interprètes en langue des signes (SLI)

Les services d'hébergement les plus courants pour les réunions ou les événements sont les services de transcription en temps réel assistés par ordinateur (CART) et d'interprétation.

Informations importantes

  • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

Il est important de prévoir que les personnes culturellement sourdes puissent préférer un service d’interprétation en langue des signes, car leur langue maternelle est probablement la langue des signes des États-Unis (ASL) ou la langue des signes québécoise (LSQ), mais ne le présumez pas. Demandez à ces personnes la mesure d’adaptation qu’elles préfèrent. En effet, des personnes devenues sourdes plus tard dans leur vie peuvent ne pas avoir appris à communiquer avec l’(ASL) ou la LSQ.

Traduction en temps réel des communications (CART)

Interprètation en langue des signes

Les services d’interprètes en langue des signes sont obtenus de deux façons: par l’intermédiaire du Bureau de la traduction ou auprès de fournisseurs externes.

Bureau de la traduction

  • Détails de la page

    Date de modification :
    \ No newline at end of file + })(window);

    Sélection de la langue

    Gouvernement du Canada / Gouvernement du Canada

    Recherche

    Services CART et interprètes en langue des signes (SLI)

    Les services d'hébergement les plus courants pour les réunions ou les événements sont les services de transcription en temps réel assistés par ordinateur (CART) et d'interprétation.

    Informations importantes

    • Les liens qui ne fonctionnent que derrière le pare-feu du gouvernement du Canada sont marqués avec lien interne

    Il est important de prévoir que les personnes culturellement sourdes puissent préférer un service d’interprétation en langue des signes, car leur langue maternelle est probablement la langue des signes des États-Unis (ASL) ou la langue des signes québécoise (LSQ), mais ne le présumez pas. Demandez à ces personnes la mesure d’adaptation qu’elles préfèrent. En effet, des personnes devenues sourdes plus tard dans leur vie peuvent ne pas avoir appris à communiquer avec l’(ASL) ou la LSQ.

    Traduction en temps réel des communications (CART)

    Interprètation en langue des signes

    Les services d’interprètes en langue des signes sont obtenus de deux façons: par l’intermédiaire du Bureau de la traduction ou auprès de fournisseurs externes.

    Bureau de la traduction

  • Détails de la page

    Date de modification :
    \ No newline at end of file diff --git a/fr/statistique-canada-statcan/index.html b/fr/statistique-canada-statcan/index.html index e033d6d59..81acaeb9e 100644 --- a/fr/statistique-canada-statcan/index.html +++ b/fr/statistique-canada-statcan/index.html @@ -1,4 +1,4 @@ -Statistique Canada (StatCan) - Boîte à outils de l'accessibilité numérique

    Sélection de la langue

    Gouvernement du Canada / Gouvernement du Canada

    Recherche

    Statistique Canada (StatCan)

    Statistique Canada, en collaboration avec des partenaires d'Emploi et Développement social Canada, continuera d'élaborer et de diffuser des produits permettant de mieux comprendre les expériences des Canadiens en matière d'accessibilité. Le carrefour de données sur l'accessibilité offre un emplacement centralisé de sujets liés à l'accessibilité et à l'incapacité par le biais de tableaux de données, d'articles, d'infographies et d'outils interactifs de visualisation de données.

    Secrétariat de l’accessibilité de StatCan

    Le Secrétariat de l’accessibilité est un centre de soutien interne de StatCan ayant pour objet d’aider les divisions de StatCan à mieux comprendre l’accessibilité et à renforcer leur capacité en la matière. Il favorise l’établissement d’une relation dynamique avec les employés, les répondants et les utilisateurs de données ayant une incapacité. Il oriente aussi l’élaboration de plans et de rapports qui satisfont aux exigences de la Loi canadienne sur l’accessibilité ainsi qu’aux objectifs définis par l’organisme à partir de ceux énoncés dans la Loi et de ceux qui sont précisés dans la stratégie du Bureau de l’accessibilité au sein de la fonction publique.

    Centre d’expertise en accessibilité (CEA)

    Le Centre d'expertise sur l'accessibilité offre une expertise sur l'accessibilité à l'interne à StatCan afin de s'assurer que tous les Canadiens ont un accès égal, quelles que soient leurs capacités, leurs langues officielles et leurs technologies d'adaptation. L'équipe évalue la conformité par rapport aux exigences internationales sur l’accessibilité du Consortium World Wide Web (W3C); fournit des conseils et des commentaires ainsi que proposeé des solutions relativement aux problèmes d’accessibilité au contenu Web les plus courants du gouvernement du Canada; vérifie de quelle façon un produit est visualisé et fonctionne avec le logiciel des lecteurs d’écran et d’autres technologies d’adaptation, comme JAWS, NVDA et un afficheur braille; produit des formats alternatifs sur demande (formats multiples - Braille/audio); et promouvoir la connaissance et l’harmonisation des meilleures pratiques et technologies actuelles relatives à l’expérience de l’utilisateur sur le Web aux prises avec différents types d’incapacités.

    Détails de la page

    Date de modification :
    \ No newline at end of file + })(window);

    Sélection de la langue

    Gouvernement du Canada / Gouvernement du Canada

    Recherche

    Statistique Canada (StatCan)

    Statistique Canada, en collaboration avec des partenaires d'Emploi et Développement social Canada, continuera d'élaborer et de diffuser des produits permettant de mieux comprendre les expériences des Canadiens en matière d'accessibilité. Le carrefour de données sur l'accessibilité offre un emplacement centralisé de sujets liés à l'accessibilité et à l'incapacité par le biais de tableaux de données, d'articles, d'infographies et d'outils interactifs de visualisation de données.

    Secrétariat de l’accessibilité de StatCan

    Le Secrétariat de l’accessibilité est un centre de soutien interne de StatCan ayant pour objet d’aider les divisions de StatCan à mieux comprendre l’accessibilité et à renforcer leur capacité en la matière. Il favorise l’établissement d’une relation dynamique avec les employés, les répondants et les utilisateurs de données ayant une incapacité. Il oriente aussi l’élaboration de plans et de rapports qui satisfont aux exigences de la Loi canadienne sur l’accessibilité ainsi qu’aux objectifs définis par l’organisme à partir de ceux énoncés dans la Loi et de ceux qui sont précisés dans la stratégie du Bureau de l’accessibilité au sein de la fonction publique.

    Centre d’expertise en accessibilité (CEA)

    Le Centre d'expertise sur l'accessibilité offre une expertise sur l'accessibilité à l'interne à StatCan afin de s'assurer que tous les Canadiens ont un accès égal, quelles que soient leurs capacités, leurs langues officielles et leurs technologies d'adaptation. L'équipe évalue la conformité par rapport aux exigences internationales sur l’accessibilité du Consortium World Wide Web (W3C); fournit des conseils et des commentaires ainsi que proposeé des solutions relativement aux problèmes d’accessibilité au contenu Web les plus courants du gouvernement du Canada; vérifie de quelle façon un produit est visualisé et fonctionne avec le logiciel des lecteurs d’écran et d’autres technologies d’adaptation, comme JAWS, NVDA et un afficheur braille; produit des formats alternatifs sur demande (formats multiples - Braille/audio); et promouvoir la connaissance et l’harmonisation des meilleures pratiques et technologies actuelles relatives à l’expérience de l’utilisateur sur le Web aux prises avec différents types d’incapacités.

    Détails de la page

    Date de modification :
    \ No newline at end of file diff --git a/fr/test-d-accessibilite-101/index.html b/fr/test-d-accessibilite-101/index.html index db99a9bf5..956de8385 100644 --- a/fr/test-d-accessibilite-101/index.html +++ b/fr/test-d-accessibilite-101/index.html @@ -1,4 +1,4 @@ -Test d’accessibilité 101 - Boîte à outils de l'accessibilité numérique

    Sélection de la langue

    Gouvernement du Canada / Gouvernement du Canada

    Recherche

    Test d’accessibilité 101

    Nous encourageons tous ceux qui souhaitent créer du contenu accessible à utiliser des outils de test d’accessibilité automatisés. Ces outils aident les créateurs de contenu à développer leurs contenus en détectant les erreurs et en proposant des suggestions pour améliorer l’accessibilité de leur produit, de leur application ou de leur site Web. Cette page présente une liste d’outils de test d’accessibilité recommandés.

    Sur cette page

    Veuillez noter que certains des outils de test d’accessibilité répertoriés nécessitent des autorisations administratives pour être installés sur votre appareil.

    Création d’un ensemble d’outils

    Outil : Extensions de navigateur WAVE

    L’extension WAVE pour Chrome, Firefox et Edge vous permet d’évaluer le contenu web pour les problèmes d’accessibilité directement dans votre navigateur. Comme l’extension fonctionne entièrement dans votre navigateur web, aucune information n’est envoyée au serveur WAVE.

    Bien que WAVE soit plus efficace lorsqu’il est utilisé par une personne connaissant bien l’accessibilité du web, les personnes qui ne sont pas des experts en accessibilité du web peuvent également en tirer profit.

    Si vous ne connaissez pas WAVE, profitez de la vidéo d’introduction à WAVE (en anglais seulement).

    Compatibilité des navigateurs:

    Documentation supplémentaire sur WAVE:

    Trucs et astuces sur WAVE:

    La barre latérale de WAVE indique si WAVE a détecté des erreurs ou non. L’absence d’erreurs ne signifie pas que votre page est accessible ou conforme. Les icônes rouges indiquent les erreurs d’accessibilité qui doivent être corrigées. Les icônes vertes indiquent des caractéristiques d’accessibilité, c’est-à-dire des éléments qui améliorent l’accessibilité (bien qu’il faille les vérifier). Les autres icônes et indicateurs, en particulier les icônes d’alerte jaunes, mettent en évidence d’autres éléments qu’il convient d’examiner. WAVE met en évidence les informations sous-jacentes relatives à l’accessibilité d’une page afin qu’elles puissent être facilement évaluées dans leur contexte.

    Styles et code:

    WAVE permet de désactiver les feuilles de style en cascade (CSS) des pages. Les mises en page complexes basées sur les feuilles de style en cascade peuvent devenir difficiles à lire, en particulier après l’intégration des icônes WAVE, de sorte que la désactivation des styles peut simplifier la présentation de la page. La désactivation des styles vous permet également de voir l’ordre de lecture et de navigation sous-jacent; c’est-à-dire l’ordre dans lequel les utilisateurs, de clavier (seulement) et de lecteurs d’écran, accèdent à la page. Pour visualiser le code correspondant à une icône WAVE particulière, vous pouvez sélectionner l’onglet Code au bas de la page pour visualiser le balisage/DOM sous-jacent de votre page.

    Outil : Accessibility Insights for Web

    « Accessibility Insights for Web » est une extension pour Chrome et Microsoft Edge qui aide les développeurs à trouver et à résoudre les problèmes d’accessibilité dans les applications et les sites Web.

    L’outil prend en charge deux scénarios principaux:

    Il s’agit d’un outil pour tous les niveaux, vous n’avez pas besoin de connaître l’accessibilité pour l’utiliser, il vous guidera à chaque étape.

    Compatibilité des navigateurs:

    Documentation sur Accessibility Insights:

    Conseils et astuces:

    Raccourcis clavier:

    Outil: LightHouse

    Lighthouse est un outil automatisé à code source ouvert qui permet d’améliorer la qualité des pages web. Il peut être exécuté sur n’importe quelle page web, qu’elle soit publique ou qu’elle nécessite une authentification. Il propose des audits pour les performances, l’accessibilité, les applications web progressives, le référencement, etc. Un outil très utile pour les développeurs multimédias et les testeurs d’accessibilité du web.

    Navigateurs:

    Documentation sur l’extension LightHouse:

    Aide supplémentaire:

    Aide et ressources supplémentaires

    Tests clavier et manuels de votre site

    Outils automatisés et validateurs pour identifier les problèmes d’accessibilité :

    Principes de base des tests au clavier

    Examinez ou testez votre site périodiquement pour vous assurer qu’il n’y a pas de nouvelles erreurs et qu’il reste accessible.

    Ressources supplémentaires

    Détails de la page

    Date de modification :
    \ No newline at end of file + })(window);

    Sélection de la langue

    Gouvernement du Canada / Gouvernement du Canada

    Recherche

    Test d’accessibilité 101

    Nous encourageons tous ceux qui souhaitent créer du contenu accessible à utiliser des outils de test d’accessibilité automatisés. Ces outils aident les créateurs de contenu à développer leurs contenus en détectant les erreurs et en proposant des suggestions pour améliorer l’accessibilité de leur produit, de leur application ou de leur site Web. Cette page présente une liste d’outils de test d’accessibilité recommandés.

    Sur cette page

    Veuillez noter que certains des outils de test d’accessibilité répertoriés nécessitent des autorisations administratives pour être installés sur votre appareil.

    Création d’un ensemble d’outils

    Outil : Extensions de navigateur WAVE

    L’extension WAVE pour Chrome, Firefox et Edge vous permet d’évaluer le contenu web pour les problèmes d’accessibilité directement dans votre navigateur. Comme l’extension fonctionne entièrement dans votre navigateur web, aucune information n’est envoyée au serveur WAVE.

    Bien que WAVE soit plus efficace lorsqu’il est utilisé par une personne connaissant bien l’accessibilité du web, les personnes qui ne sont pas des experts en accessibilité du web peuvent également en tirer profit.

    Si vous ne connaissez pas WAVE, profitez de la vidéo d’introduction à WAVE (en anglais seulement).

    Compatibilité des navigateurs:

    Documentation supplémentaire sur WAVE:

    Trucs et astuces sur WAVE:

    La barre latérale de WAVE indique si WAVE a détecté des erreurs ou non. L’absence d’erreurs ne signifie pas que votre page est accessible ou conforme. Les icônes rouges indiquent les erreurs d’accessibilité qui doivent être corrigées. Les icônes vertes indiquent des caractéristiques d’accessibilité, c’est-à-dire des éléments qui améliorent l’accessibilité (bien qu’il faille les vérifier). Les autres icônes et indicateurs, en particulier les icônes d’alerte jaunes, mettent en évidence d’autres éléments qu’il convient d’examiner. WAVE met en évidence les informations sous-jacentes relatives à l’accessibilité d’une page afin qu’elles puissent être facilement évaluées dans leur contexte.

    Styles et code:

    WAVE permet de désactiver les feuilles de style en cascade (CSS) des pages. Les mises en page complexes basées sur les feuilles de style en cascade peuvent devenir difficiles à lire, en particulier après l’intégration des icônes WAVE, de sorte que la désactivation des styles peut simplifier la présentation de la page. La désactivation des styles vous permet également de voir l’ordre de lecture et de navigation sous-jacent; c’est-à-dire l’ordre dans lequel les utilisateurs, de clavier (seulement) et de lecteurs d’écran, accèdent à la page. Pour visualiser le code correspondant à une icône WAVE particulière, vous pouvez sélectionner l’onglet Code au bas de la page pour visualiser le balisage/DOM sous-jacent de votre page.

    Outil : Accessibility Insights for Web

    « Accessibility Insights for Web » est une extension pour Chrome et Microsoft Edge qui aide les développeurs à trouver et à résoudre les problèmes d’accessibilité dans les applications et les sites Web.

    L’outil prend en charge deux scénarios principaux:

    Il s’agit d’un outil pour tous les niveaux, vous n’avez pas besoin de connaître l’accessibilité pour l’utiliser, il vous guidera à chaque étape.

    Compatibilité des navigateurs:

    Documentation sur Accessibility Insights:

    Conseils et astuces:

    Raccourcis clavier:

    Outil: LightHouse

    Lighthouse est un outil automatisé à code source ouvert qui permet d’améliorer la qualité des pages web. Il peut être exécuté sur n’importe quelle page web, qu’elle soit publique ou qu’elle nécessite une authentification. Il propose des audits pour les performances, l’accessibilité, les applications web progressives, le référencement, etc. Un outil très utile pour les développeurs multimédias et les testeurs d’accessibilité du web.

    Navigateurs:

    Documentation sur l’extension LightHouse:

    Aide supplémentaire:

    Aide et ressources supplémentaires

    Tests clavier et manuels de votre site

    Outils automatisés et validateurs pour identifier les problèmes d’accessibilité :

    Principes de base des tests au clavier

    Examinez ou testez votre site périodiquement pour vous assurer qu’il n’y a pas de nouvelles erreurs et qu’il reste accessible.

    Ressources supplémentaires

    Détails de la page

    Date de modification :
    \ No newline at end of file diff --git a/fr/texte-alternatif-et-description-longue-bonnes-pratiques/index.html b/fr/texte-alternatif-et-description-longue-bonnes-pratiques/index.html index ab8479cd3..d43c33af7 100644 --- a/fr/texte-alternatif-et-description-longue-bonnes-pratiques/index.html +++ b/fr/texte-alternatif-et-description-longue-bonnes-pratiques/index.html @@ -1,4 +1,4 @@ -Texte alternatif et description longue - Bonnes pratiques - Boîte à outils de l'accessibilité numérique

    Sélection de la langue

    Gouvernement du Canada / Gouvernement du Canada

    Recherche

    Texte alternatif et description longue - Bonnes pratiques

    Un texte alternatif (ou texte alt) est un texte qui décrit et transmet la signification d'un élément visuel non textuel tel qu'une image, un organigramme, un graphique, etc. Ce document vous aidera à déterminer le type de texte alternatif nécessaire et vous donnera des conseils pour rédiger un texte alternatif et des descriptions longues pour des images simples et complexes, telles que des graphiques, des cartes, etc.

    Description

    Le texte alternatif, également connu sous le nom de texte de remplacement ou de texte Alt, est un texte qui décrit et transmet la signification d'un élément visuel non textuel tel qu'une image, un organigramme, un graphique ou un tableau.

    L'ajout d'un texte alternatif profite à de nombreux utilisateurs, tels que:

    Déterminer le type de texte alternatif

    Posez-vous les questions suivantes:

    Si l'image ne transmet pas d'information ou si l'information est disponible dans le document/la page, elle est décorative.

    Texte alternatif pour les images décoratives

    Pour Word et PowerPoint, tapez « Décoratif » dans la zone de texte de remplacement. Ne cochez pas la case « Marquer comme décoratif », car certaines personnes peuvent utiliser une version plus ancienne de Word/PowerPoint et la case ne s'appliquera pas.

    Le fait de marquer une image comme décorative varie selon les systèmes de gestion de l'apprentissage. Lors de la conception d'un produit web en HTML, le W3C recommande d'utiliser un texte alternatif nul (ou vide) qui est un guillemet ouvert et fermé (alt="").

    Un texte alternatif qui est significatif

    Texte en tant qu'image

    Parfois, les utilisateurs souhaitent personnaliser le texte en fonction de leurs besoins, par exemple en augmentant la taille de la police, en modifiant sa couleur, etc. Lorsque le texte est présenté sous forme d'image, il est difficile pour l'utilisateur de le personnaliser. Dans la mesure du possible, utilisez du texte avec des feuilles de style CSS pour appliquer un style comme la famille de polices et la couleur.

    Si un logo est utilisé, fournissez un texte alternatif du texte se trouvant dans le logo.

    Images complexes

    Tableaux et graphiques

    Le texte alternatif doit contenir les informations suivantes :

    Votre description longue doit fournir les mêmes informations que celles présentées dans le tableau ou le graphique. Elle doit inclure des informations telles que

    En fonction du graphique et des informations qu'il tente de transmettre, la description longue peut être présentée sous la forme d'un tableau, en tenant compte des éléments nécessaires à la création d'un tableau accessible. Voici quelques exemples de descriptions longues de graphiques et de tableaux.

    Organigrammes et cartes conceptuelles

    Lorsqu'on utilise un organigramme ou une carte conceptuelle pour montrer un processus ou la relation entre des concepts, la description longue peut être rédigée sous la forme d'une liste. Voici deux exemples de descriptions longues pour les organigrammes:

    Tableaux

    Pour Word et PowerPoint

    HTML:

    Cartes

    Comme pour les autres images, lorsque vous réfléchissez au texte alternatif des cartes, pensez à l'objectif ou au contexte de la carte. Montre-t-elle un lieu? Plusieurs lieux? Des directions?

    Un lieu ou des points de repère ou des lieux

    Indiquez le point de repère et l'adresse. Par exemple: la Chambre des communes est située à l'édifice de l'Ouest (111, rue Wellington) sur la colline du Parlement à Ottawa (Ontario).

    Plusieurs lieux ou points de repère

    Fournir un contexte sur la nature des lieux ou des points de repère. Si la carte montre plusieurs lieux ou points de repère, une longue description sera probablement nécessaire. Par exemple: Emplacement des arrêts d'autobus au centre-ville de Fredericton. Une longue description suit.

    Itinéraire

    Si la carte indique des directions, le texte alternatif doit le refléter. La description longue serait un simple texte d'orientation. Par exemple: Itinéraire depuis la gare de l'aéroport (arrêt ID 5844) jusqu'au ministère de la Justice du Canada. Une description longue suit.

    Conseils pour la rédaction de descriptions longues

    Liens utiles sur le texte alternatif

    Détails de la page

    Date de modification :
    \ No newline at end of file + })(window);

    Sélection de la langue

    Gouvernement du Canada / Gouvernement du Canada

    Recherche

    Texte alternatif et description longue - Bonnes pratiques

    Un texte alternatif (ou texte alt) est un texte qui décrit et transmet la signification d'un élément visuel non textuel tel qu'une image, un organigramme, un graphique, etc. Ce document vous aidera à déterminer le type de texte alternatif nécessaire et vous donnera des conseils pour rédiger un texte alternatif et des descriptions longues pour des images simples et complexes, telles que des graphiques, des cartes, etc.

    Description

    Le texte alternatif, également connu sous le nom de texte de remplacement ou de texte Alt, est un texte qui décrit et transmet la signification d'un élément visuel non textuel tel qu'une image, un organigramme, un graphique ou un tableau.

    L'ajout d'un texte alternatif profite à de nombreux utilisateurs, tels que:

    Déterminer le type de texte alternatif

    Posez-vous les questions suivantes:

    Si l'image ne transmet pas d'information ou si l'information est disponible dans le document/la page, elle est décorative.

    Texte alternatif pour les images décoratives

    Pour Word et PowerPoint, tapez « Décoratif » dans la zone de texte de remplacement. Ne cochez pas la case « Marquer comme décoratif », car certaines personnes peuvent utiliser une version plus ancienne de Word/PowerPoint et la case ne s'appliquera pas.

    Le fait de marquer une image comme décorative varie selon les systèmes de gestion de l'apprentissage. Lors de la conception d'un produit web en HTML, le W3C recommande d'utiliser un texte alternatif nul (ou vide) qui est un guillemet ouvert et fermé (alt="").

    Un texte alternatif qui est significatif

    Texte en tant qu'image

    Parfois, les utilisateurs souhaitent personnaliser le texte en fonction de leurs besoins, par exemple en augmentant la taille de la police, en modifiant sa couleur, etc. Lorsque le texte est présenté sous forme d'image, il est difficile pour l'utilisateur de le personnaliser. Dans la mesure du possible, utilisez du texte avec des feuilles de style CSS pour appliquer un style comme la famille de polices et la couleur.

    Si un logo est utilisé, fournissez un texte alternatif du texte se trouvant dans le logo.

    Images complexes

    Tableaux et graphiques

    Le texte alternatif doit contenir les informations suivantes :

    Votre description longue doit fournir les mêmes informations que celles présentées dans le tableau ou le graphique. Elle doit inclure des informations telles que

    En fonction du graphique et des informations qu'il tente de transmettre, la description longue peut être présentée sous la forme d'un tableau, en tenant compte des éléments nécessaires à la création d'un tableau accessible. Voici quelques exemples de descriptions longues de graphiques et de tableaux.

    Organigrammes et cartes conceptuelles

    Lorsqu'on utilise un organigramme ou une carte conceptuelle pour montrer un processus ou la relation entre des concepts, la description longue peut être rédigée sous la forme d'une liste. Voici deux exemples de descriptions longues pour les organigrammes:

    Tableaux

    Pour Word et PowerPoint

    HTML:

    Cartes

    Comme pour les autres images, lorsque vous réfléchissez au texte alternatif des cartes, pensez à l'objectif ou au contexte de la carte. Montre-t-elle un lieu? Plusieurs lieux? Des directions?

    Un lieu ou des points de repère ou des lieux

    Indiquez le point de repère et l'adresse. Par exemple: la Chambre des communes est située à l'édifice de l'Ouest (111, rue Wellington) sur la colline du Parlement à Ottawa (Ontario).

    Plusieurs lieux ou points de repère

    Fournir un contexte sur la nature des lieux ou des points de repère. Si la carte montre plusieurs lieux ou points de repère, une longue description sera probablement nécessaire. Par exemple: Emplacement des arrêts d'autobus au centre-ville de Fredericton. Une longue description suit.

    Itinéraire

    Si la carte indique des directions, le texte alternatif doit le refléter. La description longue serait un simple texte d'orientation. Par exemple: Itinéraire depuis la gare de l'aéroport (arrêt ID 5844) jusqu'au ministère de la Justice du Canada. Une description longue suit.

    Conseils pour la rédaction de descriptions longues

    Liens utiles sur le texte alternatif

    Détails de la page

    Date de modification :
    \ No newline at end of file diff --git a/sitemap.xml b/sitemap.xml index 675cf2026..e3c3042c5 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -286,11 +286,6 @@ 2023-11-27 - - https://a11y.canada.ca/en/introduction-to-accessibility-requirements-for-audio-video/ - 2023-11-27 - - https://a11y.canada.ca/en/live-broadcast/ 2023-11-27 @@ -316,11 +311,6 @@ 2023-11-27 - - https://a11y.canada.ca/en/statistics-canada-statcan/ - 2023-11-27 - - https://a11y.canada.ca/en/targeted-engagement-draft-standard-on-information-and-communication-technology-ict-accessibility/ 2023-11-27 @@ -361,16 +351,6 @@ 2023-11-27 - - https://a11y.canada.ca/fr/introduction-aux-exigences-d-accessibilite-pour-l-audio-video/ - 2023-11-27 - - - - https://a11y.canada.ca/fr/le-groupe-de-travail-sur-l-acces-gta/ - 2023-11-27 - - https://a11y.canada.ca/fr/liste-de-controle-des-transcriptions/ 2023-11-27 @@ -381,11 +361,6 @@ 2023-11-27 - - https://a11y.canada.ca/fr/plateformes-de-reunions-virtuelles-et-fonctionnalites/ - 2023-11-27 - - https://a11y.canada.ca/fr/rapport-sur-ce-que-nous-avons-entendu-norme-d-accessibilite-des-technologies-de-l-information-et-des-communications-natic/ 2023-11-27 @@ -396,11 +371,6 @@ 2023-11-27 - - https://a11y.canada.ca/fr/statistique-canada-statcan/ - 2023-11-27 - - https://a11y.canada.ca/en/language-of-audio-video-content/ 2023-11-27 @@ -851,46 +821,16 @@ 2023-11-28 - - https://a11y.canada.ca/en/access-working-group-awg/ - 2023-11-29 - - - - https://a11y.canada.ca/fr/services-cart-et-interpretes-en-langue-des-signes-sli/ - 2023-11-29 - - - - https://a11y.canada.ca/en/mapping-between-revised-section-508-and-en-301-549-2014-2018-2019-and-2021/ - 2023-11-29 - - - - https://a11y.canada.ca/en/microsoft-document-compliance-checklist/ - 2023-11-29 - - https://a11y.canada.ca/en/additional-resources-on-accessible-meetings-and-events/ 2023-11-30 - - https://a11y.canada.ca/fr/ressources-additionnelles-sur-les-reunions-et-evenements-accessibles/ - 2023-11-30 - - https://a11y.canada.ca/en/contact-us/ 2023-11-30 - - https://a11y.canada.ca/en/useful-links/ - 2023-11-30 - - https://a11y.canada.ca/en/about-us/ 2023-12-01 @@ -921,26 +861,11 @@ 2023-12-01 - - https://a11y.canada.ca/fr/mise-en-correspondance-entre-l-article-508-revise-revised-section-508-et-la-norme-en-301-549-2014-2018-2019-et-2021/ - 2023-12-01 - - https://a11y.canada.ca/404.html 2023-12-01 - - https://a11y.canada.ca/en/pdf-accessibility-checklist/ - 2023-12-01 - - - - https://a11y.canada.ca/en/find-out-how-to-make-accessible-digital-forms/ - 2023-12-01 - - https://a11y.canada.ca/en/accessible-excel-workbooks-in-microsoft-365/ 2023-12-01 @@ -956,21 +881,6 @@ 2023-12-01 - - https://a11y.canada.ca/fr/emploi-et-developpement-social-canada-edsc/ - 2023-12-01 - - - - https://a11y.canada.ca/en/employment-and-social-development-canada-esdc/ - 2023-12-01 - - - - https://a11y.canada.ca/en/auditory-disabilities/ - 2023-12-03 - - https://a11y.canada.ca/en/mobility-flexibility-and-body-structure-disabilities/ 2023-12-03 @@ -981,26 +891,6 @@ 2023-12-03 - - https://a11y.canada.ca/en/terms-of-reference/ - 2023-12-03 - - - - https://a11y.canada.ca/en/visual-impairments/ - 2023-12-03 - - - - https://a11y.canada.ca/fr/deficiences-auditives/ - 2023-12-03 - - - - https://a11y.canada.ca/fr/deficiences-visuelles/ - 2023-12-03 - - https://a11y.canada.ca/fr/handicaps-de-mobilite-de-flexibilite-et-de-structure-corporelle/ 2023-12-03 @@ -1016,11 +906,6 @@ 2023-12-03 - - https://a11y.canada.ca/en/the-structure-of-web-content-accessibility-guidelines-wcag-2-1/ - 2023-12-03 - - https://a11y.canada.ca/en/accessible-word-documents-in-microsoft-365/ 2023-12-05 @@ -1036,26 +921,6 @@ 2023-12-20 - - https://a11y.canada.ca/en/canada-school-of-public-service-csps/ - 2023-12-28 - - - - https://a11y.canada.ca/fr/ecole-de-la-fonction-publique-du-canada-efpc/ - 2023-12-28 - - - - https://a11y.canada.ca/en/cart-services-and-sign-language-interpreters/ - 2024-01-17 - - - - https://a11y.canada.ca/en/digital-accessibility-toolkit-project/ - 2024-01-23 - - https://a11y.canada.ca/links/en/accessibility-canada-act/ 2024-02-03 @@ -1166,21 +1031,6 @@ 2024-02-03 - - https://a11y.canada.ca/en/accessibility-testing-101/ - 2024-02-03 - - - - https://a11y.canada.ca/en/alternative-text-and-long-description-best-practices/ - 2024-02-03 - - - - https://a11y.canada.ca/en/audio-description-guidelines/ - 2024-02-03 - - https://a11y.canada.ca/en/designing-for-users-of-screen-readers/ 2024-02-03 @@ -1216,36 +1066,16 @@ 2024-02-03 - - https://a11y.canada.ca/en/personas-with-disabilities-for-inclusive-user-experience-ux-design/ - 2024-02-03 - - - - https://a11y.canada.ca/en/research-on-our-target-audience/ - 2024-02-03 - - https://a11y.canada.ca/en/tips-for-creating-online-courses/ 2024-02-03 - - https://a11y.canada.ca/en/universal-design-for-learning-udl/ - 2024-02-03 - - https://a11y.canada.ca/fr/a-faire-et-a-ne-pas-faire-pour-developper-des-cours-en-ligne/ 2024-02-03 - - https://a11y.canada.ca/fr/conception-universelle-pour-l-apprentissage-cua/ - 2024-02-03 - - https://a11y.canada.ca/fr/conseils-pour-la-conception-de-cours-en-ligne/ 2024-02-03 @@ -1281,26 +1111,11 @@ 2024-02-03 - - https://a11y.canada.ca/fr/recherche-sur-notre-audience/ - 2024-02-03 - - https://a11y.canada.ca/links/fr/norme-sur-l-accessibilite-des-sites-web/ 2024-02-09 - - https://a11y.canada.ca/en/cognitive-disabilities/ - 2024-02-09 - - - - https://a11y.canada.ca/fr/ameliorer-l-accessibilite-des-formulaires/ - 2024-02-09 - - https://a11y.canada.ca/fr/concevoir-des-images-accessibles/ 2024-02-09 @@ -1311,36 +1126,6 @@ 2024-02-09 - - https://a11y.canada.ca/fr/directives-pour-la-description-sonore/ - 2024-02-09 - - - - https://a11y.canada.ca/fr/handicaps-cognitifs/ - 2024-02-09 - - - - https://a11y.canada.ca/fr/la-structure-des-regles-pour-l-accessibilite-des-contenus-web-wcag-2-1/ - 2024-02-09 - - - - https://a11y.canada.ca/fr/liens-utiles/ - 2024-02-09 - - - - https://a11y.canada.ca/fr/liste-de-verification-de-l-accessibilite-des-documents-pdf/ - 2024-02-09 - - - - https://a11y.canada.ca/fr/liste-de-verification-de-la-conformite-des-documents-microsoft/ - 2024-02-09 - - https://a11y.canada.ca/fr/liste-de-verification-pour-l-accessibilite-web/ 2024-02-09 @@ -1401,46 +1186,11 @@ 2024-02-09 - - https://a11y.canada.ca/fr/personas-handicapes-pour-la-conception-d-une-experience-utilisateur-inclusive-eu/ - 2024-02-09 - - https://a11y.canada.ca/fr/projet-de-la-boite-a-outils-de-l-accessibilite-numerique/ 2024-02-09 - - https://a11y.canada.ca/fr/rendre-vos-courriel-accessibles/ - 2024-02-09 - - - - https://a11y.canada.ca/fr/test-d-accessibilite-101/ - 2024-02-09 - - - - https://a11y.canada.ca/fr/texte-alternatif-et-description-longue-bonnes-pratiques/ - 2024-02-09 - - - - https://a11y.canada.ca/en/information-and-communication-technology-ict-accessibility-requirements/ - 2024-02-29 - - - - https://a11y.canada.ca/en/best-practices-for-accessible-virtual-events/ - 2024-03-12 - - - - https://a11y.canada.ca/fr/bonnes-pratiques-pour-les-evenements-virtuels-accessibles/ - 2024-03-12 - - https://a11y.canada.ca/links/_template/ 2024-04-26 @@ -1647,37 +1397,287 @@ - https://a11y.canada.ca/en/additional-resources/ + https://a11y.canada.ca/en/accessible-pdf-documents-in-microsoft-365/ 2024-04-26 - https://a11y.canada.ca/fr/ressources-additionnelles/ - 2024-04-26 + https://a11y.canada.ca/en/making-accessible-emails/ + 2024-04-30 - https://a11y.canada.ca/en/accessible-pdf-documents-in-microsoft-365/ - 2024-04-26 + https://a11y.canada.ca/en/technical-summary-of-the-en-301-549-v3-2-1-2021/ + 2024-05-31 - https://a11y.canada.ca/en/making-accessible-emails/ - 2024-04-30 + https://a11y.canada.ca/fr/resume-technique-de-la-norme-en-301-549-v3-2-1-2021/ + 2024-05-31 + + + + https://a11y.canada.ca/en/access-working-group-awg/ + 2024-06-17 + + + + https://a11y.canada.ca/en/accessibility-testing-101/ + 2024-06-17 + + + + https://a11y.canada.ca/en/additional-resources/ + 2024-06-17 + + + + https://a11y.canada.ca/en/alternative-text-and-long-description-best-practices/ + 2024-06-17 + + + + https://a11y.canada.ca/en/audio-description-guidelines/ + 2024-06-17 + + + + https://a11y.canada.ca/en/auditory-disabilities/ + 2024-06-17 + + + + https://a11y.canada.ca/en/best-practices-for-accessible-virtual-events/ + 2024-06-17 + + + + https://a11y.canada.ca/en/canada-school-of-public-service-csps/ + 2024-06-17 + + + + https://a11y.canada.ca/en/cart-services-and-sign-language-interpreters/ + 2024-06-17 + + + + https://a11y.canada.ca/en/cognitive-disabilities/ + 2024-06-17 + + + + https://a11y.canada.ca/en/digital-accessibility-toolkit-project/ + 2024-06-17 + + + + https://a11y.canada.ca/en/employment-and-social-development-canada-esdc/ + 2024-06-17 + + + + https://a11y.canada.ca/en/find-out-how-to-make-accessible-digital-forms/ + 2024-06-17 + + + + https://a11y.canada.ca/en/information-and-communication-technology-ict-accessibility-requirements/ + 2024-06-17 + + + + https://a11y.canada.ca/en/introduction-to-accessibility-requirements-for-audio-video/ + 2024-06-17 + + + + https://a11y.canada.ca/en/mapping-between-revised-section-508-and-en-301-549-2014-2018-2019-and-2021/ + 2024-06-17 + + + + https://a11y.canada.ca/en/microsoft-document-compliance-checklist/ + 2024-06-17 + + + + https://a11y.canada.ca/en/pdf-accessibility-checklist/ + 2024-06-17 + + + + https://a11y.canada.ca/en/personas-with-disabilities-for-inclusive-user-experience-ux-design/ + 2024-06-17 + + + + https://a11y.canada.ca/en/research-on-our-target-audience/ + 2024-06-17 + + + + https://a11y.canada.ca/en/statistics-canada-statcan/ + 2024-06-17 + + + + https://a11y.canada.ca/en/terms-of-reference/ + 2024-06-17 + + + + https://a11y.canada.ca/en/the-structure-of-web-content-accessibility-guidelines-wcag-2-1/ + 2024-06-17 + + + + https://a11y.canada.ca/en/universal-design-for-learning-udl/ + 2024-06-17 + + + + https://a11y.canada.ca/en/useful-links/ + 2024-06-17 + + + + https://a11y.canada.ca/en/visual-impairments/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/ameliorer-l-accessibilite-des-formulaires/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/bonnes-pratiques-pour-les-evenements-virtuels-accessibles/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/conception-universelle-pour-l-apprentissage-cua/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/deficiences-auditives/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/deficiences-visuelles/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/directives-pour-la-description-sonore/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/ecole-de-la-fonction-publique-du-canada-efpc/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/emploi-et-developpement-social-canada-edsc/ + 2024-06-17 https://a11y.canada.ca/fr/exigences-en-matiere-de-technologies-de-l-information-et-des-communications-tic-accessibles/ - 2024-05-29 + 2024-06-17 - https://a11y.canada.ca/en/technical-summary-of-the-en-301-549-v3-2-1-2021/ - 2024-05-31 + https://a11y.canada.ca/fr/handicaps-cognitifs/ + 2024-06-17 - https://a11y.canada.ca/fr/resume-technique-de-la-norme-en-301-549-v3-2-1-2021/ - 2024-05-31 + https://a11y.canada.ca/fr/introduction-aux-exigences-d-accessibilite-pour-l-audio-video/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/la-structure-des-regles-pour-l-accessibilite-des-contenus-web-wcag-2-1/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/le-groupe-de-travail-sur-l-acces-gta/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/liens-utiles/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/liste-de-verification-de-l-accessibilite-des-documents-pdf/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/liste-de-verification-de-la-conformite-des-documents-microsoft/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/mise-en-correspondance-entre-l-article-508-revise-revised-section-508-et-la-norme-en-301-549-2014-2018-2019-et-2021/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/personas-handicapes-pour-la-conception-d-une-experience-utilisateur-inclusive-eu/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/plateformes-de-reunions-virtuelles-et-fonctionnalites/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/recherche-sur-notre-audience/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/rendre-vos-courriel-accessibles/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/ressources-additionnelles-sur-les-reunions-et-evenements-accessibles/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/ressources-additionnelles/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/services-cart-et-interpretes-en-langue-des-signes-sli/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/statistique-canada-statcan/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/test-d-accessibilite-101/ + 2024-06-17 + + + + https://a11y.canada.ca/fr/texte-alternatif-et-description-longue-bonnes-pratiques/ + 2024-06-17