Re: Wednesdays Telecon; Call for agenda

ScreenReaderActive, ScreenReaderName, ScreenReaderVersion should also fall
under the privacy discussion.

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.

Also, keys may be an issue as mobile devices may not have keys. We should
decide how we are going to address this.

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.

Rich


Rich Schwerdtfeger



From: James Craig <jcraig@apple.com>
To: Janina Sajka <janina@rednote.net>,
Cc: Independent User Interface Task Force <public-indie-ui@w3.org>
Date: 03/14/2013 06:02 PM
Subject: Re: Wednesdays Telecon; Call for agenda



On Mar 14, 2013, at 6:15 AM, Janina Sajka <janina@rednote.net> wrote:

      Please provide any agenda items you would like included on our
      upcoming
      teleconference this coming Wednesday 20 March at 21:00Z.

Three agenda items so far.

   1. Summary of User Context edits including new settings keys: fontSize,
      fontSizeMinimum, invertColors, pointOfRegard, screenReaderActive,
      screenReaderName, screenReaderVersion, signLanguage, subtitle,
      subtitleLanguages, subtitleType, transcript. Should we support the
      additional FCC settings for subtitle colors/fonts/etc? What others do
      we need?

   2. Summary/brainstorm of current ideas regarding UA privacy policy
      settings by settings group dictionaries: GeneralKeys,
      AuditoryAlternativeKeys, and ScreenReaderKeys, probably more… Access
      restriction to first from group, by domain, by access control.
      Potentially also limiting initial access to user-initiated event
      rather than something like onload.

   3. Brainstorm alternate names for the Point-of-Regard concept.