Comments for today’s ARIA Caucus call (March 10)

For the record, I wished to clarify a couple of points from the minutes.

I’m not objecting to an additional combobox pattern, just that the wording needs to be clear that the 1.0 design pattern and mapping structure is and will remain valid regardless in 1.1. When Rich mentioned checker tools, this became even clearer to me that this is necessary, because if left vague, checkers are likely to start flagging role=combobox on inputs as invalid for 1.1, and this is going to lead to problems down the road because this is presently and has been going back five years the only method available for ensuring accessibility for this widget type, and it is used all over the place and it’s not going to go away.

Matt, I understand that you disagree with my statement that the original 1.0 design pattern is fully accessible, simply because I know that nothing in the world is “fully accessible”. However I don’t understand what actually is inaccessible about this design pattern when implemented properly. Here is an example that includes two such role=combobox examples.,%20Editable%20and%20Readonly)/demo.htm

Can you explain how these two widgets are still inaccessible? From my testing, this functions in the same way as a native combobox such as a select. This is why I disagree with your statement that “the 1.0 pattern will fade away”, and I don’t agree that it should.

All the best,

From: Schnabel, Stefan []
Sent: Thursday, March 10, 2016 10:12 AM
To: Rich Schwerdtfeger <>; Amelia Bellamy-Royds <>
Cc: ARIA Working Group <>
Subject: RE: [ARIA] Agenda: March 3, 2016 WAI-ARIA Working Group



From: Rich Schwerdtfeger []
Sent: Mittwoch, 9. März 2016 22:40
To: Amelia Bellamy-Royds <<>>
Cc: ARIA Working Group <<>>
Subject: Re: [ARIA] Agenda: March 3, 2016 WAI-ARIA Working Group

This involves the core aam. I sent a note to Joseph and had copied the svg a11y task force earlier although I did not link to the github issue but rather the w3c issue for it.

Rich Schwerdtfeger

On Mar 2, 2016, at 9:31 PM, Amelia Bellamy-Royds <<>> wrote:

If there's time, I'd appreciate the group taking a look at GitHub Issue #136, on the interaction of role=none/presentation and other global ARIA attributes. Joanmarie filed the issue when trying to implement SVG-AAM, but it really stems from the Core mapping spec.

I'd like to confirm that the interpretation we're taking for SVG-AAM matches how others think Core-AAM should be interpreted. And it would be nice to get clarified language into both specs in time for publication of the new drafts next week.


On 27 February 2016 at 18:59, Richard Schwerdtfeger <<>> wrote:

Agenda: March 3, 2016 WAI-ARIA Working Group

Time of meeting is 12:30PM EST, 9:30AM PST, 16:30 UTC, duration is 1.5 hours


US Toll Number: +1-617-324-0000<tel:%2B1-617-324-0000> Access code:640 582 571 (Mobile Auto Dial: +1-617-324-0000<tel:%2B1-617-324-0000>,,,640582571#)

IRC: server:<>  , port: 6665, channel: #aria.


1. Reminder: Heartbeat drafts Freeze March 11

2. Action 1490: Combobox (20 minutes *max* discussion) Matt



       - Proposal:

3. Action 2021: Draft text for default max and min spinbutton values (Joanie)



4. Action 1489: Propose spec text to limit what aria attributes can be overriden by strong native semantics (Michael)


       - Proposal:

       - Diff:

5. Action 1719: Review Draft of ARIA exit Criteria (Michael)


       - Proposal:

6 Action 1730 Draft “deprecated section for conformance section of spec.(Michael)


       - Proposal:

7. Action 2004: Create Proposal for Password Role (Cynthia Shelly to respond with response from security team)




8. Action 1723: Create sections listing the roles that provide nameFrom:author and nameFrom:Contents (Joanie)


9. Action 1743: Put aria-activedescendant on application (Joanie)


10. Actiom 1489: Propose spec text to limit what aria attributes can be overridden by strong native semantics (e.g., aria-label and aria-labelledby) (Michael)


11. Action 1513: Set up ARIA 1.1 Requirements draft (Michael)


12. Action 2023 Write a proposal about how to modify the definition of role text to limit its use.


13. Review Open Action Items and Issues (Many overdue items - need to get new dates and determine if must reassign)



Extended Description Analysis:

ARIA Test Plan Action Items:

ARIA Implementation Guide:

ARIA Name Computation Issues and Actions:

ARIA Test Report:

ARIA 1.1 Test Plan Issues and Actions:

ARIA 1.1 Test Harness:

Use Cases for Extended Descriptions:

WAI-ARIA Extension Process:

ARIA Working Group Decision Policy

Minutes Last Meeting:

Received on Thursday, 10 March 2016 19:41:41 UTC