a11yproject.com
Less
a11yproject.com | Less | |
---|---|---|
2 | 2 | |
3,686 | 121 | |
0.1% | - | |
6.6 | 0.0 | |
about 1 month ago | about 7 years ago | |
Nunjucks | Ruby | |
Apache License 2.0 | - |
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.
Less
-
CSS Deep
mrkrupski/LESS-Dynamic-Stylesheet - A set of useful mixins for LESS, the CSS pre-processor: http://lesscss.org
-
Setting Up a JavaScript Build Process using Rollup
Now that we have addressed our scripts, we can focus on our styles. In this setup, we will look at the CSS preprocessor Less which lets us write CSS simpler, use variables and mixins. We can add it to the project with the following command:
What are some alternatives?
fancyInput - Makes typing in input fields fun with CSS3 effects
rollup-plugin-postcss - Seamless integration between Rollup and PostCSS.
PageLoadingEffects - Modern ways of revealing new content using SVG animations.
Less Rails - :-1: :train: Less.js For Rails
awesome-conferences
Quiet Assets
css-loaders - A collection of loading spinners animated with CSS
Sass - Sass makes CSS fun!
SpinKit - A collection of loading indicators animated with CSS
Emoji - A gem. For Emoji. For everyone. ❤
humane-js - A simple, modern, browser notification system
Gutenberg - Modern framework to print the web correctly.