RE: 7-Day Call for Consensus (CfC): Publish FPWD of AccName 1.2

+1 for me, but I do need to point out some things for the record as well.

As part of the AccName simplification project that we have previously discussed, I am planning to reorganize much of the algorithm content to make it easier for implementors to understand and implement, so there will be substantive changes in the future once I have a working draft ready for people to review. This isn't one of those things that can be released one bit at a time since it involves the whole structure of the content.

The draft outline that I submitted weeks ago is the forerunner to this, which will need a wiki page on the AccName spec repo for general reference and where updates can be posted. The structure will reflect the bones of how I am planning to reorganize the spec itself, and to provide a way to keep track of new additions as part of 1.2 to account for new role additions and how these need to be processed in the right locations as part of the algorithm. This is important, because the order of processing is just as significant as what is or is not meant to be processed, and all of these need to be in alignment. So the spec text will be framed around this outline structure to ensure interoperability, and to make it easier to insert new concepts in the correct locations as updates to the ARIA spec are made in the future.

One important change is how child nodes are processed when they do not except 'name from content', but in some cases they do need to be processed regardless to ensure logical accessibility. The logic for this is already included in the outline, but the spec text does not yet exist for it since there needs to be a relevant structure for it to exist within.

This sounds complicated, but it is meant to make the spec easier to read and understand, and to also provide a mechanism where agreed upon concepts can be more readily reviewed and understood by those already implementing these changes within browsers.

All the best,
Bryan



Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com
415.624.2709 (o)
www.LevelAccess.com

> On Jun 27, 2019, at 11:22 AM, Joanmarie Diggs <jdiggs@igalia.com> wrote:
>
> This is a Call for Consensus (CfC) to the ARIA Working Group on the question of publishing First Public Working Drafts of AccName 1.2. The content to be published can be found at the https://rawgit.com/w3c/accname/FPWD_CANDIDATE_1/.

>
> Details
> -------
> The only substantive change thus far is modifying step 1 of the algorithm so that it now reads:
>
>  Set the root node to the given element, the current node to the  root 
> node, and the total accumulated text to the empty string ("").
>  If the root node's role prohibits naming, return the empty string  
> ("").
>
> This change in and of itself has no implementation impact, but it allows other specifications to optionally prohibit naming for a top-level element. Furthermore, even if this prohibition is made within a specification, that prohibition will not have any impact on calculating name from contents. The reason for the addition to this statement is to make it possible for specifications to achieve results such as the following:
>
>  <span aria-label="bar">foo</span>: The span has no name.
>
>  <button><span aria-label="bar">foo</span></button>: The button's  
> accessible name is "bar" (but the span itself has no name).
>
> But, again, doing the actual prohibiting will still need to be done elsewhere; not in AccName.
>
> Action
> ------
> This CfC is now open for objection, comment, as well as statements of support via email. Silence will be interpreted as support, though messages of support are certainly welcome.
>
> If you object to this proposal, or have comments concerning it, please respond by replying on list to this message no later than 12:00 Boston Time, Friday, 5 July 2019.
>
> For objections only, please copy the main public-aria@w3.org list to allow technical discussion of the objection to happen there.
>
> Process
> -------
> This CfC is conducted per the ARIA WG decision policy: 
> https://www.w3.org/WAI/ARIA/decision-policy

>

Received on Friday, 28 June 2019 17:31:50 UTC