Skip to content

Commit 4ebc353

Browse files
authored
fix(a11y): reducing 50% of a11y issues on contributor page (#79)
1 parent 4633d39 commit 4ebc353

File tree

2 files changed

+8
-4
lines changed

2 files changed

+8
-4
lines changed

_sass/_contributing.scss

+4
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,8 @@
99
font-size: 1.2em;
1010
padding: 1em 0 0;
1111
}
12+
13+
a {
14+
text-decoration: underline;
15+
}
1216
}

contributing/index.html

+4-4
Original file line numberDiff line numberDiff line change
@@ -22,23 +22,23 @@
2222
<ol class="description">
2323

2424
<li> Look through the existing issues and see if your idea is something new. </li>
25-
<li> Create a <a href="https://github.com/yargs/yargs/issues"> new issue </a>, or comment on an existing issue that you would like to help solve:
25+
<li> Create a <a href="https://github.com/yargs/yargs/issues">new issue</a>, or comment on an existing issue that you would like to help solve:
2626
<ul>
2727
<li> it's usually best to get some feedback before proceeding to write code. ,</li>
2828
</ul>
2929
</li>
3030

3131
<li> fork the yargs repo, and clone it to your computer:
3232
<ul>
33-
<li> GitHub has <a href="https://help.github.com/articles/using-pull-requests/"> great documentation </a> regarding writing your first pull request. </li>
33+
<li> GitHub has <a href="https://help.github.com/articles/using-pull-requests/">great documentation</a> regarding writing your first pull request. </li>
3434
</ul>
3535
</li>
3636

3737
<li> make sure that you write unit-test for any code that you write for yargs:
3838
<ul>
39-
<li> we use <a href="https://github.com/feross/standard"> standard </a> coding style, which will validate your style when you run tests </li>
39+
<li> we use <a href="https://github.com/feross/standard">standard</a> coding style, which will validate your style when you run tests </li>
4040

41-
<li> look through our extensive test suite in <a href="https://github.com/yargs/yargs/issues"> /test </a> to get an idea for how to write unit-tests for this codebase. </li>
41+
<li> look through our extensive test suite in <a href="https://github.com/yargs/yargs/issues">/test</a> to get an idea for how to write unit-tests for this codebase. </li>
4242
</ul>
4343
</li>
4444

0 commit comments

Comments
 (0)