W3C home > Mailing lists > Public > public-pfwg@w3.org > January 2014

UAIG: features at risk status.

From: Joseph Scheuhammer <clown@alum.mit.edu>
Date: Fri, 17 Jan 2014 14:19:21 -0500
Message-ID: <52D98239.7050104@alum.mit.edu>
To: W3C WAI Protocols & Formats <public-pfwg@w3.org>
Regarding the UAIG features at risk [1], there is a test report [2] that 
captures their status, more or less.  The following is a brief 
commentary on those features-at-risk and what the test cases show.

1.  Steps 10 and 11 of Controlling focus with tabindex (Section 4.2) [3]

The relevant test cases are 31 and 32, and the report shows insufficient 
implementations.  I don't anticipate those test cases passing before the 
ARIA 1.1 timeframe.

Status:  remove steps 10 and 11 from the UAIG.

2.  Microsoft UIA columns in various mapping tables.

Since this deals with only UIA, we need a test report that shows all UIA 
tests results.  Unfortunately, I cannot generate such a report, even 
with the full main test report [4].  Note the lack of a UIA only 
column.  I suspect that none of the tests have been run.  Do any testers 
know otherwise?

Status:  Remove the columns from the tables.

3. Menu events (Section 5.8.4) [5]

Relevant tests are 104 - 108.  As of this writing, James is finishing 
testing Safari/AXAPI.  There are likely two implementations.

Status:  Two implementations are likely.  Leave the menu events section 
as is, although revisit on Mon to be certain.

4. Text alternative computation (Section 5.6.1.1), step 2B [6]

The relevant 54 test cases, and their disposition are [4]:
* 547 - 550: pass,
* 617 - 626: pass,
* 627 - 631: fail (invalid),
* 632 - 635, pass,
* 636: fail (invalid),
* 637 - 646 : pass,
* 727 - 731: pass,
* 733 - 747: pass

With respect to the failing tests, ACTION-1154 recommends removing a 
list from step 2B, namely, 'If the embedded control is a menu, use the 
text alternative of the chosen menu item.'  That's because it would be a 
menu button or popup button, not the menu itself.  Also, test 636 
involves an INPUT type="file", which we decided is also invalid since 
step 2B does not mention this type of INPUT, and there is no common UI 
for file INPUT types among browsers.

Status:  Two implementations were found; step 2B of the text alternative 
computation need not be removed.  Also, since this corresponds to the 
feature at risk in the spec itself [7], these tests satisfy the spec as 
well.

[1] http://www.w3.org/TR/wai-aria-implementation/#sotd_atrisk
[2] 
https://www.w3.org/WAI/PF/testharness/testreport?testsuite_id=2&filter_invalid=on&filter_cr_met=on&filter=Filter+view
[3] http://www.w3.org/TR/wai-aria-implementation/#keyboard-focus_tabindex
[4] https://www.w3.org/WAI/PF/testharness/testreport?testsuite_id=1
[5] http://www.w3.org/TR/wai-aria-implementation/#mapping_events_menus
[6] http://www.w3.org/TR/wai-aria-implementation/#mapping_additional_nd_name
[7] http://www.w3.org/TR/wai-aria/#sotd_atrisk

-- 
;;;;joseph.


'A: After all, it isn't rocket science.'
'K: Right. It's merely computer science.'
              - J. D. Klaun -
Received on Friday, 17 January 2014 19:19:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:44:59 UTC