- From: Ramón Corominas <rcorominas@technosite.es>
- Date: Mon, 25 Nov 2013 13:43:37 +0000
- To: stefan.schnabel@sap.com
- CC: Marco Zehe <mzehe@mozilla.com>, Steve Faulkner <faulkner.steve@gmail.com>, David MacDonald <david100@sympatico.ca>, HTML Accessibility Task Force <public-html-a11y@w3.org>, WCAG <w3c-wai-gl@w3.org>, "kirsten@can-adapt.com" <kirsten@can-adapt.com>
Hello again, Comments are inline: Stefan wrote: > No matter what property will be used, what’s been mapped into the > platform accessibility api by the respective user agent matters, IMHO. Are the text alternatives only for screen readers? Are they only for screen readers that support WAI-ARIA? Is the screen reader the only consideration of the guideline 1.1 when it talks about text that "can be changed into other forms people need". I know a low vision user that sometimes disables images to read the descriptions because he finds difficult to identify certain icons. The alt text is also included when you use Ctrl+C to copy the contents of a web page, so it can also be read if the user copies the text into another tool (for example, a TTS application that is not a screen reader). > With other words, when e.g. the MSAA accessible name (get_accName) > property is satisfied, all good, no matter WHO or WHAT does that. Of course I assume that MSAA is just an example, the technique should be also accessibility supported on other non-Windows platforms. In my opinion, every technique should include an "accessibility support" section that includes only the environments where the technique has been tested and verified to be valid. Regards, Ramón.
Received on Monday, 25 November 2013 19:23:30 UTC