minutes: UAWG telecon 19 Dec 2013

from http://www.w3.org/2013/12/19-ua-minutes.html

- DRAFT -
User Agent Accessibility Guidelines Working Group Teleconference 19 Dec 2013

See also: IRC log <http://www.w3.org/2013/12/19-ua-irc>
http://www.w3.org/2013/12/19-ua-irc
Attendees
 Present Jim_Allan, [Microsoft], Greg_Lowney, jeanne, Kim_Patch Regrets Eric
Chair jimallan, Kellyford Scribe allanj
Contents

   - Topics <http://www.w3.org/2013/12/19-ua-minutes.html#agenda>
      1. writing tests <http://www.w3.org/2013/12/19-ua-minutes.html#item01>
      2. Wayne comment on
1.4.2<http://www.w3.org/2013/12/19-ua-minutes.html#item02>
      3. 1.4.2 test <http://www.w3.org/2013/12/19-ua-minutes.html#item03>
    - Summary of Action
Items<http://www.w3.org/2013/12/19-ua-minutes.html#ActionSummary>

------------------------------

 <trackbot> Date: 19 December 2013

http://www.w3.org/WAI/EO/wiki/UAAG_review

http://lists.w3.org/Archives/Public/public-uaag2-comments/2013Dec/0000.html

open item 1

js: request that responders commit by Jan 8 and let us know when UAWG can
expect the report
... then start calling and writing for meeting the deadline

<jeanne> real player

<jeanne> quicktime

<jeanne> jwplayer

<jeanne> media players to contact.

www.longtailvideo.com

<jeanne> windows media player

itunes

<scribe> scribe: allanj

Resolution: UAWG to agree to keep the comment period open through January.
... UAWG agrees to keep the comment period open through January.

close item 1

eo comments http://www.w3.org/WAI/EO/wiki/UAAG_review

Wayne's comments
http://lists.w3.org/Archives/Public/public-uaag2-comments/2013Dec/0000.html

open item 2
writing tests

gl: tried to write a test and came up with lots of questions, the SC seemed
clear.

ja: agrees

kp: this happens many times with writing tests, you are looking at the SC
in a different context, which changes the thinking

js: this happened in other guidelines - so rule is that tests written
before CR

kp: if person writing the test comes up with question(s), then bring to
group to resolve questions, rewrite SC, etc. as necessary.
... with comments, then things will change more, and affect the tests

js: need to incorporate tests into the document, so we can't change an SC
without changing the test at the same time.
... if we edit an SC because of comments then we write the test then also.
Wayne comment on 1.4.2

<Greg> Original:

<Greg> 1.4.2 Text Size, Color and Font (by Element): The user can set all
of the following characteristics of visually rendered text content for text
element types including at least headings and input fields:(Level AA)

<Greg> Text size

<Greg> Text color and background color, choosing from all platform color
options

<Greg> Font family, choosing from all platform fonts

<Greg> With Wayne's suggested change:

<Greg> 1.4.2 Text Size, Color and Font (by Element): The user can set all
of the following characteristics of visually rendered text content for text
element types including at least headings, input fields, and links:(Level
AA)

<Greg> Also, should add a space before (Level AA).

<Greg> Thus:

<Greg> 1.4.2 Text Size, Color and Font (by Element): The user can set all
of the following characteristics of visually rendered text content for text
element types including at least headings, input fields, and links: (Level
AA)

ja, kp, gl, js all ok with the addition.

<Greg> It looks like we should (a) add "links that have not been visited
recently" to 1.3.1 and (b) add "Font style (underline, bold, italics)" to
1.3.2.

<Greg> That will take care of letting people adjust the underlining of
links.

js: can't we just say links

gl: but html we have visited and not visited

js: but if you can customize links then you can customize links

<Greg> As Jeanne points out, we don't want to make any PDF readers fail
because they don't distinguish between visited and unvisited links. Thus we
could change 1.3.1 "Recently visited links" to something like "Recently
visited links, if the user agent distinguishes them from unvisited links."

<Greg> On the other hand, I agree with Jim that we should enable to user to
change underlining of links (visited and unvisited).

1.4.2 Text Size, Color and Font (by Element): The user can set all of the
following characteristics of visually rendered text content for text
element types including at least headings, input fields, and links: (Level
AA)

Text style (underline, italic, bold)

Text size

Text color and background color, choosing from all platform color options

Font family, choosing from all platform fonts

<Greg> We may want to address what is meant by "text size", particularly
absolute vs. relative sizes.

<Greg> We could add "(e.g. 15pt, or 'larger')"

ja: we should reference CSS about text size

<scribe> *ACTION:* jeanne to update the 1.4.2 to be 1.4.2 Text Size, Color
and Font (by Element): The user can set all of the following
characteristics of visually rendered text content for text element types
including at least headings, input fields, and links: (Level AA) [recorded
in http://www.w3.org/2013/12/19-ua-minutes.html#action01]

<trackbot> Created ACTION-932 - Update the 1.4.2 to be 1.4.2 text size,
color and font (by element): the user can set all of the following
characteristics of visually rendered text content for text element types
including at least headings, input fields, and links: (level aa) [on Jeanne
F Spellman - due 2013-12-26].

* Text style (underline, italic, bold)

* Text size

* Text color and background color, choosing from all platform color options

* Font family, choosing from all platform fonts
1.4.2 test

<jeanne> trackbot, close action-932

<trackbot> Closed action-932.

<jeanne> Test assertion 01: The user can set the text size of headings
elements

<jeanne> 1. If the content does not have headings, choose [NOT APPLICABLE].

<jeanne> 2. Load the accessible test content file. Using the user agent
user interface, change the text size of the headings.

<jeanne> 3. If the heading changes as you set in Step 2, choose [PASS]

<jeanne> ... otherwise, select [FAIL]

<jeanne> Note that the above test is for 1.4.2

<Greg> The problem with that is that you could comply by changing the size
of all text.

<jeanne> 2. Load the accessible test content file. Using the user agent
user interface, change ONLY the text size of the headings.

<Greg> You may want to note that they may have to adjust the sizes of
different heading levels separately.

<Greg> And they need to be able to ensure that headings of different levels
have different sizes.

<Greg> (Thus making them visually distinguishable.)

<jeanne> 2. Load the accessible test content file. Using the user agent
user interface OR a user stylesheet, change ONLY the text size of the
heading or a level of heading. Most technologies support multiple levels of
headings.

<Greg> That means they need to be able to either (a) adjust the relative
sizes of all levels of headings (e.g. making all of them proportionately
larger or smaller), or (b) set absolute or relative sizes of individual
heading levels.

<jeanne> 3. If there is only one heading level and that level changes as
instructed, choose [PASS].

<Greg> If we control the test documents we can make sure they have multiple
levels of headings.
 Summary of Action Items *[NEW]* *ACTION:* jeanne to update the 1.4.2 to be
1.4.2 Text Size, Color and Font (by Element): The user can set all of the
following characteristics of visually rendered text content for text
element types including at least headings, input fields, and links: (Level
AA) [recorded in http://www.w3.org/2013/12/19-ua-minutes.html#action01]

[End of minutes]
------------------------------
 Minutes formatted by David Booth's
scribe.perl<http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm>version
1.138 (CVS
log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2013-12-19 20:02:10 $
-- 
Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964