Thread Subject: Re: Web - Link purpose-harmonizationwithWCAG2.0

Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.

From: Gregg Vanderheiden
Date: Wed, Jun 27 2007 11:25 AM


It is supposed to say " When you have the two of them you can figure it
out. "
We are considering adding "together" so it is clearer.

In WCAG - "making sense ONLY from link text" is a different provision at a
higher accessibility level.


Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.



> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Jared Smith
> Sent: Wednesday, June 27, 2007 10:53 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Web - Link
> purpose-harmonizationwithWCAG2.0
>
> I think the confusion here arises from the definition of
> "programmatically determined link context". In WCAG 2.0, this
> includes the link text itself -
> http://www.w3.org/TR/WCAG20/#pdlinkcontextdef
>
> If we take this literally, then the word "and" in the WCAG
> 2.0 language does not allow links to make sense all by
> themselves, they
> *must* make sense only with the link content. If there is no
> context other than the link text, then would it fail?
>
> So "or" does make more sense to me. Better yet, if the link
> text is one possible component of programmatically determined
> link context, then "The purpose of each link can be
> determined from the programmatically determined link context"
> would suffice as it would allow both the link text and the
> link context to be used in determining the purpose of the link.
>
> An alternative that perhaps is better and doesn't rely so
> much on the definition of link context: "The purpose of each
> link can be determined from the link text or the link text
> and its programmatically determined link context."
>
> I'm also a bit concerned with the word "purpose". I don't
> think it is inclusive enough. Don't we really mean "function"
> or "function or target" or "general context of the link
> target" or something. I have no recommendations for change
> here, but "purpose" seems much to vague
> - it refers to what the link *does* ("something will
> happen"), not to what the link is about ("*this* will happen").
>
> Jared Smith
> WebAIM
>


WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University