o: Alexander Surkov <surkov.alexan...@gmail.com>
>>Cc: Joseph Scheuhammer <cl...@alum.mit.edu>, Stefan Schnabel
>><stefan.schna...@sap.com>, Steven Faulkner
>><faulkner.st...@gmail.com>, IA2 List
>><accessibility-...@lists.linux-foundat
s.linuxfoundation.org
> To: Alexander Surkov <surkov.alexan...@gmail.com>
> Cc: Joseph Scheuhammer <cl...@alum.mit.edu>, Stefan Schnabel
> <stefan.schna...@sap.com>, Steven Faulkner
> <faulkner.st...@gmail.com>, IA2 List
> <accessibil
Jamie, Alex,
There is far too much resistance to concatenating the description with the error message. It will never carry with the working group. I am sorry. Right now we are holding up ARIA in HTML in ARIA.
Can we agree:
1. For the Firefox mapping of the form element, and ARIA 1.1 form
I would also argue that, today, navigating a web page should be by regional
landmarks first. They create a table of contents for the page and we advise all
IBM developers to ensure all content is contained within a landmark. This way
content is not orphaned. To that end a form should be treated
Well it is used by the most pervasive apps on the planet using IA2 already.
Chrome, FF, and eclipse-based apps.
Sent from my iPhone
> On Aug 25, 2016, at 10:45 AM, Alexander Surkov
> wrote:
>
> I definitely agree that IA2 needs a flexible mechanism to expose
I definitely agree that IA2 needs a flexible mechanism to expose roles, I'm
just not sure it should be xml-roles object attribute.
On Thu, Aug 25, 2016 at 11:15 AM, Rich Schwerdtfeger
wrote:
> Alex, those object attributes should have been included in IA2 a long time
>
Alex, those object attributes should have been included in IA2 a long time ago.
I in no way see these as a hack. Eclipse uses them too.
Sent from my iPhone
> On Aug 25, 2016, at 9:49 AM, Alexander Surkov
> wrote:
>
> This is true, however xml-roles is not standard
This is true, however xml-roles is not standard attribute in IA2, it's
rather a browser specific hack to expose the semantics, that otherwise was
missed. So if the API provides a way to expose an element semantics more
fully, then I'd say it's the way to go.
Having said that, I'm also concerned
Hi, Joanie.
I'd say HTML form is a landmark as any other form in the world, but I let
judge others on this.
If there's no use case for ATK form role, then what is a reason to keep it?
On Thu, Aug 25, 2016 at 10:24 AM, Joanmarie Diggs wrote:
> Hi Alex, all.
>
> I don't
l.com>
> *Cc:* Alexander Surkov <surkov.alexan...@gmail.com>; Joseph Scheuhammer <
> cl...@alum.mit.edu>; Joanmarie Diggs <jdi...@igalia.com>; IA2 List <
> accessibility-...@lists.linux-foundation.org>; ARIA Working Group <
> public-a...@w3.org>; Steven Faulkne
.st...@gmail.com>
Subject: Re: [Accessibility-ia2] IA2 Role Landmark
Hi Rich,
I understand the reason for the use of the landmark role for role="form".
However, I disagree with the HTML form element being mapped to the landmark
role because semantics are lost. The fact that something
Hi Rich,
I understand the reason for the use of the landmark role for
role="form". However, I disagree with the HTML form element being mapped
to the landmark role because semantics are lost. The fact that something
is a form has more semantic value than just being a landmark. Still, if
the
Jamie,
The point is we want ALL the landmarks to be treated the same way for ATVs. So,
first we determine that it is a landmark. Then we go to xml-roles to determine
the type of landmark.
Otherwise, we need a special case for a form. That is what we are trying to
avoid. For these reasons
On 2016-02-23 10:48 PM, Rich Schwerdtfeger wrote:
We will update the ARIA mapping spec
Can you be more specific? One thing we will do is change the mapping
for role region to:
"IAccessible2: IA2_ROLE_LANDMARK and object attribute xml-roles:region".
For comparison, the current ATK/AT-SPI
Alright, please add the role to IA2. We will update the ARIA mapping spec and I
will let some of the ATs know and We will need to let Google know as well.
Rich
Sent from my iPhone
> On Feb 23, 2016, at 4:50 PM, James Teh wrote:
>
> That's a fair justification. We don't
That's a fair justification. We don't have a collections interface for
IA2, so if we did want to fetch all landmarks, we have to walk the
entire tree in-process, in which case checking the role is about the
same as checking xml-roles. Still, it does make sense and I'm happy to
accept it given
Hi all.
On 02/23/2016 03:38 PM, Alexander Surkov wrote:
> As a side note, it sounds a bit wired that the assistive technologies on
> Windows have to support a new role to make Orca faster. Please don't get
> me wrong, I'm exited to have fast Orca, but I feel there's something
> wrong with the
I'm totally up to keep APIs in sync but if no one is going to use the
feature, then there's no much benefit of implementing it. I defer to Jamie
on this.
As a side note, it sounds a bit wired that the assistive technologies on
Windows have to support a new role to make Orca faster. Please don't
Hey Jamie.
At least on my platform, getting all of the ROLE_LANDMARK objects (e.g.
for a list of landmarks dialog) via AtspiCollection is a lot more
performant than getting all the elements and then filtering out the
non-landmarks (99-100% of the set) via object attribute. The xml-roles
value
Hi Rich,
I don't necessarily have an objection to introducing a new role, but I
also don't quite follow the justification.
I follow that region became a subclass of landmark. However, I don't
follow how this changes the "landmark" role; if anything, it changes the
"region" role. And even
20 matches
Mail list logo