[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-tc] DocBook Technical Committee Meeting Minutes: 18 July 2012
Folks, per my action item, here is the proposal for Table Accessibility changes: In order to enhance accessibility for screen readers, the following changes are proposed to the DocBook table model for DocBook v5.1 (and associated schemas): 1. Allow @headers attribute on <entry>. Identifies one or more entry elements that apply to its entry. The headers attribute contains an unordered set of unique space-separated tokens, each of which is an ID reference. For example: <thead><row> <entry scope="col" id="col9a">12/12/2005</entry> <entry scope="col" id="col9b">12/19/2005</entry> <entry scope="col" id="col9c">12/26/2005</entry> </row></thead> <row> <entry id="col8-1b">Actual</entry> <entry headers="col9 col9a row1 col8-1b">11,123.45</entry> <entry headers="col9 col9b row1 col8-1b">11,012.34</entry> <entry headers="col9 col9c row1 col8-1b">10,987.64</entry> </row> 2. Allow @scope attribute on <entry>. The scope attribute can contain one of "row" or "col" or "rowgroup" or "colgroup", where: * The row keyword, which maps to the row state. The row state means the header cell applies to some of the subsequent cells in the same row(s). * The col keyword, which maps to the column state. The column state means the header cell applies to some of the subsequent cells in the same column(s). * The rowgroup keyword, which maps to the row group state. The row group state means the header cell applies to all the remaining cells in the row group. An entry element's scope attribute must not be in the row group state if the element is not anchored in a row group. * The colgroup keyword, which maps to the column group state. The column group state means the header cell applies to all the remaining cells in the column group. An entry element's scope attribute must not be in the column group state if the element is not anchored in a column group. * The auto state. The auto state makes the header cell apply to a set of cells selected based on context. The scope attribute's missing value default is the auto state. <! ENTITY % tbl.entry.scope "scope (row|col|rowgroup|colgroup) #IMPLIED"> 3. Add @rowheader to the colspec element, with possible values 'yes' or 'no'. There is no default value, but absence of the attribute implies 'no'. 4. Since there is no @summary in CALS, the table's summary should be allowed in a caption. Ensure that <caption> is allowed within <table>. This proposal is informed by the following resources (courtesy of Nathalie Sequiera): http://www.w3.org/html/wg/wiki/IssueTableHeaders W3C HTML5 editor's draft (26 June 2012) - scope: http://dev.w3.org/html5/spec/the-th-element.html#the-th-element - headers: http://dev.w3.org/html5/spec/attributes-common-to-td-and-th-elements.html Techniques for WCAG2.0: http://www.w3.org/TR/WCAG20-TECHS/H43.html W3C research on complex tables: http://www.w3.org/html/wg/wiki/ComplexTables WebAim Guide for accessible data tables: http://webaim.org/techniques/tables/data Thanks and best regards, --Scott Scott Hudson | Pelco by Schneider Electric | United States | Standards Lead Site: pdn.pelco.com | scott.hudson@schneider-electric.com On 7/27/12 10:54 AM, "Bob Stayton" <bobs@sagehill.net> wrote: > DocBook Technical Committee Meeting Minutes: 18 July 2012 > ============================================================= > > The DocBook Technical Committee met on Wednesday, 18 July 2012 at > 01:00p ET. > > 1. Roll call > > Present: Nancy Harrison, Dick Hamilton, Scott Hudson, > Larry Rowland, Bob Stayton, Norm Walsh > > Regrets: Jirka Kosek > > 2. Accepted the minutes [1] of the previous meeting. > > 3. Next meeting: 15 August 2012 > > 4. Review of the agenda. > > 5. Review of open action items > > a. Norm to publish an XSD for 5.1 when it is finished. > CONTINUED > > b. Norm to document XLink support in The Definitive > Guide for 5.1, including the concern about > translatable text in the title attribute. > CONTINUED > > c. Jirka to follow up on OASIS mirroring the schema directory. > CONTINUED [Reassign this item to Norm] > > d. Norm to integrate accessibility attributes > into DocBook 5.1. > CONTINUED > > e. Norm to allow admonitions in table in DocBook 5.1. > CONTINUED > > f. Larry to propose mechanism for profiling based on > output type so it is compatible with the same > feature in DocBook assembly. > COMPLETED > > 6. OASIS website issues > > Improvements are pending. > > 7. Publisher's subcommittee > > A new draft of the spec is being developed, considering > table accessibility features now. Next meeting is 25 July. > They request that people try out the publisher's stylesheet. > > The eLearning subcommittee will meet 27 July, and are still > recruiting new members. > > 8. DocBook Assembly: > Proposal to change @fileref to @uri in resource element. > > Norm proposed @href instead. Approved for 5.1. > > ACTION: Norm to change @fileref to @href in assembly. > > 9. CALS table accessibility > a. scope attribute. > b. Feedback from Nathalie Sequeira. > > The Committee discussed these features and is generally in > favor of the changes. > > ACTION: Scott to write a proposal for the schema changes. > > 10. Transclusion in DocBook > > Norm reports that the W3C Core Working Group is > proceeding, awaiting a draft from Norm for > XInclude 1.1. > > 11. DocBook 5.1 release > > Waiting for table accessibility issues to be settled. > > 12. Review of Requests for Enhancement > > To browse a specific RFE, enter the URL (on one line): > > http://sf.net/support/tracker.php?aid=XXXXXX > > RFEs to revisit for 6.0 > 1907003 biblioid content model too broad > > RFEs under discussion > 2820947 Ability to transclude text > 3035565 Allow sections at any level > 3107140 aconym expansion inline > 3156768 <result> tag > 3491860 license tag > > New RFEs > 3531929 Include Equivalent format Attribute Name to DocBook Elements > > This request is to add a new profiling attribute to specify > the output format such as 'html', or 'pdf'. The Committee > agreed to the need, but the proposed attribute name of 'format' > was not favored because it could be interpreted as applying > styles to an element. Instead, proposed using @outputformat, > and change the attribute name in assembly to match it. > > ACTION: Norm to reply to the author in the RFE. > > ACTION: Norm to add @outputformat as a profiling attribute. > > ACTION: Norm to change @format to @outputformat in > the assembly element named 'output'. > > 3540409 Extending function attribute for keycap element > > Agreed to add AltGr and Return to the list of allowed values. > Other keys can be had by using the @other attribute. > > ACTION: Norm to add AltGr and Return to the enumerated values > of the keycap element. > > > ----- > > [1] http://lists.oasis-open.org/archives/docbook-tc/201206/msg00008.html > [2] http://lists.oasis-open.org/archives/docbook-apps/201203/msg00065.html > [3] http://www.w3.org/TR/2012/NOTE-xinclude-11-requirements-20120214/ > > > Bob Stayton > Sagehill Enterprises > bobs@sagehill.net > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: docbook-tc-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: docbook-tc-help@lists.oasis-open.org > > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > ______________________________________________________________________
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]