(unknown charset) Re: Responsive design and "loss of functionality"

Can you  share a link to this for us?
Just reading me has me feeling it is complex.  witnessing it in action 
might   make the process more clear, if that resonates?



On Sat, 8 Jun 2024, Michael Livesey wrote:

> I would appreciate some feedback as to our situation with respect to
> functionality and processes.
>
> We have a dropdown select type list. This list is a third party tool, and
> doesn't support a grid pattern so we can't have interactive elements within
> the list.
>
> For the non-accessible site, we added trash icons in the list so a user
> could open the list and delete multiple options from the list just by
> opening it, scrolling and clicking the items to delete.
>
> However, for the accessible version, the user only had arrow key support
> for moving up and down the list for selection only, they couldn't access
> the trash icon. So we removed the trash icon, and placed a delete button
> outside the list.
> In order to delete an item, the accessible user had to select it, close the
> list, tab onto the external button, then delete. To do this multiple times
> is therefore a different process albeit the functionality could be said to
> be the same.
>
> The team was divided as to whether functionality under 5.2.1 had been met
> or whether this was a failure. I felt this was unduly complex versus the
> non-conforming version of the site, others thought it was a technical pass
> (albeit bad UX).
>
>
> On Thu, Jun 6, 2024 at 2:18 AM Patrick H. Lauke <redux@splintered.co.uk>
> wrote:
>
>> When considered purely on a "per page" level, this sounds like a
>> failure. But looking at it more holistically on a "per site" basis, I
>> would say it passes as the user can still achieve the same end result
>> (just by a different route).
>>
>> P
>> --
>> Patrick H. Lauke
>>
>> * https://www.splintered.co.uk/
>> * https://github.com/patrickhlauke
>> * https://flickr.com/photos/redux/
>> * https://mastodon.social/@patrick_h_lauke
>>
>>
>>
>