Re: 48-Hour CfC: Publish third (4th) release of the Note ARIA Authoring Practices 1.1

+1

On Wed, Jul 17, 2019 at 7:57 AM Janina Sajka <janina@rednote.net> wrote:

> +1
>
>
> Joanmarie Diggs writes:
> > This is a Call for Consensus (CfC) to the ARIA Working Group on the
> question
> > of publishing a fourth (4th) release of the Note ARIA Authoring
> > Practices 1.1. The content to be published can be found at:
> >
> https://raw.githack.com/w3c/aria-practices/apg-1.1r4-candidate/aria-practices.html
> >
> > Summary of changes
> >
> > Major additions and revisions:
> >
> > * Added section providing guidance on coding and composing accessible
> >   names and descriptions. This section comprehensively covers ARIA and
> >   HTML naming and describing techniques as well as specific guidance for
> >   every ARIA role.
> > * Added example of a site navigation bar ( " menu system " ) with
> >   dropdown lists of links coded using the disclosure pattern.
> > * Added an example of a date picker based on the dialog and grid
> >   patterns. A modal dialog contains a calendar grid that presents
> >   buttons for each day of a month.
> > * Added an example of a date picker that uses three spin buttons for
> >   day, month, and year.
> > * Image Carousel Example: Updated the example so that the rotation
> >   control is always visible instead of only being visible for keyboard
> >   users who move focus into the carousel region. Also changed the
> >   controls so they are implemented with HTML button elements instead of
> >   links with the button  role.
> > * Toolbar Example: Added popup text labels for icons that are displayed
> >   on both hover and focus.
> >
> > Minor revisions of guidance or implementation were made to the following
> > design patterns and examples:
> >
> > * Editor Menubar Example: Updated example so that meta data used by the
> >   scripts is specified using data-  attributes instead of with rel
> >   attributes.
> > * Radio Group with Active Descendant Example: Removed unused keycodes
> >   and fixed linting issues.
> >
> > 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 17:00 Boston
> > Time, Thursday, 18 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
>
> --
>
> Janina Sajka
>
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:       http://a11y.org
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Accessible Platform Architectures        http://www.w3.org/wai/apa
>
>
>