Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

We definitely should reach out our AT vendor contacts, pointing to the summary of the thread, but in general I'd say it's reasonable to expect that all IA2 consumers/implementers follow the list. On Wed, Feb 22, 2017 at 2:39 AM, Dominic Mazzoni wrote: > Great summary. I

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

Hey, here's some commenting inline. On Wed, Feb 22, 2017 at 1:13 AM, James Teh wrote: > Hi guys, > > Sorry for the delay in responding. I needed to find time to sit down and > digest all of this. :) > > >1. Alex, your (thorough) outline of how this should work looks

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

Great summary. I think the next step is to bring this to other AT vendors and see if this will work for everyone. On Tue, Feb 21, 2017 at 10:13 PM James Teh wrote: > Hi guys, > > Sorry for the delay in responding. I needed to find time to sit down and > digest all of this.

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

Hi guys, Sorry for the delay in responding. I needed to find time to sit down and digest all of this. :) 1. Alex, your (thorough) outline of how this should work looks correct to me and is what I intended. Thanks. 2. Moving to the first cell in the table is easily achieved by

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

I referred to relations as a concept, which is exposed via IAccessibleRelation or accNavigate. IA2 relations don't have to be expensive, IA2 provides relationTargetsOfType which returns multiple targets for a relation type and lighter version of IAccessibleRelation array. On the other hand,

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

On Wed, Feb 15, 2017 at 11:25 AM Alexander Surkov < surkov.alexan...@gmail.com> wrote: > On Wed, Feb 15, 2017 at 2:06 PM, Dominic Mazzoni > wrote: > > Agreed, finding the first or last cell in a row isn't hard. But finding > the first or last cell in a column is hard, and

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

Agreed, finding the first or last cell in a row isn't hard. But finding the first or last cell in a column is hard, and some AT already have a command for that. Not sure what to do with the table with lots of holes in it. The best option for the user might be to just navigate linearly in the

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

I think I miss why AT can't rely on accessible tree structure to fetch first or last cell in a row. If AT has a row, then NAVDIR_FIRSTCHILD/NAVDIR_LASTCHILD can be used on the row. It may be tricky though to navigate through table with holes by means of UP/DOWN/LEFT/RIGHT relations. For example,

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

Yes, that's how I'd interpret it too. I like this because it essentially frees each AT from needing to reason about complex table structures. The browser takes care of understanding the virtual table structure and exposes it via a more straightforward API to the AT. One question, though: How

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

Let's get this discussion started again. :) I was thinking about this recently and it occurred to me that we may not need new API after all, just more implementation of existing (if rarely used) API. What do you think about implementing the NAVDIR_LEFT, NAVDIR_RIGHT, NAVDIR_UP and NAVDIR_DOWN

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

On 5/01/2016 7:53 AM, Richard Schwerdtfeger wrote: Although it is possible to have 2 cells I don't think this even close to the norm. Two cells was just an extreme example to demonstrate the issue. The point is that gaps at the start or middle of a row are problematic. Why would we we not

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

I don't think it's true that tables can currently only have missing cells at the end of a row. There's nothing preventing an author from marking any cell as aria-hidden, which removes it from the accessibility tree, but doesn't affect its row and column index. NVDA gets confused if you do this. I

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

ccess.org> Cc: IAccessible2 mailing list <accessibility-...@lists.linux-foundation.org>, accessibility-ia2-boun...@lists.linuxfoundation.org Date: 01/04/2016 10:47 AM Subject:Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

...@lists.linux-foundation.org> Date: 01/03/2016 10:55 PM Subject:Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again Sent by: accessibility-ia2-boun...@lists.linuxfoundation.org On 29/12/2015 5:52 AM, Dominic Mazzoni via Accessibility-ia2 wrote

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

zzoni <dmazz...@google.com>, IAccessible2 mailing list < > accessibility-...@lists.linux-foundation.org> > Date: 01/03/2016 10:55 PM > Subject: Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, > again > Sent by: accessibility-ia2-boun...@lists.linuxfoundation.org &g

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

On 29/12/2015 5:52 AM, Dominic Mazzoni via Accessibility-ia2 wrote: Totally agreed that screen readers need to be able to navigate from cell to cell and fetch rows at a time. Note that the spec requires the numbering to be sequential, so you don't need to worry about that. When I said

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

MUS Cc: IAccessible2 mailing list <accessibility-...@lists.linux-foundation.org>, accessibility-ia2-boun...@lists.linuxfoundation.org Date: 12/31/2015 04:07 PM Subject: Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again On

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

<dmazz...@google.com> > To: Richard Schwerdtfeger/Austin/IBM@IBMUS > Cc: IAccessible2 mailing list < > accessibility-...@lists.linux-foundation.org>, > accessibility-ia2-boun...@lists.linuxfoundation.org > Date: 12/31/2015 04:07 PM > Subject: Re: [Accessibility-ia2] ari

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

org> To: IAccessible2 mailing list <accessibility-...@lists.linux-foundation.org> Date: 12/30/2015 07:00 PM Subject:[Accessibility-ia2] aria-colcount and aria-rowcount mapping, again Sent by:accessibility-ia2-boun...@lists.linuxfoundati

Re: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, again

essibility-ia2@lists.linuxfoundation.org> > To: IAccessible2 mailing list < > accessibility-...@lists.linux-foundation.org> > Date: 12/30/2015 07:00 PM > Subject: [Accessibility-ia2] aria-colcount and aria-rowcount mapping, > again > Sent by: accessibility-ia2-boun...@lists.l