- From: Matthew King <mattking@us.ibm.com>
- Date: Thu, 4 Dec 2014 09:23:19 +0000
- To: "janina@rednote.net" <janina@rednote.net>
- Cc: W3C WAI Protocols & Formats <public-pfwg@w3.org>
- Message-Id: <OF375CF555.5C39C30C-ON88257DA4.00310924-88257DA4.0033935E@notes.na.collabserv.c>
There is a lot of discussion of the text role, with which I still have
significant concerns, and of text related to aria-hidden. But, is
consensus on major changes in the spec required before a heart beat
publication? If so, I think there should be further discussion of the text
role before publication.
I am also concerned with the accessibility of the spec itself. The respec
generated html needs quite a bit of work still. Perhaps it is fine to put
the heart beat out with such issues. I would rather we didn't. But, if it
is major work to correct them, it may be better to just get a draft out.
Issues:
1. Section heading levels are not correct. Every section, regardless of
its level, has h2. So for example, sections5, 5.1, and 5.1.1 are all H2
instead of H2, H3, and H4.
2. the permalinks are included inside the heading tags. It would improve
readability if they were not a child of the heading.
3. Headings have aria-describedby pointing to the 1st paragraph after the
heading. I do not see the benefit. The downside is extra verbosity. I
don't think it models best practice to use aria-describedby in a document
in this way.
4. All the notes have heading tags. If the notes are going to have
headings, then I believe they should be a subheading under the heading of
the section in which they exist. For example, a note in a level 4 section
like 5.1.1 would have an H5.
Matt King
IBM Senior Technical Staff Member
I/T Chief Accessibility Strategist
IBM BT/CIO - Global Workforce and Web Process Enablement
Phone: (503) 578-2329, Tie line: 731-7398
mattking@us.ibm.com
From: "janina@rednote.net" <janina@rednote.net>
To: W3C WAI Protocols & Formats <public-pfwg@w3.org>,
Date: 12/03/2014 10:37 AM
Subject: 48-Hour Call for Consensus (CfC); Publish 1 ARIA FPWD & 2
ARIA Heartbeats
Colleagues:
This is a Call for Consensus (CfC) to the Protocols and Formats Working
Group to approve publication of the following three ARIA related
documents:
* A First Public Working Draft (FP:WD of the
Accessible Name and Description: Computation and API Mappings
https://rawgit.com/w3c/aria/6cd22e8b0a834c4a54b7c6e4496a5887cc43f7ea/accname-aam/accname-aam.html
* Updated (heartbeat) drafts of the following 2 documents:
Core Accessibility API Mappings 1.1
https://rawgit.com/w3c/aria/edfde333e76d19c4bf7a421978eaf89b7d9701e6/core-aam/core-aam.html
Accessible Rich Internet Applications (WAI-ARIA) 1.1
https://rawgit.com/w3c/aria/eaf032dc62e0dc3c25b76db0f2300f972eff6977/aria/aria.html
ACTION TO TAKE
According to our agreed Consensus Procedures, this CfC is now open for
objection, comment, as well as statements of support via email. Silence
will be interpreted as support, though messages of support are certainly
welcome.
If you object to this proposed action, or have comments concerning this
proposal, please respond by replying on list to this message no later
than 17:00 (5PM) Boston Time on Friday 5 December.
Janina
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina@rednote.net
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Protocols & Formats http://www.w3.org/wai/pf
Indie UI
http://www.w3.org/WAI/IndieUI/
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina@rednote.net
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Protocols & Formats http://www.w3.org/wai/pf
Indie UI
http://www.w3.org/WAI/IndieUI/
Attachments
- application/octet-stream attachment: alt_cfc
Received on Thursday, 4 December 2014 09:24:01 UTC