W3C

- DRAFT -

User Agent Accessibility Guidelines Working Group Teleconference

24 May 2012

See also: IRC log

Attendees

Present
sharper, Kim_Patch, Jeanne, Greg_Lowney, kford, [Microsoft]
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Harper_Simon

Contents


<trackbot> Date: 24 May 2012

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0040.html,

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0042.html

<kford> Action-467 https://www.w3.org/WAI/UA/tracker/actions/467

<jeanne> Latest Editor's Draft -> http://www.w3.org/WAI/UA/2012/ED-UAAG20-20120517/

Face to Face planning, go over proposed agenda

<scribe> scribe: Harper_Simon

<scribe> ScribeNick: sharper

KF: F2F in less than 2 weeks - trying to get the document done -solid at IDing actions which are left
... Current think - work - 1.5h divide actions and finish for each section of the document - assignment doesn't matter - 45 minutes to integrate and resolve. iterate this.
... Goal is to get these done.

JS: Cycle back and look at the levels for any section that is done.

KF: write, review, set level - lets get this done before we go home.
... 08:30 start - show up 08:00-08:30

finalize 1.7

http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0040.html,

http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0042.html

<jeanne> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0073.html

JS: repeats the text as per the e-mail link above

<jeanne> 1.7.2 Apply User Stylesheets:

<jeanne> The user can turn on the use of user stylesheets (Level A)

<jeanne> (a) all pages on specified web sites, or

<jeanne> (b) all pages.

JS: clarifies that all pages on specific website can be turned on, GL: confirms this is OK

<jeanne> The user can apply user stylesheets.

GL/JS: general wordsmithing

<jeanne> The user can apply or disable user stylesheets

GL: can have multiple user style sheets - can clarify in the intent
... need to specify different CSS for different websites
... is point (a) useful at all in this case - is this really good enough.
... turning on and off user style sheets may be cumbersome

JS: agreed, but not sure this is level A
... which more important - a at A, or different and a different level
... lets make sure this is in the intent

JS/GL: running through scenarios of use

KF: apply or disable = enable or disable?

<jeanne> The user can enable or disable user stylesheets for (Level A)

The user can enable or disable the use of user stylesheets (Level A): (a) all pages on specified web sites; or (b) all pages.

<KimPatch> off for about 10

RESOLUTION: Level 1.7.2 as suggested by above , but add to intent to recommend different stylesheets load for different website.

he user can enable or disable user stylestheets for (Level A)

JS: the IER for these are combined

http://www.w3.org/WAI/UA/2012/ED-IMPLEMENTING-UAAG20-20120517/

Intent of Success Criterion 1.7.1, 1.7.2 & 1.7.3: are combined

<jeanne> Since different web sites may require different style changes to be readable, it is recommended that user agents provide a feature that lets the user specify which stylesheet should be automatically applied to different web pages as they are loaded.

<Greg> Something like "It is recommended that user agents provide a feature that lets the user specify which stylesheets should be automatically applied to different web pages as they are loaded (e.g. based on a list of domain names or URL templates)."

GL: adding - it is recommended that UAs provide a feature that lets the user specify which CSS should be automatically applied to different web pages as they are loaded - eg based on a list of domains or URL templates.

<jeanne> 1.7.3 Author Style Sheets:

<jeanne> The user can turn off the use of author stylesheet on the current page (Level A)

JS: reads JA: remove the current a and b bullets

<jeanne> The user can turn off the use of author stylesheets on the current page (Level A)

JS: stylesheet should be plural

<Greg> I'd prefer "The user can turn off the use of author stylesheets on the current page or the current viewport".

<Greg> Either globally or for the current viewport.

RESOLUTION: The user can disable the use of author stylesheets on the current page (Level A)

topic 1.7.4 Save copies of stylesheets

current: The user can save copies of the stylesheets referenced by the current page, so that they can edit and load them as user (Level AA)

JS channels JA: proposes AAA - no current functionality - and only some UAs can do this with an extension.

JS: thinks it's OK at AA - KP agrees

GL: eg in FF puts copies of all CSS into a folder - upon save

SH: safari - does this via a WebArchive

<jeanne> JS: I remember Wayne saying that Safari had the best interface for stylesheet management

RESOLUTION: Stay at AA

Links to stylish, mouseless browsing, greasemonkey etc

<Greg> Issue: Add SC recommending feature to automatically apply different scripts to different pages when they load (e.g. Greasemonkey). Product-2

<trackbot> Created ISSUE-92 - Add SC recommending feature to automatically apply different scripts to different pages when they load (e.g. Greasemonkey). Product-2 ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/92/edit .

JS: No IER for 1.7.4

