Dear Ajeesh Interesting question, I shall answer inline in the trailing mail. My comments are indicated <hk> . Harish Kotian
-----Original Message----- From: AccessIndia [mailto:accessindia-boun...@accessindia.org.in] On Behalf Of Ajeesh Thomas Sent: 24 March 2015 19:20 To: accessindia Subject: [AI] Technical facts about screen reader Hi all, I am looking for in depth Technical details about screen reader's, not getting a proper stuff, could you please help me? 1. How Technically screen reader works? <hk> Every application is a container of smaller objects running under it. Whenever the focus falls on an object, the screen reader becomes aware of it by a trigger mechanism, the screen reader in turn looks for the text which is exposed and dispatches this text to the TTS engine for speech output similarly, it also dispatches the info to the Braille display engine. What is dispatched to the later 2 engines would not necessarily be the same. 2. Facts about TTS, Vocaliser,Synthisiser etc , and what is the difference ?? <hk> Broadly, there are 2 category of TTS engine. 1) Phonymn based and 2) concatenation based Phonymn based TTS would not be pleasant to hear but it is more versatile and lightweight 3. The main Screen reader accessibility barriers in various OS 's. <HK> There are various contributory factors, viz. how much info is exposed by the object and the level of accessibility factored in the design stage. By and large, accessibility is far better integrated in the core design of the Linux OS compared to that of Windows implementation. The second important factor the level of efforts by the screen readers level of commitment and resources. This is visible in the level of accessibility by different screen reader. 4. Microsoft Active Accessibility and it's connection with screen reader's so on <hk> MSAA is the platform through which Microsoft has windows object exposes info to the objects running under its hood. If all developers adhere totally to this standards, then, we shall face no issues. However, the reality is far different. Microsoft themselves disdainfully breach it royally, then we can't expect much from others. Basically it is the lack of awareness on part of the developer community about the understanding of accessibility technology. please share the knowledge /links ... Thanks in advance, -- " Have a fantastic day "ahead" Ajeesh Thomas, Accessibility Test Engineer, IBM India, Banglore, Mob: 0 81233 81222,Lan: 04742586821, Office: 04443423000 skipe: ajeeshthomas86 "waves are inspiring not due to they rise and fall, because they never fail to rise again" Register at the dedicated AccessIndia list for discussing accessibility of mobile phones / Tabs on: http://mail.accessindia.org.in/mailman/listinfo/mobile.accessindia_accessindia.org.in Search for old postings at: http://www.mail-archive.com/accessindia@accessindia.org.in/ To unsubscribe send a message to accessindia-requ...@accessindia.org.in with the subject unsubscribe. To change your subscription to digest mode or make any other changes, please visit the list home page at http://accessindia.org.in/mailman/listinfo/accessindia_accessindia.org.in Disclaimer: 1. Contents of the mails, factual, or otherwise, reflect the thinking of the person sending the mail and AI in no way relates itself to its veracity; 2. AI cannot be held liable for any commission/omission based on the mails sent through this mailing list.. Caution: The Reserve Bank of India never sends mails, SMSs or makes calls asking for personal information such as your bank account details, passwords, etc. It never keeps or offers funds to anyone. Please do not respond in any manner to such offers, however official or attractive they may look. Notice: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this email by error, please notify us by return e-mail or telephone and immediately and permanently delete the message and any attachments. The recipient should check this email and any attachments for the presence of viruses. The Reserve Bank of India accepts no liability for any damage caused by any virus transmitted by this email. Register at the dedicated AccessIndia list for discussing accessibility of mobile phones / Tabs on: http://mail.accessindia.org.in/mailman/listinfo/mobile.accessindia_accessindia.org.in Search for old postings at: http://www.mail-archive.com/accessindia@accessindia.org.in/ To unsubscribe send a message to accessindia-requ...@accessindia.org.in with the subject unsubscribe. To change your subscription to digest mode or make any other changes, please visit the list home page at http://accessindia.org.in/mailman/listinfo/accessindia_accessindia.org.in Disclaimer: 1. Contents of the mails, factual, or otherwise, reflect the thinking of the person sending the mail and AI in no way relates itself to its veracity; 2. AI cannot be held liable for any commission/omission based on the mails sent through this mailing list..
