opened
dianjuar
username_0
<!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.

ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->

## I'm submitting a...
<!-- 
Please search GitHub for a similar issue or PR before submitting.
Check one of the following options with "x" -->
<pre><code>
[ ] Regression <!--(a behavior that used to work and stopped working in a new release)-->
[X] Bug report
[ ] Feature request
[ ] Documentation issue or request (new chapter/page)
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
</code></pre>

## Current behavior
<!-- Describe how the issue manifests. -->
The bookmark anchors are not visible when they were accessed by keyboard

![ezgif-2-b8e8cb912d1a](https://user-images.githubusercontent.com/7026066/56079965-ec3c7580-5dc0-11e9-9f9f-2a504e435d7f.gif)

## Expected behavior
<!-- Describe what the desired behavior would be. -->
When the bookmark anchor has the focus be visible

![ezgif-2-7c2e1254cbbe](https://user-images.githubusercontent.com/7026066/56079950-cb742000-5dc0-11e9-81c8-ce84932280c3.gif)



## Minimal reproduction of the problem with instructions
<!-- Please share a repo, a gist, or step-by-step instructions. -->
Click on the article or the body section (is a shortcut to skip another interactible element) and start navigating through all (using tab) and where is expected to see the bookmark anchor is not there but if you put your mouse hover the tittle you can see that is focused.


## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->
Improve the accessibility of the site, remember that there is around of [1billon of people in the world that are disabled](https://www.google.com/search?q=how+many+fisical+disabled+person+in+the+world&oq=how+many+fisical+disabled+person+in+the+world)
Just imagine, to create empathy, that is no possible to use one arm because you have a permanent or a temporal disability (a broken arm for ex). Is more comfortable if you use the keyboard, but if the page is not prepared for that the experience is going to be affected.

## Environment

<pre><code>
For Tooling issues:
- Node version: XX  <!-- run `node --version` -->
- Platform:  <!-- Mac, Linux, Windows -->

Others:
<!-- Anything else relevant?  Operating system version, IDE, package manager, ... -->
</code></pre>
A little accesibility issue
issue
closed
kamilmysliwiec
username_1
issue