From 1c22510a35ed22c59fd6bec1669fac8edfcd850d Mon Sep 17 00:00:00 2001 From: Matt King Date: Tue, 2 Jul 2019 20:10:28 -0700 Subject: [PATCH] Intro paragraph: additional editorial simplification based on feedback from @LJWatson in issue #1050. --- aria-practices.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/aria-practices.html b/aria-practices.html index c1c9994a62..be9f9698a2 100644 --- a/aria-practices.html +++ b/aria-practices.html @@ -3702,9 +3702,9 @@

Providing Accessible Names and Descriptions

Providing elements with accessible names, and where appropriate, accessible descriptions is one of the most important responsibilities authors have when developing accessible web experiences. - While doing so is straightforward for most elements, technical mistakes that can have devastating impacts on users of assistive technologies are easy to make and unfortunately common. - To help authors provide effective and reliable accessible names and descriptions, this section explains their purpose, when authors need to provide them, how browsers assemble them, and rules for coding and composing them. - It also provides guidance for effectively employing the following naming and describing techniques and WAI-ARIA properties: + While doing so is straightforward for most elements, technical mistakes that can completely block users of assistive technologies are easy to make and unfortunately common. + To help authors effectively provide accessible names and descriptions, this section explains their purpose, when authors need to provide them, how browsers assemble them, and rules for coding and composing them. + It also guides authors in the use of the following naming and describing techniques and WAI-ARIA properties: