a11yproject.com
docco
a11yproject.com | docco | |
---|---|---|
2 | 4 | |
3,686 | 3,544 | |
0.1% | - | |
6.6 | 0.0 | |
about 1 month ago | 5 months ago | |
Nunjucks | HTML | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
a11yproject.com
-
The A11Y Project Checklist
> The colour contrast of the title section fails all tests.
It doesn't. The background color is --color-blue: #3b4bbf and the SVG's fill color is --color-blue-tint: #d4d8f2, a 5.1:1 contrast ratio.
Having the top-level page titles replicated as such giant SVGs is probably overdoing it but the user also has the page title in the browser tab and the word "Checklist" underlined in the main navigation to locate themselves (the actual h1 heading for the page is visually hidden contains "Checklist."
I didn't find a viewport size/shape that had the overlapping you're describing, maybe their design has a problem they didn't find and you could report it to them [0].
> I also thought uppercase text-transform was best avoided
Do you mean on "Check your WCAG compliance?" Making all the text on a page or full sentences all uppercase can make it hard to read, I don't think you have to pretend `text-transform: uppercase` doesn't exist. It's definitely better to use the property to make text uppercase as a design choice vs. actually writing the text using all capital letters, at least some of the time browsers and assistive technologies can treat them differently.
I think the A11y Project in particular tries to reach designers and developers who often think "accessibility" means making sites plain, boring, and/or ugly. Therefore, they've adopted a design that is more capital "D" Designed on their top-level pages; that may mean not making everything maximally accessible 100% of the time. Additionally, people will always disagree about design choices.
[0] https://github.com/a11yproject/a11yproject.com/
-
CSS Deep
a11yproject/a11yproject.com - Making #A11Y tips and tricks easier to digest and leveraging the community into the cloud.
docco
-
Ask HN: Show Code with Notes Alongside
i have seen those in annotated javascript documentation. but it was the other way around. (comment on the left, and code on the right).
they all seem to use docco[0] with the option to display comment in "parallel". the author of docco used it in their library underscore[1].
[0]: https://github.com/jashkenas/docco
- Docco is a quick-and-dirty documentation generator
-
Lisp.py
Side note - it's been a while since i've seen a Docco-style annotated-source-style documentation! http://ashkenas.com/docco/
Backbone.js was the first time i saw it, and I loved it! https://backbonejs.org/docs/backbone.html It demonstrated to me that the libraries I use are just normal code that other people write, and i myself can read it to understand a problem.
-
CSS Deep
jashkenas/docco - Literate Programming can be Quick and Dirty.
What are some alternatives?
fancyInput - Makes typing in input fields fun with CSS3 effects
documentation.js - :book: documentation for modern JavaScript
PageLoadingEffects - Modern ways of revealing new content using SVG animations.
ESDoc - ESDoc - Good Documentation for JavaScript
Less - Leaner CSS, in your browser or Ruby (via less.js).
sphinx - The Sphinx documentation generator
awesome-conferences
jsduck - Simple JavaScript Duckumentation generator.
css-loaders - A collection of loading spinners animated with CSS
dox - JavaScript documentation generator for node using markdown and jsdoc
SpinKit - A collection of loading indicators animated with CSS
JSDoc - An API documentation generator for JavaScript.