- From: Matt King <a11ythinker@gmail.com>
- Date: Sun, 8 Mar 2020 18:34:36 -0700
- To: <public-aria-practices@w3.org>
- Message-ID: <046f01d5f5b2$e4f39490$aedabdb0$@gmail.com>
Hi All, We have a PR for adding guidance for range related properties. It is very close to final. However, we need to give it a bit more scrutiny. It contradicts itself in a few places. The information in the table in section 8.1 that describes the requirements in the ARIA specification, which values are required and what default values they have, does not always agree with the prose in the subsequent sections. I'd be happy to make them align by changing the prose where appropriate. But, I'd like to first have the information in the table verified by at least 2 people. This is a relatively straightforward task: compare the information in the table to the information in the ARIA spec for each of the 5 roles listed in the table. Then, add a comment in the pull request if you find a discrepancy. If you do not find a discrepancy, add a comment that says the values in the table in section 8.1 match the ARIA spec. The only complicating factor is that the ARIA spec for meter will be changing. So, for meter, it is important to look at the revised version of the spec instead of the current master. Here are all the necessary links: 1. The APG branch with the table in section 8.1. This link goes right to section 8.1: https://raw.githack.com/w3c/aria-practices/zcorpan/range-related-properties- 2/aria-practices.html#range_related_properties_using_aria-valuemin_aria-valu emax_and_aria-valuenow 2. The current master branch of the ARIA spec: https://w3c.github.io/aria/ 3. The branch of the ARIA spec where meter has been changed: https://pr-preview.s3.amazonaws.com/w3c/aria/pull/1129.html 4. The APG pull request where we need the comments: https://github.com/w3c/aria-practices/pull/1279 Thank you! Matt
Received on Monday, 9 March 2020 01:34:56 UTC