See also: IRC log
<Jan> Scribe:Jan
http://lists.w3.org/Archives/Public/w3c-wai-au/2012JanMar/0001.html
<scribe> Scribe: andrewronksley
<Jan> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#sc_a222
JR: The idea is that the text editor serves two purposes. It serves as a text editor but also it's a part of a workflow.
<Jan> JR: ANy objections to the SC wording?
<Jan> Resolution: All agree with "A.2.2.2 Access to Rendered Text Properties:@@If an editing-view renders any text formatting properties that authors can also edit using the editing-view, then the properties can be programmatically determined."
JR: The level is currently A.
Wondering if this should be AA?
... It's not preventing authors from editing something. It's
making something more effective.
<Jan> Resolution: Change A.2.2.2 Access to Rendered Text Properties to AA
<Jan> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#sc_a311
JR: Some questions raised about devices that don't have a keyboard. We're not trying to imply that the device has to have a physical keyboard. We've added a note to clarify this.
JS: I would use the phrase "hardware" keyboard rather than "conventional" keyboard.
Not all software keyboards have tab and arrow keys
There's often alternative (third party) keyboards available that do have these keys though.
<Jan> Note 1: Keyboard interfaces are programmatic services provided by many platforms that allow operation in a device independent manner. This success criterion does not imply the presence of a hardware keyboard.
<Jan> Resolution: All accept: Note 1: Keyboard interfaces are programmatic services provided by many platforms that allow operation in a device independent manner. This success criterion does not imply the presence of a hardware keyboard."
<Jan> Note 3: This success criterion does not forbid and should not discourage @@other input methods (e.g., mouse, touch) in addition to keyboard operation.
<Jan> Resolution: All accept: "Note 3: This success criterion does not forbid and should not discourage other input methods (e.g., mouse, touch) in addition to keyboard operation."
<Jan> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#sc_a311-i
<Jan> Note 1 clarifies that the success criterion does not require a hardware keyboard to be present. Many mobile platforms lack hardware keyboards, but nonetheless provide "keyboard interfaces".
<Jan> Resolution: All accept "Note 1 clarifies that the success criterion does not require a hardware keyboard to be present. Many mobile platforms lack hardware keyboards, but nonetheless provide "keyboard interfaces"."
<Jan> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#sc_a315-i
<Jan> Resolution: All accept "@@on platforms that support keyboard commands"
<Jan> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#sc_a316-i
<Jan> Resolution: All accept "@@on platforms that support keyboard commands " for A.3.1.6
<Jan> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#sc_a421
What if the feature requires no action on the user's part?
Things like programatically determined. Users don't get involved with that stuff.
<Jan> A.4.2.1 Document Accessibility Features: All features of the authoring tool that are used direclty by the author and that are used to meet Part A of ATAG 2.0 (e.g., keyboard shortcuts, text search) are documented.
<Jan> Jeanne: A.4.2.1 Document Accessibility Features: All features of the authoring tool that require author interaction and that are used to meet Part A of ATAG 2.0 (e.g., keyboard shortcuts, text search) are documented.
JR: There's things that are so
trivial that they probably don't need documenting
... e.g. a search box
GS: Section 508 does have a
requirement for documentation of accessibility features
... How do you count features though
Alex: once you start counting you realise it's practically impossible
GS: Section 508 doesn't comment on the quality of the documentation, just that it's available.
JR: I think what we're getting at is some accessibility features will be hard to use without documentation, e.g. keyboard shortcuts.
GS: The other issue that comes
into play is platform or OS conventions.
... There's an assumption that people will know a certain
amount.
... e.g. on Windows CTRL+O for open etc.
Alex: Normally the platform should provide documentation relating to things such as this.
GS: Getting back to the notion of trivial, we assume users know the conventions for their platform. That being said, users still ask us to document these kinds of things.
JR: Maybe what trivial means in this case is things that are common to a platform.
<Jan> ACTION: JR to To propose something for A.4.2.1 that includes user interactive features and a note on platform conventions being documented elesewhere [recorded in http://www.w3.org/2012/01/09-au-minutes.html#action01]
<trackbot> Created ACTION-370 - Propose something for A.4.2.1 that includes user interactive features and a note on platform conventions being documented elesewhere [on Jan Richards - due 2012-01-16].
<Jan> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#sc_b311
<Jan> Resoltuion: All accept "@@in such a way" in B.3.1.1
<Jan> Resolution: All accept "@@in such a way" in B.3.1.1
<Jan> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#conf-req
<Jan> Everyone will take an action to look at the (tentative) confromance requirements http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#conf-req
<Jan> 9. (Tentative) Table of Accessibility Information types in the Implementing doc
<Jan> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#prompting-types
<Jan> Resolution: To remove the tentative marking on the Table of Accessibility Information types (i.e. to keep the table)
<Jan> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#def-Accessibility-Information
<Jan> remove ")" at end of accessibility info
<Jan> Resolution: Alll accept "Note: For the purposes of ATAG 2.0, only programmatically determinable information qualifies. For additional examples, see Appendix A of the Implementing ATAG 2.0 document."
<Jan> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20111222/#def-Keyboard-Interface
<Jan> A programmatic interface used by software to obtain keystroke input. A keyboard interface can allow keystroke input even if particular devices do not contain a hardware keyboard (e.g., a touchscreen-controlled device can have a keyboard interface built into its operating system to support onscreen keyboards as well as external keyboards that may be connected).
<Jan> Note: Keyboard-operated mouse emulators, such as MouseKeys, do not qualify as operation through a keyboard interface because these emulators use pointing device interfaces, not keyboard interfaces.
<Jan> Keyboard interfaces are programmatic services provided by many platforms that allow operation in a device independent manner. This success criterion does not imply the presence of a conventional keyboard.
<Jan> Keyboard interfaces are programmatic services provided by many platforms that allow operation in a device independent manner. A keyboard interface can allow keystroke input even if particular devices do not contain a hardware keyboard (e.g., a touchscreen-controlled device can have a keyboard interface built into its operating system to support onscreen keyboards as well as external...
<Jan> ...keyboards that may be connected).Note: Keyboard-operated mouse emulators, such as MouseKeys, do not qualify as operation through a keyboard interface because these emulators use pointing device interfaces, not keyboard interfaces.
<Jan> Resolution: All accept "Keyboard interfaces are programmatic services provided by many platforms that allow operation in a device independent manner. A keyboard interface can allow keystroke input even if particular devices do not contain a hardware keyboard (e.g., a touchscreen-controlled device can have a keyboard interface built into its operating system to support onscreen keyboards as...
<Jan> ...well as external keyboards that may be connected).Note: Keyboard-operated mouse emulators, such as MouseKeys, do not qualify as operation through a keyboard interface because these emulators use pointing device interfaces, not keyboard interfaces.
<jeanne> http://www.w3.org/WAI/AU/2012/ATAG20tests/
<jeanne> http://www.w3.org/WAI/AU/2011/ED-ATAG20-20111222/MASTER-20111221
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) Found Scribe: Jan Inferring ScribeNick: Jan Found Scribe: andrewronksley Inferring ScribeNick: andrewronksley Scribes: Jan, andrewronksley ScribeNicks: Jan, andrewronksley WARNING: No "Present: ... " found! Possibly Present: Alessandro_Miele Alex Andrew Cherie GS Greg IPcaller JR JS Jan Jeanne Microsoft Note P1 Resoltuion Tim Tim_Boland aaaa andrewronksley trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2012JanMar/0000.html Got date from IRC log name: 09 Jan 2012 Guessing minutes URL: http://www.w3.org/2012/01/09-au-minutes.html People with action items: jr WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]