Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

The reason one might wish to have the reverse relationship is if the error messages could be encountered independently. Consider the following scenario: 1. User fills out form 2. User presses submit 3. New page loads displaying the errors at the top with the form fields reproduced below the

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

Note, Jamie has been objecting against new relation for aria-errormessage [1]. [1] https://lists.linuxfoundation.org/pipermail/accessibility-ia2/2016-April/002046.html On Wed, Aug 10, 2016 at 8:33 AM, Alexander Surkov < surkov.alexan...@gmail.com> wrote: > All reverse relations go at

Re: [Accessibility-ia2] ARIA feed role

Let's go with ROLE_SYSTEM_GROUPING then until Jamie has objections. On Wed, Aug 10, 2016 at 8:54 AM, Joanmarie Diggs wrote: > Hey Alex. > > On 08/10/2016 08:27 AM, Alexander Surkov wrote: > > > 1) IA2_ROLE_FEED > > Piñeiro might kill me if I tell him I need a new role in ATK.

Re: [Accessibility-ia2] ARIA feed role

So I can see three options 1) IA2_ROLE_FEED It will take time to be picked up by browsers and screen readers. 2) ROLE_SYSTEM_GROUPING with xml-roles='feed' Probably more backward compatible option, as existing AT, that have no 'feed' support, can announce 'grouping'. 3) ROLE_SYSTEM_LIST with