E-mail List Archives

Re: Accessible GIS coordinates

for

From: Jonathan Metz
Date: Oct 31, 2013 11:38AM


Couldn¹t this be solved by using ActualText, since they are unambiguous as
Olaf points out.

>>No, not really. This should fall on the end user's system to read the
necessary characters. It should be apparent to most readers what the
numbers are, even if the characters aren't being read. And they could
read character-by-character if need be. I wouldn't worry about doing
anything special here.

On 10/30/13 7:54 PM, "Jared Smith" < <EMAIL REMOVED> > wrote:

>
>No, not really. This should fall on the end user's system to read the
>necessary characters. It should be apparent to most readers what the
>numbers are, even if the characters aren't being read. And they could
>read character-by-character if need be. I wouldn't worry about doing
>anything special here.


I would argue that only readers who may have seen coordinates would know
what these symbols represent. Users of screen readers for non-visual
related disabilities (for example, those with a CI) might require a more
specific explanation of the usage of the symbols.

Thanks,
Jon



On 10/31/13 10:15 AM, "Jim Allan" < <EMAIL REMOVED> > wrote:

>did a test with JAWS 14
>
>Degrees, minutes and seconds: 41° 24' 12.1674", 2° 10' 26.508"
>reading by word (ctrl right arrow)-
>"degree" spoken, minutes read as "apostrophe", seconds read as "quote".
>reading by line "degree" spoken, minutes/apostrophe not spoken, "quote"
>spoken.
>
>Decimal degrees: 41.40338, 2.17403 was the fine no matter what mode the
>reading happened. Unambiguous all the time.
>
>Degrees and decimal minutes: 41 24.2028, 2 10.4418 was a slight pause
>between the degrees and minutes. it read as forty-one twenty-four point
>two
>oh two eight.
>
>to me the decimal degrees are the cleanest and read the same way all the
>time.
>
>
>On Thu, Oct 31, 2013 at 3:13 AM, Olaf Drümmer < <EMAIL REMOVED> > wrote:
>
>> Hi Bevi,
>>
>>
>> Am 31 Oct 2013 um 04:46 schrieb Chagnon | PubCom < <EMAIL REMOVED> >:
>>
>> > I'm often stumped why
>> > today's screen reader software doesn't recognize or voice most of the
>> > characters on a font.
>>
>> maybe you should let the vendors low about thisŠ.
>>
>> A while ago the NVDA team told they'd voice most of the important
>>Unicode
>> codepoints but that they don't see any value in doing this for each and
>> every code point. It seems prime and double prime might be among the
>>less
>> important ones. As the NVDA guys are very open minded - if they begin
>>to
>> hear they should include support fore more of these code points,
>>especially
>> including prime and double prime for GIS coordinates etc., they might
>> simply add it.
>>
>>
>> Olaf
>>
>> >> >> >>
>
>
>
>--
>Jim Allan, Accessibility Coordinator & Webmaster
>Texas School for the Blind and Visually Impaired
>1100 W. 45th St., Austin, Texas 78756
>voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/
>"We shape our tools and thereafter our tools shape us." McLuhan, 1964
>>>