- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Fri, 15 Mar 2013 08:18:19 -0500
- To: James Craig <jcraig@apple.com>
- Cc: Janina Sajka <janina@rednote.net>, Independent User Interface Task Force <public-indie-ui@w3.org>
- Message-ID: <OFB54DF121.972AD242-ON86257B2F.0048D9FD-86257B2F.0049173D@us.ibm.com>
Rich Schwerdtfeger James Craig <jcraig@apple.com> wrote on 03/14/2013 06:43:59 PM: > From: James Craig <jcraig@apple.com> > To: Richard Schwerdtfeger/Austin/IBM@IBMUS, > Cc: Janina Sajka <janina@rednote.net>, Independent User Interface > Task Force <public-indie-ui@w3.org> > Date: 03/14/2013 06:44 PM > Subject: Re: Wednesdays Telecon; Call for agenda > > On Mar 14, 2013, at 4:22 PM, Richard Schwerdtfeger <schwer@us.ibm.com> wrote: > > > ScreenReaderActive, ScreenReaderName, ScreenReaderVersion should > also fall under the privacy discussion. > > They are. That's the ScreenReaderKeys dictionary. > > > Do we want to address whitespace between characters and lines in > v1.0? Andy and I did not include this in our proposal as this is > considered a more advanced feature. A feature would be required to > allow adjust the spacing both vertically and horizontally. We have > this feature in AccessForAll extended preferences vs. core. > > Settings for default letter-spacing and line-spacing seem reasonable > to me. These can also be "set" in most browsers by way of a user > style sheet, so implementation should be possible in a few ways. > > Added ACTION-44 > https://www.w3.org/WAI/IndieUI/track/actions/44 > > > Also, keys may be an issue as mobile devices may not have keys. We > should decide how we are going to address this. > > I'm not sure what this means. I don't see why the mobile device > context would have any bearing on whether a browser can use key/ > value pairs for settings. > Sorry, my confusion. I thought you meant keyboard keys vs. key/value pairs. > > I am also not sure this is a 1.0 item but one really big problem > is that content providers are pushing down bitmaps of Math vs. > MathML. Unlike bitmaps, MathML can be processed and read by > assistive technologies like MathPlayer plus an AT. Should we have a > setting to ask that content providers deliver MathML vs. bitmaps of > Math? I am ok with addressing this beyond 1.0 but note that it is a > big problem. One reason this has been there has been for older > browsers not being able to render MathML or because a math render > like MathJax has not been provided. The browser should know. Users > with Cognitive impairments need Math to be spoken verbally in > chunks. If the content provider sends down a bitmap in all > situations just to play it safe then then nothing can be done to > assist the user. > > While I agree that this is a problem, MathML is outside the scope of IndieUI. > Well, it is a user context issue. Do you know of another way to convey that the browser tells a web app that it supports MathML? > James >
Received on Friday, 15 March 2013 13:19:19 UTC