Accessible Platform Architectures Working Group Teleconference

07 Nov 2018


jasonjgw, janina, sloandr, scott_h


<jasonjgw> Janina: notes a very successful TPAC meeting, with several topics discussed in different contexts.

<jasonjgw> Knowledge domain discussions have been identified in the minutes at various points - and these are cited in the RQTF meeting agenda.

<jasonjgw> Janina notes significant interest in solution finding - especially from Digital Publishing.

<jasonjgw> Wednesday plenary session on knowledge domain, also cited in the agenda.

<jasonjgw> Janina summarizes the general outcome as indicating a need to compile more information related to the problem. This makes the RQTF work on the topic invaluable.

<jasonjgw> This progress suggests other aspects of APA activity that could benefit from the same literature analysis.

<jasonjgw> Janina suggests that some issues need to be addressed as distinct concerns (e.g., navigation support).

<jasonjgw> We should be looking for navigational paradigms - profiles of how people navigate through domain-specific content (e.g., mathematical content).

<jasonjgw> Janina notes a long-standing discussion with the CSS Working Group regarding how to identify reading order in Web content that could benefit from this work.

<jasonjgw> Having a list of navigational requirements would significantly assist the CSS accessibility task force.

<jasonjgw> Janina notes the relationships (similarities and differences) across knowledge domains - for example, mathematics and physics are closely related in notation and in the use of mathematical expressions; chemistry is similar but has distinct requirements.

<jasonjgw> Janina notes the navigational requriements emerging from two-dimensional structures (e.g., matrices, with semantically significant details along the diagonal).

<scribe> scribe: janina

jgw: Looked through math lit with nav in mind ...
... Identified implicit nav reqs
... derived from teaching approaches in textbooks
... appeared to be an early -- not fully thought through
... expand and collapse sub expressions
... ability to review the path taken to get to where you are
... second project--lambda system ...
... focused on nonlinear nav
... relied on tables for matrices, even graphs
... looked at fully linearized tabular vs spatially laid out tables
... also ability to nav between two tables
... node edge graph for automata
... adjacancy matrix
... proposes nav and manipulation are useful distinct categories

<jasonjgw> anina: agrees with the categories - navigation, manipulation, and semantic distinctions/enrichment.

<jasonjgw> Janina notes the need to identify and characterize the semantic distinctions that should be preserved in content to support alternative renderings, manipulation and navigation.

<scott_h> great approach Jason - +1 from me

<jasonjgw> Judy: notes the need for detailed technical exploration in each knowledge domain, and the complexity (diversity) of the standardization situation with respect to each knowledge domain.

<jasonjgw> Judy acknowledges that various attempts have been made to solve the accessibility problem in each knowledge domain, and the need for technical discussions that make headway in achieving common/consistent solutions.

<jasonjgw> Judy emphasizes the unusual complexity of the problems to be addressed in that they transcend several distinct areas of Web technologies for the domains under discussion.

<jasonjgw> Janina concurs with the suggested analytical categories - navigation, manipulation and semantics - which are relevant irrespective of one's preferred technical appraoch as they identify key requirements.

<jasonjgw> Scott plans to write a more detailed synopsis of the music-domain literature.

Domain-specific content and notations: themes and issues to consider in reviewing the literature.

<jasonjgw> CAPTCHA: Janina plans to work on the draft on Friday.

<jasonjgw> It is agreed that we'll leave the Wednesday meeting possibility for next week open for a possible discussion of CAPTCHA if this is considered desirable as of the beginning of the week.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2018/11/07 15:02:12 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: jasonjgw, janina, sloandr, scott_h
Present: jasonjgw janina sloandr scott_h
Found Scribe: janina
Inferring ScribeNick: janina
Found Date: 07 Nov 2018
People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)

[End of scribe.perl diagnostic output]