Re: How the W3C Text Alternative Computation Works

Good work Bryan

A small typo.
"...However, if a validation error occurs and display:hidden is dynamically
set to display:block, then the Name of the edit field then becomes “Email
address: ..."

Should be display:none in this case I think...

David & Kirsten MacDonald




On Mon, Dec 21, 2015 at 1:41 PM, Bryan Garaventa <
bryan.garaventa@whatsock.com> wrote:

> Hello,
> Recently I was asked to write a blog post explaining the naming
> calculation and how it works, which I've published at
>
> http://www.ssbbartgroup.com/blog/how-the-w3c-text-alternative-computation-works/
>
> I believe I've covered everything of note that should help explain the
> algorithm and how it works. The only controversial aspect is
> the section regarding aria-hidden='false', however since this is written
> in the spec, this is the only way I see that logically
> explains how this would impact the naming calculation. I'll pass this
> around to spread the word; the more who understand the
> algorithm the easier it is to understand how ATs use it. Please let me
> know if anything is missing.
>
> Also, I wanted to thank Google for stepping up and doing an excellent job
> updating the recursive naming calculation with the most
> recent release of Chrome Canary, which now has the closest recursion
> algorithm match for the naming calculation as compared with any
> of the other browsers. This is really a great achievement, and all those
> who worked on this to get this done so quickly, should be
> congratulated since it will have a significant impact in the future.
>
> All the best,
> Bryan
>
>
>
>