One other important issue in web applications is whether something should be a button or a link. Most web applications use these interchangeably, for example in a web based editor the "update" function is a button, but the "cancel" function is a link. This distinction seems minor to people who can see the visual rendering, but for screen reader users the difference is huge. Screen readers have separate functions to navigate form controls and links. So they could easily miss the cancel function when it is a link, instead of a button. Jon From: Loretta Guarino Reid [mailto:lorettaguarino@google.com] Sent: Tuesday, November 29, 2011 9:21 AM To: adam solomon Cc: WCAG Subject: Re: link text 2.4.4 This would be covered by 1.1.1: If non-text content is a control or accepts user input, then it has a name<http://www.w3.org/TR/2008/REC-WCAG20-20081211/#namedef> that describes its purpose. (Refer to Guideline 4.1<http://www.w3.org/TR/2008/REC-WCAG20-20081211/#ensure-compat> for additional requirements for controls and content that accepts user input.) On Tue, Nov 29, 2011 at 4:39 AM, adam solomon <adam.solomon2@gmail.com<mailto:adam.solomon2@gmail.com>> wrote: Hi everyone Does 2.4.4 require there to be link text? Or, in cases where there is no link text (for instance a background image of text), a descriptive title attribute would suffice, since screen readers (at least Jaws that I know for sure) will read the title attribute when no text is present?
Received on Tuesday, 29 November 2011 15:28:18 UTC