E-mail List Archives
Thread: Re: Foreign:Re: Screen readers and Arabic
Number of posts in this thread: 5 (In chronological order)
From: Moore, Michael
Date: Tue, Sep 23 2008 10:10AM
Subject: Re: Foreign:Re: Screen readers and Arabic
No previous message | Next message →
JAWS does not include Arabic by default, but an Arabic language pack has
been available from Freedom Scientific since JAWS 6.
Mike
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Joshue O
Connor
Sent: Tuesday, September 23, 2008 10:42 AM
To: WebAIM Discussion List
Subject: Foreign:Re: [WebAIM] Screen readers and Arabic
Hi all,
Does anyone know if JAWS can be configured to read Arabic?
I know that Dolphins HAL can read Arabic but for a JAWS user what are
the options? [1]
Cheers
Josh
[1] http://www.yourdolphin.com/newsitem.asp?id=61
********************************************************************
NOTICE: The information contained in this email and any attachments
is confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of
the content of it or of any attachment; you are requested to notify
the sender immediately of your receipt of the email and then to
delete it and any attachments from your system.
NCBI endeavours to ensure that emails and any attachments generated
by its staff are free from viruses or other contaminants. However,
it cannot accept any responsibility for any such which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent the views of NCBI
********************************************************************
From: Joshue O Connor
Date: Tue, Sep 23 2008 10:20AM
Subject: Re: Foreign:Re: Screen readers and Arabic
← Previous message | Next message →
Moore, Michael wrote:
> JAWS does not include Arabic by default, but an Arabic language pack has
> been available from Freedom Scientific since JAWS 6.
Thanks for that Mike.
Cheers
Josh
********************************************************************
NOTICE: The information contained in this email and any attachments
is confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of
the content of it or of any attachment; you are requested to notify
the sender immediately of your receipt of the email and then to
delete it and any attachments from your system.
NCBI endeavours to ensure that emails and any attachments generated
by its staff are free from viruses or other contaminants. However,
it cannot accept any responsibility for any such which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent the views of NCBI
********************************************************************
From: Angela French
Date: Wed, Nov 12 2008 2:35PM
Subject: screen readers and empty paragraphs
← Previous message | Next message →
Can anyone tell me if there are any ramifications (for screen readers)
for empty paragraphs tags?
For example: <p></p>
Thank you!
Angela French
Internet Specialist
State Board for Community & Technical Colleges
360-704-4316
http://www.checkoutacollege.com
http://www.sbctc.ctc.edu
From: Jukka K. Korpela
Date: Wed, Nov 12 2008 2:50PM
Subject: Re: screen readers and empty paragraphs
← Previous message | Next message →
Angela French wrote:
> Can anyone tell me if there are any ramifications (for screen readers)
> for empty paragraphs tags?
You mean empty paragraph _elements_.
According to HTML specifications,
1) Authors should not use empty paragraphs.
2) User agents should ignore them.
But we need to add:
3) User agents don't always ignore them. Visual user agents may leave extra
empty space. I would not be surprised if some aural user agents treated them
as causing some extra pause.
The conclusion is that you should not use empty paragraphs. But if existing
pages contain them, you should probably spend your time more constructively
than removing empty paragraphs. Beware that they may have been inserted on
purpose, for spacing, and they may have that effect, so layout might get
changed. It is of course possible to create spacing using CSS, but cleaning
up existing pages is usually waste of time, and risky.
Actually it is probably much more common to have a paragraph that contains a
no-break space only, <p> </p>. It tends to cause spacing worth of one
empty line. It is technically not empty, so in principle HTML specs don't
say anything specific about them, but the spirit there is clearly that
spacing should be achieved using style sheets, not trickery with dummy HTML
elements.
> For example: <p></p>
Or for example the paragraph element in
<p>
<h2>Hello world</h2>
The old, 1990-style habit of using <p> as a paragraph _terminator_ often
creates unintended empty paragraphs.
--
Yucca, http://www.cs.tut.fi/~jkorpela/
From: Moore, Michael
Date: Wed, Nov 12 2008 3:00PM
Subject: Re: screen readers and empty paragraphs
← Previous message | No next message
I agree with Yucca, but I did try a short contrived experiment using
JAWS 9 and IE7.
I found that JAWS would report a "blank" for the first occurrence in a
series of <p> </p>. JAWS completely ignored <p></p>. The
interesting consequence of this was that if two headings were separated
by <p></p> or a series of <p></p> then JAWS would read the headings in a
continuous stream when reading by sentence, alt+down arrow, or
paragraph, cntrl+down arrow. Normal behavior would have been to stop
after each heading. Reading was exactly as expected when reading by
line, word, letter, or in say all mode.
Mike
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jukka K.
Korpela
Sent: Wednesday, November 12, 2008 3:46 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] screen readers and empty paragraphs
Angela French wrote:
> Can anyone tell me if there are any ramifications (for screen readers)
> for empty paragraphs tags?
You mean empty paragraph _elements_.
According to HTML specifications,
1) Authors should not use empty paragraphs.
2) User agents should ignore them.
But we need to add:
3) User agents don't always ignore them. Visual user agents may leave
extra
empty space. I would not be surprised if some aural user agents treated
them
as causing some extra pause.
The conclusion is that you should not use empty paragraphs. But if
existing
pages contain them, you should probably spend your time more
constructively
than removing empty paragraphs. Beware that they may have been inserted
on
purpose, for spacing, and they may have that effect, so layout might get
changed. It is of course possible to create spacing using CSS, but
cleaning
up existing pages is usually waste of time, and risky.
Actually it is probably much more common to have a paragraph that
contains a
no-break space only, <p> </p>. It tends to cause spacing worth of
one
empty line. It is technically not empty, so in principle HTML specs
don't
say anything specific about them, but the spirit there is clearly that
spacing should be achieved using style sheets, not trickery with dummy
HTML
elements.
> For example: <p></p>
Or for example the paragraph element in
<p>
<h2>Hello world</h2>
The old, 1990-style habit of using <p> as a paragraph _terminator_ often
creates unintended empty paragraphs.
--
Yucca, http://www.cs.tut.fi/~jkorpela/