-
Notifications
You must be signed in to change notification settings - Fork 36
Hackday #15
Everybody presents themselves: Graciela (Unic), Donato (Liip), Joshua (Freelance), Henrik (Zeix, as Esther could not join and as they want to have more than one person in the ADG project), Manu (ZFA, A4A), Léa (Awareness Workshops about Accessibility; BKW), Sulekha (UX designer from India)
Josh presents the new parts of the ADG. The new release has been online for two weeks now. There are parts about mobile screen readers in the Setup section plus in the Knowledge section. Parts have been re-written where they are relevant for both desktop and mobile screen readers. Minor changes, some parts have been moved. Everything is as simple as possible.
We want to find out what our strategy for the ADG is. Graciela has talked to Thomas Jaggi (who has been working at Unic and does so as a freelancer now) about website statistics. ADG is hosted at Netlify. There is basically no analytics data about the ADG and we would need that. Some work has been done but right now we do not have any data. At Netlify we would have to pay for analytics which is why we have not integrated that part. As far as we have understood, there is data at Netlify but we cannot access it. Graciela would re-check this with Thomas. Donato says, Matomo should be ready to use. Plus: In Github, there is another open task, where we wanted to collect data on a voluntary basis (survey popup).
Joshua explains, where it all started: In each and every project that A4A did, the client's developers understood that they had to do something for more accessibility, but they did not really know how to do it. So A4A had all the necessary knowledge and was able to help with 1:1 workshops or coaching sessions. So the original idea about the ADG was to put all that knowledge into a knowlege base (which is the ADG).
- In the last years further ressources and knowlegde bases have appeared. Some are behind a pay wall. We would need a better overview of what the other ressources do (and what they don't). We would need to find out more about the possible unique aspects about ADG.
- We are far away from making accessibility knowledge obsolete, because it still will be needed in the future. There is not enough knowledge about accessibility in the developers' world.
- Most of the content of the ADG is for developers. We would have to find a good balance between new content and "just" maintaining the content we have.
- The community is still a small one. And the ADG is a community-driven thing. In the past, all content came from A4A, but their role has changed (they neither have the financial nor the human ressources to generate new contents). Contents should come from the agencies, from the community. A4A confirms, that they think content should come from the community, whereas the quality check and releasing new content and coordination would be A4A's role.
- Is the ADG rather a book or a reference? See https://github.com/Access4all/adg/wiki/Testing,-Release-1.0,-Dec-2018-and-Jan-2019. It was planned as a kind of book. But times may have changed. If we reorganise the contents, Sulekha proposes to go point by point, e.g. writing about tables, first for UX designers, then for UI development, etc. Then write about images, first for UX designers, then for UI development.
- The A11y Project: https://a11yproject.com/. Is also community driven. Is more than a library where you can find examples. Most links go the external sites. It existed already before the ADG started. Josh clarifies that the fact that the A11y project links to others sites is exactly what we did not want to do. This is why we started our own guide. Josh will create a ticket to get in contact with the A11y project: They could link to our ADG.
- Mozilla Accessibility Developer guides: https://developer.mozilla.org/en-US/docs/Web/Accessibility. Graciela has asked some of her fellow workers at Unic what they use as a reference. They do use Mozilla's developer guides a lot. It does focus on accessibility and on learning accessible web development. Léa points out that we should try to link to them and then ask them to link back to us. That would make the ADG more visible.
- As a matter of fact, there have been many accessibility guide projects but they have not worked together. Maybe ADG is not the one that survives in the end but our knowledge could enhance other existing guides.
- We will have to find out what kind of other ressources there are and what they do and how they work.
- We do not have any data about its usage.
- At Unic: A couple colleagues use it and really like it a lot. But many say they do not find enough examples there, so the don't.
- Sulekha says she finds the ADG useful but there are some things that could be optimised.
- It is the only guide we know about that is intended for beginners and where you then can go on and on. Allows you to begin from zero.
- We put all our thoughts in the Mural Strategy blueprint in this PDF: Strategy Blueprint Results PDF
25.8.2020 Hackday #16, @Hinderling-Volkart, Badenerstrasse 415, 8003 Zürich. Topic not yet set.