E-mail List Archives
Re: Confirmation of actions - violation or feature?
From: Jonathan Cohn
Date: Jul 18, 2018 9:44AM
- Next message: Peter Quale: "Re: Interpretation of WCAG 1.4.13"
- Previous message: Maxability A11Y: "Re: [EXTERNAL] Regular Web Conferencing Session for Accessibility Professionals?"
- Next message in Thread: Ajay Sharma: "Re: Confirmation of actions - violation or feature?"
- Previous message in Thread: Maxability A11Y: "Re: Confirmation of actions - violation or feature?"
- View all messages in this Thread
I would also suggest that just "filter applied" is minimally useful as a
status. I would prefer if an approximation of the size of the filtered
results can be quite helpful.
On 18 July 2018 at 10:41, Maxability A11Y < <EMAIL REMOVED> >
wrote:
> Hi Ajay,
>
> In many cases the content that is modified because of filters is after the
> filter components and the user will navigate forward to read the filtered
> content. The announcement of the alert that says filters applied is a best
> practice as far as my knowledge is concerned. Anything that gets updated
> before the initiating element in the content sequence can be considered
> violation. Since this is a content change for the sequence I hope it is a
> 1.3.2 Meaningful Sequence success criteria.
>
> As you said that the page is refreshed, consider checking the focus of the
> screen reader after hitting the filter button. Chances that the screen
> reader focus may jump to an arbitrary region on the page which may cause in
> 2.4.3 Focus order failure.
>
> Hope this helps.
>
>
> On Wed, Jul 18, 2018 at 2:11 PM, Mohith BP < <EMAIL REMOVED> > wrote:
>
> > Hi,
> >
> > Is there any clue for the non-screen reader users such as any change
> > of color, shape such as arrow up / down etc.?
> > then 1.1.1, 1.3.3 and / or 1.4.1.
> >
> > Are there other mechanisms such as remove filter which indirectly
> > notifies the users that the filter has been applied?
> >
> >
> > Thanks & Regards,
> > Mohith B. P.
> >
> > On 7/18/18, Ajay Sharma < <EMAIL REMOVED> > wrote:
> > > Hey All,
> > >
> > > Need your thoughts on this situation, would you consider it as
> > > accessibility violation or a usability feature?
> > >
> > > Expected - Screen reader should confirm"Filters Applied" after user
> > > hits "Apply" button after selecting the filters from the filters
> > > dropdown.
> > > Actual - Page refreshes when "Apply" button is clicked and screen
> > > reader doesn't say anything.
> > >
> > > Although there is SC 4.1.3 Status Messages in WCAG 2.1 for it but we
> > > do not follow it till now, the closest SC seems to be 1.23.1 Info and
> > > Relationship.
> > >
> > > Thoughts?
> > >
> > > Best Regards,
> > > Ajay
> > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > >
- Next message: Peter Quale: "Re: Interpretation of WCAG 1.4.13"
- Previous message: Maxability A11Y: "Re: [EXTERNAL] Regular Web Conferencing Session for Accessibility Professionals?"
- Next message in Thread: Ajay Sharma: "Re: Confirmation of actions - violation or feature?"
- Previous message in Thread: Maxability A11Y: "Re: Confirmation of actions - violation or feature?"
- View all messages in this Thread