[PatternFly] User Accessibility Consideration

[Greg Sheremeta]

On Mon, Jun 17, 2019 at 12:21 PM Alex Mayberry <amayberr at redhat.com> wrote:

> How do I determine which version of patternfly is in use?  We've just
> upgraded from Satellite6.3 to 6.5.  I did try a quick google, but I'm only
> getting references, nothing showing precisely what version.
>

Looks like 3:
https://github.com/theforeman/foreman/blob/develop/package.json#L95


>
> As for the option I mentioned.  I am not a web developer, so I'm sure
> there are myriad considerations I simply don't have the frame of reference
> to consider.  But to clarify my thought, I was considering a user or
> session flag that alters the way the site is rendered.  Similar to how
> mobile sites have the link for "full desktop". Something like a
> "simplified" or "accessibility" link.
>
> In any case, it seems this is an issue already under consideration.
>

:)


> Thank you for your time.  :-)
>
> On Mon, Jun 17, 2019 at 11:06 AM Jenn Giardino <jgiardin at redhat.com>
> wrote:
>
>>
>> Hi Alex,
>>
>> Thanks for sharing! User feedback is always appreciated! :-)
>>
>> In addition to Greg's question, is this in the context of PatternFly 3 or
>> 4?
>>
>> One or our initiatives with PatternFly 4 is to meet WCAG 2.0 up to level
>> AA. The concerns you expressed are something that we have been actively
>> working on by increasing the target area within which a user has to click
>> to interact with an element, in addition to increasing the spacing between
>> elements. If your user was experiencing issues in the context of PatternFly
>> 4, we would love to capture more feedback about their experience so that we
>> can make more informed decisions as we work on this aspect of PatternFly.
>>
>>  I was curious if there is an option/toggle to require clicks to expand
>>> vs. mouse-over?
>>
>>
>> One of the potential downsides of this approach is that it can make the
>> interaction more tedious for users who are using only a keyboard to
>> interact with the UI, since things that become visible on hover must also
>> become visible when it receives focus by hitting the Tab key. The end
>> result of this for the keyboard-only user is that they have many more Tab
>> key stops in the UI when these components become expanded on focus, than
>> when these components remain in a collapsed state until click/Enter.
>>
>>
>> Jenn Giardino
>> Senior Interaction Designer
>> User Experience Design Team
>> Red Hat, Inc.
>> 1-919-716-5045
>> jgiardin at redhat.com
>>
>>
>> On Mon, Jun 17, 2019 at 11:41 AM Greg Sheremeta <gshereme at redhat.com>
>> wrote:
>>
>>> Is there a specific component that the use finds challenging, for
>>> example the left navigation?
>>>
>>> Greg
>>>
>>>
>>> On Mon, Jun 17, 2019 at 11:38 AM Alex Mayberry <amayberr at redhat.com>
>>> wrote:
>>>
>>>>
>>>> Hi everyone.  Just wanted to drop a note that I am working with a
>>>> customer that has a difficult time holding the mouse steady, and the
>>>> patternfly UI is proving quite difficult for them to use.
>>>>
>>>> With Chrome, the browser responded so quickly that it was causing a
>>>> great deal of frustration.  With firefox, the issue doesn't seem to be
>>>> present.
>>>>
>>>> I was curious if there is an option/toggle to require clicks to expand
>>>> vs. mouse-over?
>>>> _______________________________________________
>>>> PatternFly mailing list
>>>> PatternFly at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/patternfly
>>>>
>>>
>>>
>>> --
>>>
>>> Greg Sheremeta
>>>
>>> Senior Software Engineer, Service Delivery
>>>
>>> Red Hat <https://www.redhat.com/>
>>> <https://www.redhat.com/>
>>> _______________________________________________
>>> PatternFly mailing list
>>> PatternFly at redhat.com
>>> https://www.redhat.com/mailman/listinfo/patternfly
>>>
>>

-- 

Greg Sheremeta

Senior Software Engineer, Service Delivery

Red Hat <https://www.redhat.com/>
<https://www.redhat.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/patternfly/attachments/20190618/57fe515f/attachment.htm>