On Wed, Aug 29, 2012 at 7:14 PM, Steve Faulkner
wrote:
> Hi Ian,
> you wrote:
>
>> Can you provide an example of how using a redundant role value can lead
>>> > to conflicts?
>>>
>>
> Sure. Support someone writes:
>>
>>
>>
>> ...and then someone else copies and pastes it, and changes the type
Hi Ian,
you wrote:
> Can you provide an example of how using a redundant role value can lead
>> > to conflicts?
>>
>
Sure. Support someone writes:
>
>
>
> ...and then someone else copies and pastes it, and changes the type and
> name and value, but doesn't know what "role" is:
>
>
>
that
On Sun, 10 Jun 2012, Steve Faulkner wrote:
> > >
> > > I've used role and/or redundant ARIA within the scripting
> > > environment to minimize calls in applications checking for roles.
> > > Redundancy doesn't harm anything, I actively promote it, as it does
> > > help, sometimes.
> >
> > I di
On Jun 8, 2012, at 5:46 PM, Ian Hickson wrote:
>> I've used role and/or redundant ARIA within the scripting environment to
>> minimize calls in applications checking for roles. Redundancy doesn't
>> harm anything, I actively promote it, as it does help, sometimes.
>
> I disagree with that prem
Hi Ian,
On 10 June 2012 10:16, Steve Faulkner wrote:
> Hi Ian,
>
>> On Mon, 12 Mar 2012, Charles Pritchard wrote:
>> > On 3/12/2012 5:52 PM, Ian Hickson wrote:
>> > > On Mon, 12 Mar 2012, Charles Pritchard wrote:
>> > > > >
>> > > > > Ignore the error, the HTML5 spec does not reflect implementat
Hi Ian,
> On Mon, 12 Mar 2012, Charles Pritchard wrote:
> > On 3/12/2012 5:52 PM, Ian Hickson wrote:
> > > On Mon, 12 Mar 2012, Charles Pritchard wrote:
> > > > >
> > > > > Ignore the error, the HTML5 spec does not reflect implementations
> > > > > in this section about ARIA.
> > > > >
> > > > > T
On Mon, 12 Mar 2012, Charles Pritchard wrote:
> On 3/12/2012 5:52 PM, Ian Hickson wrote:
> > On Mon, 12 Mar 2012, Charles Pritchard wrote:
> > > >
> > > > Ignore the error, the HTML5 spec does not reflect implementations
> > > > in this section about ARIA.
> > > >
> > > > The warning is not helpfu
2012/3/13 Scott González :
> It's my understanding that authors should only apply ARIA via script.
No. Where do you understand that from?
> The
> redundancy cases seem to be the most reasonable use cases I've heard of for
> wanting ARIA in the initial markup, but even that seems wrong. What happe
On Tue, 13 Mar 2012 15:57:57 -, Hugh Guiney
wrote:
The validator is probably just not up to date.
Note that that in this case the validator is probably right. If it's
just presentational, why are you using ? It doesn't seem
presentational to me. I think you are incorrectly using
ro
On Mon, Mar 12, 2012 at 8:52 PM, Ian Hickson wrote:
> The validator is probably just not up to date.
>
> Note that that in this case the validator is probably right. If it's just
> presentational, why are you using ? It doesn't seem presentational to
> me. I think you are incorrectly using role=pr
It's my understanding that authors should only apply ARIA via script. The
redundancy cases seem to be the most reasonable use cases I've heard of for
wanting ARIA in the initial markup, but even that seems wrong. What happens
when you have type=range and role=slider, the UA doesn't understand the n
On 3/12/12 11:42 PM, Simon Pieters wrote:
On Tue, 13 Mar 2012 02:16:29 +0100, Charles Pritchard
wrote:
Warnings are generally not useful. Either something is fine and we
should
support it, or it's wrong and we should alert the author. I think
"must"
is very much the appropriate requirement
On Tue, 13 Mar 2012 02:16:29 +0100, Charles Pritchard
wrote:
Warnings are generally not useful. Either something is fine and we
should
support it, or it's wrong and we should alert the author. I think "must"
is very much the appropriate requirement level here.
From the implementation-sid
On 3/12/2012 5:52 PM, Ian Hickson wrote:
On Mon, 12 Mar 2012, Charles Pritchard wrote:
>
> Ignore the error, the HTML5 spec does not reflect implementations in
> this section about ARIA.
>
> The warning is not helpful to authors nor does it accurately describe
> the means in which ATs work w
On Mon, 12 Mar 2012, Hugh Guiney wrote:
>
> Why not?
>
> I have this in an otherwise-valid HTML5 + SVG 1.1 + MathML 2.0 + RDFa
> Lite 1.1 document:
>
>
> Company Name
> Tagline
>
>
> Spec says:
>
> > Authors must not set the ARIA�role�and�aria-*�attributes in a manner
> > that conflicts
To clarify:
http://www.w3.org/TR/2011/WD-html5-20110405/author/content-models.html#annotations-for-assistive-technology-products-aria
"the presentation role may always be used.". The validator should not
have thrown an error for role=presentation.
The section was made because: "exceptions are
Ignore the error, the HTML5 spec does not reflect implementations in
this section about ARIA.
The warning is not helpful to authors nor does it accurately describe
the means in which ATs work with ARIA.
-Charles
On 3/12/2012 4:27 PM, Hugh Guiney wrote:
Why not?
I have this in an otherwise-va
Why not?
I have this in an otherwise-valid HTML5 + SVG 1.1 + MathML 2.0 + RDFa
Lite 1.1 document:
Company Name
Tagline
Spec says:
> Authors must not set the ARIA role and aria-* attributes in a manner that
> conflicts with the
> semantics described in the following table, except that the
18 matches
Mail list logo
