Hi, Jamie. Here's a changeset [1] for new relations (both direct and reverse for aria-details and aria-errormessage). Please review it at your earliest convenience.
Please object if you are not convinced that we have a valid use case for each relation. I'll be happy to update the proposal. Thanks! Alex. [1] http://git.linuxfoundation.org/?p=a11y/ia2.git;a=commitdiff;h=249313d5742b188b17b766be7666f2a92854b013 On Thu, Sep 8, 2016 at 7:22 AM, Alexander Surkov <surkov.alexan...@gmail.com > wrote: > Thank you, Jamie. I'm taking that screen readers may need to a context > element, when error message pops up, as a use case for a reverse relation > (if not, please correct me). > > Could you also comment my guess about aria-details? If a screen reader > skips aria-details elements when navigating, then what mechanism we'd use > for aria-details element detection. > > On Wed, Sep 7, 2016 at 8:12 PM, James Teh <ja...@nvaccess.org> wrote: > >> Agreed. Happy to have a reverse relation for errormessage, since we seem >> to have a use case. We don't seem to have a compelling use case for a >> reverse relation for details, so let's leave it out for now. >> >> On 8/09/2016 5:25 AM, Richard Schwerdtfeger wrote: >> >> Hi Alex, >> >> Correct, aria-details requires no special role. However, the use case is >> for the digital publishing industry. They want to be able to take a piece >> of content and go to the alternative content that provides detailed >> information which could be alternative content as we discussed previously. >> The user may or may not wish to go back to the content the details is being >> provided for. >> >> The need for a reverse relationship for the error message is more >> critical. >> >> So, do we agree on a reverse relationship for error message and not >> details? >> >> >> >> Rich Schwerdtfeger >> >> >> >> ----- Original message ----- >> From: Alexander Surkov <surkov.alexan...@gmail.com> >> <surkov.alexan...@gmail.com> >> To: Brett Lewis <ble...@vfo-group.com> <ble...@vfo-group.com> >> Cc: Richard Schwerdtfeger/Austin/IBM@IBMUS, "ja...@nvaccess.org" >> <ja...@nvaccess.org> <ja...@nvaccess.org> <ja...@nvaccess.org>, >> "jdi...@igalia.com" <jdi...@igalia.com> <jdi...@igalia.com> >> <jdi...@igalia.com>, "accessibility-...@lists.linux-foundation.org" >> <accessibility-...@lists.linux-foundation.org> >> <accessibility-...@lists.linux-foundation.org> >> <accessibility-...@lists.linux-foundation.org> >> Subject: Re: Reverse relationships >> Date: Wed, Sep 7, 2016 10:34 AM >> >> You're right. An element referred by aria-errormessage can be an alert of >> live region and thus should be announced by a screen reader, when it pops >> up. In this case, it seems the screen reader may need to find a context >> element, and if this is true, then the reverse relation is needed. >> >> aria-details are different, since they are more like labels and >> descriptions, and I guess thus they should be skipped when navigating the >> virtual buffer. That suggests that aria-details either needs a role (or >> xml-roles object attribute) or a reverse relation. >> >> On Wed, Sep 7, 2016 at 11:11 AM, Brett Lewis <ble...@vfo-group.com> >> wrote: >> >> Hi, >> >> Is that documented somewhere? >> >> I read through the information on error and I don’t see anything about AT >> skipping error messages if encountering them while reading through the >> virtual buffer. >> >> Have I misunderstood something? >> >> Thanks, >> >> Brett >> >> >> >> *Brett Lewis* >> >> *VFO* | Software Engineer >> >> 11800 31st Court North, St. Petersburg, FL 33716 >> >> *T* 727-299-6270 >> >> ble...@vfo-group.com >> >> www.vfo-group.com >> >> >> >> >> >> *From:* Alexander Surkov [mailto:surkov.alexan...@gmail.com] >> *Sent:* Wednesday, September 07, 2016 8:02 AM >> *To:* Brett Lewis <ble...@vfo-group.com> >> *Cc:* Richard Schwerdtfeger <sch...@us.ibm.com>; ja...@nvaccess.org; >> jdi...@igalia.com; accessibility-...@lists.linux-foundation.org >> *Subject:* Re: Reverse relationships >> >> >> >> Hi, Brett. >> >> Can you please elaborate your use case? My understanding is AT skips >> error/details, if the user encounters them, but announce them, when the >> user navigates to an element related with error/details. Why would AT need >> to find a related element by error/details? >> >> Thanks. >> >> Alex. >> >> >> >> On Wed, Sep 7, 2016 at 9:42 AM, Brett Lewis <ble...@vfo-group.com> wrote: >> >> Hi Rich, >> >> I think we do need the reverse relationships. >> >> Web authors can place the error/details anywhere on the page and there >> doesn’t seem to be any simple way for the user to determine what element >> the error message or details applies to without such a reverse relation. >> >> Brett >> >> >> >> >> >> *Brett Lewis* >> >> *VFO* | Software Engineer >> >> 11800 31st Court North, St. Petersburg, FL 33716 >> >> *T* 727-299-6270 >> >> ble...@vfo-group.com >> >> www.vfo-group.com >> >> >> >> >> >> *From:* Richard Schwerdtfeger [mailto:sch...@us.ibm.com] >> *Sent:* Tuesday, September 06, 2016 12:57 PM >> *To:* ja...@nvaccess.org; surkov.alexan...@gmail.com; Brett Lewis < >> ble...@vfo-group.com>; jdi...@igalia.com >> *Cc:* accessibility-...@lists.linux-foundation.org >> *Subject:* Reverse relationships >> >> >> >> We need agreement: >> >> >> >> Should the error message and details relationships have reverse mappings? >> >> >> >> Rich >> >> >> >> >> >> Rich Schwerdtfeger >> >> >> >> >> >> >> >> >> -- >> James Teh >> Executive Director, NV Access Limited >> Ph +61 7 3149 3306www.nvaccess.org >> Facebook: http://www.facebook.com/NVAccess >> Twitter: @NVAccess >> SIP: ja...@nvaccess.org >> >> >
_______________________________________________ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
