RE: AccName utility for live AccName algorithm testing on the fly

Hi,
Looks like this was due to a null element check missing on line 827. I added “!node ||” to this and now it appears to be working as expected.

Thanks,
Bryan


Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com
415.624.2709 (o)
www.LevelAccess.com<http://www.levelaccess.com/>

From: David MacDonald <david100@sympatico.ca>
Sent: Monday, February 18, 2019 8:01 AM
To: Bryan Garaventa <bryan.garaventa@levelaccess.com>
Cc: Devarshi Pant <devarshipant@gmail.com>; public-aria@w3.org
Subject: Re: AccName utility for live AccName algorithm testing on the fly

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

HI Bryan

I dropped in the following code into the tool

<label>foo <input type="text" aria-describedby="p2"></label><br>
<span id="p3">Some error messages</span><br>

The id for the aria describedby is intentionally wrong. It appears that in this case the Accessible Name should be "foo" and the Description should be undefined. But both are empty.


Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613-806-9005

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd<http://twitter.com/davidmacd>

GitHub<https://github.com/DavidMacDonald>

www.Can-Adapt.com<http://www.can-adapt.com/>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html>


On Fri, Feb 15, 2019 at 6:31 PM Bryan Garaventa <bryan.garaventa@levelaccess.com<mailto:bryan.garaventa@levelaccess.com>> wrote:
Hi,
As a quick note, I’ve updated the live test page to include the auto-support of focusable elements, so these will be computed automatically with or without an ID attribute. I also added aria-live=polite to the textarea so blind people like me will know that something is going on when it does.

About ANDI, to be honest, I don’t know what their internal logic is for their AccName calculation. I would hope though that they are using the same one that I have here, since this is the one we are matching specifically against the spec as we work on editing AccName 1.2, and maintaining one universal understanding of AccName will be critical to ensure that everybody stays on the same page going forward, especially as bugs are entered with browsers to meet these expectations.

Yes, there is a bookmarklet available though, which I always update to ensure that the same AccName code is included within, called Visual ARIA.
https://accdc.github.io/visual-aria/github-bookmarklet/visual-aria.htm

This is now referenced at the end of the AccName live test page as well.

When Visual ARIA is loaded, you can mouse over active elements like form fields to get the same naming computation as provided by the AccName Prototype. When updates are made, this automatically appears in your display as you use Visual ARIA. I don’t believe I have all possible elements set to display when using this feature at present though, just active elements and ARIA widget roles, which are the ones that most people need to be aware of for practical usage. The live AccName page however performs the computation on any element regardless.

Hopefully this helps a bit.

All the best,
Bryan


Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com<mailto:Bryan.Garaventa@LevelAccess.com>
415.624.2709 (o)
www.LevelAccess.com<http://www.levelaccess.com/>

From: Devarshi Pant <devarshipant@gmail.com<mailto:devarshipant@gmail.com>>
Sent: Friday, February 15, 2019 12:02 PM
To: Bryan Garaventa <bryan.garaventa@levelaccess.com<mailto:bryan.garaventa@levelaccess.com>>
Cc: public-aria@w3.org<mailto:public-aria@w3.org>
Subject: Re: AccName utility for live AccName algorithm testing on the fly

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Bryan,

This is good. Any plans to for it to become a browser favelet, like the Accessible Name and Description Inspector (ANDI) developed by SSA https://www.ssa.gov/accessibility/andi/help/install.html?


Besides other modules, ANDI also features active element inspection and reports name and description in the ANDI output.

Thanks,
Devarshi


On Thu, Feb 14, 2019 at 9:50 PM Bryan Garaventa <bryan.garaventa@levelaccess.com<mailto:bryan.garaventa@levelaccess.com>> wrote:
Hi,
I wanted to share this AccName page that was recently enhanced by Todd Briley.
https://whatsock.github.io/w3c-alternative-text-computation/Editable%20Live%20Input%20AccName%20Test.html


Instead of presenting a static page, it allows you to paste or type whatever markup that you wish to compute the AccName for directly into the page, which you can then dynamically load and test without having to edit the page or reload it. This is a great way to quickly validate markup on the fly while also referencing the latest AccName Prototype code on GitHub. This too has been added to the 'docs' folder within the main GitHub repo for reference.

A quick note, you have to include id="test" on the root node that you are computing the AccName for, otherwise the script will not know which element you are trying to calculate. Simply write the markup you wish to process into the edit field at the end of the page, then click the Paste and Test button.

If anybody else would like to contribute with related tools and utilities, please let me know. All help is welcome.

All the best,
Bryan


Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com<mailto:Bryan.Garaventa@LevelAccess.com>
415.624.2709 (o)
www.LevelAccess.com<http://www.LevelAccess.com>

Received on Monday, 18 February 2019 19:30:28 UTC