Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Accessibility][Keyboard - Create Node]: Keyboard focus is not visible on 'Create Node' button. #2061

Closed
ashish315 opened this issue Feb 23, 2020 · 8 comments

Comments

@ashish315
Copy link

User Experience:
Keyboard dependent users would face difficulty if keyboard focus does not visible on the control.

Test Environment
Browser: Microsoft Edge Canary Version: 82.0.425.0 (Official build)
OS build: 2004 (19564.1005)
Screen Reader: Narrator
URL: Bot Framework Composer
Prerequisite Here

Repro Steps:

  1. Open the above mentioned URL in EDGE and set the zoom at 400%.
  2. Select 'Design Flow' from left navigation.
  3. Now, navigate to the flow chart.
  4. Navigate to "+" button available in the flow chart and observe the issue.

Actual:
The keyboard focus is not visible at "+" button i.e. create node button.

Expected:
The focus should be clearly visible to each and every control available at the page.

MAS Guideline: MAS2.4.7

Attachment:
MAS2.4.7_Focus not visible on Add node button.zip

@corinagum
Copy link
Contributor

@DesignPolice Do specs already have focus for this element? If not, this may need designer input before fix. :)
Feel free to unassign yourself if no input needed.

@DesignPolice
Copy link

DesignPolice commented Feb 27, 2020

Brought this one up in Stand Up this morning, it a relatively minimal change, but I think it brings up a bigger focus issue in the Visual Editor.

Adding @mareekuh @a-b-r-o-w-n (they were in the stand-up)

We have Focus on items in the Visual Editor as we "tab" through items the state is a blue outline. When the blue outline is on white we hit our 4.5:1 number - with the background of F6F6F6 - it knocks us down to 4.19:1 - not passing.

So my first thought was okay we can just use a darker blue, but then looking at some of the other nodes we have some inconsistent things going on.

Screen Shot 2020-02-27 at 12 29 01 PM

Screen Shot 2020-02-27 at 12 28 55 PM

So I need to get some clarity on what we want to do -

The Blue will need to be darker if we are going to use it - #0078D4 would need to be #004E8C

Black is fine for the other state...

for Focus on the "+" I would like it to be a circle like this, but probably should get some consensus on that

Screen Shot 2020-02-27 at 12 37 29 PM

Screen Shot 2020-02-27 at 12 37 43 PM

PVA does a mix of really heavy drop shadow and a border around the "+" not a huge fan, but that might be something that Lili thinks we should align. ( PVA Below )

Screen Shot 2020-02-27 at 12 51 36 PM

Let the comments begin.

thanks,
Marc

@mareekuh
Copy link
Contributor

mareekuh commented Feb 27, 2020 via email

@DesignPolice
Copy link

Okay that works. @corinagum do we need to alter the blue color to hit contrast? It does fall a little short on the #F6F6F6 background.

@corinagum
Copy link
Contributor

I would say play it safe and pick the darker color, if that's alright with you guys.

@DesignPolice
Copy link

okay... then go with this. That would affect anything on the Visual Canvas then... so all of the nodes.

The Blue will need to be darker if we are going to use it - #0078D4 would need to be #004E8C

@yeze322 yeze322 self-assigned this Mar 4, 2020
@yeze322
Copy link
Contributor

yeze322 commented Apr 9, 2020

@alanlong9278 let's solve it along with other 'tab navigation' issues

@ashish315
Copy link
Author

ashish315 commented Apr 23, 2020

As checked the issue is fixed now. So, HCL is closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants