RE: Re: ACTION-1497 - Proposal for accessible description glossary definition

Additionally, we might want to look at the concept of ‘layered help’. The first/top instance being very simple, with a link to a somewhat more detailed description, and that with a link to an even more detailed description.

 

A somewhat lame Example would be:

1st layer (using the accessible description): “Help with this Form” then a “Get more details” link.

2nd layer (using ?, maybe also using the accessible description): “Please provide your country code, area code and phone number” then a “Get more details” link.

3rd (using ?, maybe also using the accessible description):  “Please provide your 3 digit country code (such as 0O1 for the US), you 3 digit area code (such as 703 for Virginia) and 7 digit phone number” in this fashion…...

 

 

* katie *

 

Katie Haritos-Shea 
Senior Accessibility SME (WCAG/Section 508/ADA/AODA)

 

Cell: 703-371-5545 |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545

 

From: lisa.seeman [mailto:lisa.seeman@zoho.com] 
Sent: Monday, September 22, 2014 12:27 AM
To: public-cognitive-a11y-tf
Subject: Fwd: Re: ACTION-1497 - Proposal for accessible description glossary definition

 

Hi folks

I am wondering if we should be defining what a help text string would look like for COGA users.

What are the guidelines for whiting an interface help text / tool tip

All the best

Lisa Seeman

Athena ICT Accessibility Projects  <http://accessibility.athena-ict.com> 
LinkedIn <http://il.linkedin.com/in/lisaseeman/> , Twitter <https://twitter.com/SeemanLisa> 



 

 


============ Forwarded message ============
>From : James Craig<jcraig@apple.com <mailto:jcraig@apple.com> >
To : "Richard Schwerdtfeger" <schwer@us.ibm.com <mailto:schwer@us.ibm.com> >
Cc : "PF" <public-pfwg@w3.org <mailto:public-pfwg@w3.org> >
Date : Sat, 20 Sep 2014 05:33:37 +0300
Subject : Re: ACTION-1497 - Proposal for accessible description glossary definition
============ Forwarded message ============

 

 

On Sep 19, 2014, at 3:41 PM, Richard Schwerdtfeger <schwer@us.ibm.com <mailto:schwer@us.ibm.com> > wrote:

 

Accessible Description

    The accessible description provides help information about an interface element or how it is used in the form of a string.

Probably no need for "in the form of a string." 



Each platform accessibility API provides an accessible description property. 

This is incorrect. I'd just remove the sentence.

The value of the accessible description may be derived from a reference to content within a web page (visible or invisible) that is converted to a string. In some host languages the reference to the accessible description may be implied such as through the use of the <desc> element in SVG. 

Here's my draft two based on Rich's original:

The accessible description provides help information about an interface element or about how it is used. The value of the accessible description may be derived from a reference to visible or invisible content within a web page, or the accessible description may be defined by host language features, such as the <desc> element in SVG.