<kford> ACTION: KFord to write IER for 1.7.4 [recorded in http://www.w3.org/2012/05/24-ua-minutes.html#action01]

<trackbot> Created ACTION-731 - Write IER for 1.7.4 [on Kelly Ford - due 2012-05-31].

<scribe> ACTION: kford to write IER for 1.7.4 [recorded in http://www.w3.org/2012/05/24-ua-minutes.html#action02]

<trackbot> Created ACTION-732 - Write IER for 1.7.4 [on Kelly Ford - due 2012-05-31].

<kford> action-732 close

<jeanne> close action-732

<trackbot> ACTION-732 Write IER for 1.7.4 closed

Action-631 UAAG:next?

<KimPatch> 1.8.m Webpage bookmarks

<KimPatch> The user can mark items in a webpage, then navigate back to marked items using keyboard shortcuts. The user can specify whether a navigation mark disappears after a session or is persistent across sessions.

<KimPatch> Intent of Success Criterion 1.8.m:

<KimPatch> This success criterion is crucial for users who have trouble navigating a webpage. Speech users, users who have memory problems, and small-screen users, including blind users using mobile technology may be able to initially go from one area of a webpage to another area, but may have trouble frequently repeating the action. The ability to mark areas of the page allows these types of users to...

<KimPatch> ...participate on a level playing field with users who have less trouble navigating.

<KimPatch> Examples of Success Criterion 1.8.m:

<KimPatch> Jamie is a quadriplegic who uses speech recognition. She is a professor who often reads long documents online and often finds herself comparing different portions of the same document. It is tedious carrying out multiple scrolling commands by speech every time she needs to change to another portion of the document. She sets several bookmarks instead. This allows her to instantly jump among...

<KimPatch> ...sections, eliminating the time and effort penalties she usually has to pay for slow scrolling.

<KimPatch> Julie has memory problems. She finds it difficult to remember key points from a document she has just read. She uses bookmarks to mark important points she needs to read again. Without the ability to bookmark she has a catch-22 problem -- she won’t remember what she needs to read multiple times in order to do so.

<KimPatch> Justin is blind and occasionally travels to unfamiliar places for work. He sometimes uses an iPhone to orient himself within a map of the building he’s in. Once he’s found a key place on the map -- like the room where a conference session is held, or the bathroom -- he bookmarks it to build a map of useful places. This makes navigation easier the second time around. He sets the marks to be...

<KimPatch> ...persistent across sessions so next time he visits he won't have to repeat his work.

<KimPatch> Mary has repetitive strain injuries that make it painful to use a mouse. She uses an elaborate web application to correct papers. After putting a comment in a comment field she has to scroll all the way to the bottom of the document to enter the comment. The bookmarks make even this badly designed application something she can use successfully without hurting herself.

<KimPatch> --

GL: use modality independent language
... too fcused on keyboard

KP: changes on the fly

KF: this functionality and scenarios are the way they work on screen -readers and AT.

<KimPatch> The user can mark items in a webpage, then navigate back to marked items using modality independent shortcuts. The user can specify whether a navigation mark disappears after a session or is persistent across sessions.

KF: 'bookmarks' is good

KP: using modality independent shortcuts

GL: How different from just saying shortcuts?

JS: just use shortcuts

<KimPatch> The user can mark items in a webpage, then navigate back to marked items using shortcuts. The user can specify whether a navigation mark disappears after a session or is persistent across sessions.

GL: do we need a defn for shortcuts?

KP: to create defn for shortcuts

RESOLUTION: KPs 631 IET modified as 'The user can mark items in a webpage, then navigate back to marked items using shortcuts. The user can specify whether a navigation mark disappears after a session or is persistent across sessions.' - definition of shortcut to be created

<scribe> ACTION: KimPatch to create shortcut definition [recorded in http://www.w3.org/2012/05/24-ua-minutes.html#action03]

<trackbot> Sorry, couldn't find user - KimPatch

<scribe> ACTION: kimpatch to create shortcut definition [recorded in http://www.w3.org/2012/05/24-ua-minutes.html#action04]

<trackbot> Sorry, couldn't find user - kimpatch

<scribe> ACTION: kim to create shortcut definition [recorded in http://www.w3.org/2012/05/24-ua-minutes.html#action05]

<trackbot> Created ACTION-733 - Create shortcut definition [on Kimberly Patch - due 2012-05-31].

Summary of Action Items

[NEW] ACTION: KFord to write IER for 1.7.4 [recorded in http://www.w3.org/2012/05/24-ua-minutes.html#action01]
[NEW] ACTION: kford to write IER for 1.7.4 [recorded in http://www.w3.org/2012/05/24-ua-minutes.html#action02]
[NEW] ACTION: kim to create shortcut definition [recorded in http://www.w3.org/2012/05/24-ua-minutes.html#action05]
[NEW] ACTION: KimPatch to create shortcut definition [recorded in http://www.w3.org/2012/05/24-ua-minutes.html#action03]
[NEW] ACTION: kimpatch to create shortcut definition [recorded in http://www.w3.org/2012/05/24-ua-minutes.html#action04]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2012/05/24 18:29:13 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/he/the/
Succeeded: s/stylesheet/stylesheets/
Succeeded: s/do/to/
Found Scribe: Harper_Simon
Found ScribeNick: sharper

WARNING: Dash separator lines found.  If you intended them to mark
the start of a new topic, you need the -dashTopics option.
For example:
        <Philippe> ---
        <Philippe> Review of Action Items

Default Present: sharper, Kim_Patch, Jeanne, Greg_Lowney, kford, [Microsoft]
Present: sharper Kim_Patch Jeanne Greg_Lowney kford [Microsoft]

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 24 May 2012
Guessing minutes URL: http://www.w3.org/2012/05/24-ua-minutes.html
People with action items: kford kim kimpatch

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]