Re: Link text generated by respec

Well.... that wouldn't have been caught by respec anyway.  Your browser's
parser would have done something with that.  No idea what tbh.  ReSpec
Errors and Warnings are reported via the ReSpec button.  This is in the DOM
- should be tabbable.  Might not be very accessible though.  I will
investigate.

On Tue, Jul 19, 2016 at 11:34 AM, Matt King <a11ythinker@gmail.com> wrote:

> Yes, I found that in the docs and as it turns out, I had a code problem
> that was preventing it from working.
>
>
>
> I don’t know how to “see” respec errors … I assume this would have
> generated an error, but where are they output? I can’t find anything when
> searching for them with JAWS.
>
>
>
> In this particular case, my defect was an extra </ like …
>
> *<code>dialog</</code>*
>
>
>
> *It took me almost an hour and some smart luck to find the problem. *
>
>
>
> *Matt*
>
>
>
> *From:* Michael Cooper [mailto:cooper@w3.org]
> *Sent:* Monday, July 18, 2016 9:45 AM
> *To:* Matt King <a11ythinker@gmail.com>; public-aria-editors@w3.org
> *Subject:* Re: Link text generated by respec
>
>
>
> Hi Matt - I just checked this, and according to the respec documentation
> this feature is still supported, and in my copy of the ARIA practices it
> seems to work. Can you indicate where it seems not to be working? Is it
> possible the anchor reference is incorrect, perhaps because ID of target
> section was changed? Michael
>
>
>
> On 12/07/2016 7:26 PM, Matt King wrote:
>
> Hi all,
>
>
>
> I think respect did this … if you write a link without link text and refer
> to a section in the same doc, like:
>
> <a href=”#ID_OF_SECTION”></a>
>
> It used to generate link text for you.
>
>
>
> Now, that seems to not be working, at least not in the APG.
>
>
>
> Do others see this problem? Was that feature intentionally removed?
>
>
>
> Matt
>
>
>
>
>



-- 
Shane McCarron
Projects Manager, Spec-Ops