adg
adg copied to clipboard
Access4all
Accessibility Developer Guide
Based on the short discussion on Slack, I noticed that the current Codepen implementation automatically creates a pen on your account. It uses a form and a submit button to...
Made a web.dev Lighthouse check today. Loading speed could be improved. As we have a static site generator here, we should easily be able to push that very close 100...
In order to make it possible for non-developers to edit the content, we want to investigate tan alternative/complementary setup, based on Netlify CMS.
In order to speed up on-boarding of new contributors, we need to evaluate the usage of more established tool/static generator. Hints: - https://vuepress.vuejs.org/ - https://www.staticgen.com/ - https://getkirby.com/ (requires web server...
The current pattern to visually hide content we have in the guide moves elements outside the viewport (by assuming the viewport isn't bigger than the statically defined pixel size). The...
TODO: create or add to `GUIDELINES.md`! At the time being, code examples are working well, but their code is very inconsistent (and can probably be improved a lot). Some day,...
Bookmarklets can be a very fast, easy and useful way to test for some accessibility stuff. (So far, this issue is meant as a general brainstorming log.) - Win HCM...
From https://github.com/Access4all/adg/pull/201: Note to myself: I suppose we should keep a conclusion, but write something like this: > ARIA can be the right thing to use in those rare where...
# Current state The page [examples/headings/alternative-techniques](https://www.accessibility-developer-guide.com/examples/headings/alternative-techniques/#description-using-aria-optional) under the heading "Description using ARIA (optional)" contains a codepan example and a positive test case as such:  # Issue I've re-tested locally...
We should split content from presentation repo. It could be more easy for editors and reviewers. Related to this, we have this tickets: #199, #198
