Re: Responsive design and "loss of functionality"

Hi Mark,

I have been wondering similarly over this question, but with regard to
5.2.1 and an alternative conforming version.

Functionality is defined as:

"processes and outcomes achievable through user action."

Processes is further defined as:

"A series of user actions where each action is required in order to
complete an activity"

To what extent and strictness "functionality" and "processes" are construed
is a question I have pondered?

Is it acceptable to have extra steps, more clicks etc on an alternative
version?

The same question probably applies to your responsiveness question. The
wording in the glossary would seem to indicate that loss of functionality
would include any significant change to processes i.e the steps needed to
accomplish an activity.

On Wednesday, June 5, 2024, Mark Magennis <Mark.Magennis@skillsoft.com>
wrote:
>
> My take on "loss of functionality" under 1.4.4 and 1.4.10 would be that
if responsive design collapses functionality into, say, a hamburger menu,
then there is no loss of functionality because it's still there, it just
requires opening a menu to get to it. I assume there would be wide
agreement on this but I may be wrong.
> But how about this scenario? A media site has a search page that searches
within all media and a separate search page in the books area of the site
that only searches within books. On the books search page, the search
filtering functionality disappears at lower screen widths but it is still
available on the main search page at the lower width. Is this loss of
functionality on the page but not on the site a "loss of functionality"?
> Mark
>
> Mark Magennis (he)
>
> Senior Accessibility Specialist
>
> Skillsoft
>
> www.skillsoft.com
>
> </mail/u/0/s/?view=att&th=18fe945c0fe5e8e5&attid=0.1&disp=emb&zw&atsh=1>
>
>